LeashIndex Get the report

Index / messaging

xportalx

io-github-virgen101-xportalx declares 29 capabilities across 29 tools, with 3 critical issues.

87/100 exposureHigh exposure

Manifest recorded 2026-10-11 from tools/list on https://fflpdljiuruqdnewvwkk.supabase.co/functions/v1/mcp, published in the official MCP registry as io.github.virgen101/xportalx 1.0.0. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 29 tools

29 of 29 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 5 of 29 tools

5 tools are classified as irreversible and declare no limit.

critical · uncapped-spend · 3 of 29 tools

3 tools are classified as moving money and declare no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 29 tools

29 of 29 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 29 tools

29 of 29 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 12 of 29 tools

12 tools can modify data and declare no limit.

low · uncapped-read · 12 of 29 tools

12 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
fetch_apiread inferred
fetch_pageread inferred
fetch_pdfread inferred
extractwrite assumed
crawlwrite assumed
markdown_convertwrite assumed
dexscreener_tokenread inferred
coinbase_priceread inferred
verify_agentread inferred
coinbase_facilitatorread inferred
x402_proxywrite assumed
x402_proxy_priceread inferred
erc8004_registerwrite assumed
failure_reasonwrite assumed
mcp_pricingread inferred
solve_captchawrite assumed
zora_walletread inferred
swapwrite assumed
create_walletwrite inferred
fund_walletpay inferred
fund_wallet_ethpay inferred
withdraw_walletpay inferred
send_tokenssend inferred
get_wallet_balanceread inferred
x402_sendsend inferred
nansen_smart_money_holdingswrite assumed
nansen_smart_money_netflowsread inferred
nansen_token_god_modewrite assumed
nansen_wallet_profilerwrite assumed
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.