LeashIndex Get the report

Index / payments

Agoranome seller tools

io-github-agoranome-agoranome declares 42 capabilities across 42 tools, with 3 critical issues. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.

64/100 exposureElevated

Manifest recorded 2026-11-08 from tools/list on https://api.agoranome.com/mcp, published in the official MCP registry as io.github.Agoranome/agoranome 1.0.3. 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 42 tools

42 of 42 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 · 1 of 42 tools

1 tool is classified as irreversible and declares no limit.

critical · uncapped-spend · 1 of 42 tools

1 tool is classified as moving money and declares no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 42 tools

42 of 42 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 42 tools

42 of 42 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.

low · uncapped-read · 41 of 42 tools

41 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
lint_listingread declared
conformance_checkread declared
rank_checkread declared
buyer_panelread declared
buyer_panel_oneread declared
signed_sampleread declared
demand_gapsread declared
payer_analyticsread declared
weekly_insightsread declared
model_watchread declared
rank_watchread declared
certify_offerread declared
certify_continuousread declared
buyer_drillread declared
buyer_checkread declared
spend_auditread declared
vendor_watchread declared
response_scanread declared
plan_quoteread declared
dispute_packread declared
fund_commonspay inferred
pingread declared
price_positionread declared
survival_oddsread declared
repeat_demandread declared
proof_valueread declared
payer_mixread declared
server_standingread declared
category_briefread declared
launch_briefread declared
address_briefread declared
monthly_chapterread declared
insights_pageread declared
row_set_5read declared
row_set_50read declared
row_set_500read declared
row_set_5000read declared
rank_sampleread declared
check_fair_offerread declared
check_offerread declared
agent_payments_weeklyread declared
registered_agent_cardread declared

Record history

Earlier records for this server. A correction is added here, never written over the record it corrects.

RecordedExposureSource
2026-10-2852 tools/list on https://api.agoranome.com/mcp, published in the official MCP registry as io.github.Agoranome/agoranome 1.0.3
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.