LeashIndex Get the report

Index / payments

ai.bitroad/bitroad

ai-bitroad-bitroad declares 72 capabilities across 72 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.

99/100 exposureHigh exposure

Manifest recorded 2026-11-08 from tools/list on https://app.bitroad.ai/api/v1/mcp, published in the official MCP registry as ai.bitroad/bitroad 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 72 tools

72 of 72 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 · 14 of 72 tools

14 tools are classified as irreversible or destructive and declare no limit. 6 of them are counted only because the server annotated them destructiveHint. In MCP that annotation marks a tool that may make destructive changes rather than only additive ones; it does not say the change cannot be undone.

critical · uncapped-spend · 5 of 72 tools

5 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 72 tools

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

72 of 72 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 · 18 of 72 tools

18 tools can modify data and declare no limit.

low · uncapped-read · 40 of 72 tools

40 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
services_search_listingsread declared
services_purchasepay inferred
services_request_quotewrite inferred
services_get_quoteread declared
services_accept_quotewrite assumed
services_counter_quotesend inferred
services_reject_quotedestructive declared
services_withdraw_quotedestructive declared
services_list_my_quotesread declared
services_acknowledge_deliverywrite assumed
intents_postsend inferred
intents_list_openread declared
intents_bidwrite assumed
services_create_listingread inferred
services_get_listingread declared
services_list_open_requestsread declared
services_submit_quotewrite assumed
services_start_workwrite assumed
services_submit_deliverablewrite assumed
services_list_my_salesread declared
auth_whoamiread declared
auth_revoke_selfdestructive declared
sellers_getread declared
platforms_getread declared
register_getread declared
addresses_listread declared
addresses_createwrite inferred
payment_methods_listread declared
payment_methods_createpay inferred
envelopes_listread declared
envelopes_getread declared
disputes_filewrite assumed
disputes_listread declared
disputes_getread declared
disputes_add_evidencewrite inferred
disputes_withdrawdestructive declared
disputes_respondwrite assumed
catalog_search_productsread declared
catalog_get_productread declared
catalog_list_categoriesread declared
catalog_describe_categoryread declared
purchase_create_intentpay inferred
purchase_confirm_intentpay inferred
purchase_cancel_intentpay inferred
orders_listread declared
orders_getread declared
returns_initiatewrite assumed
returns_getread declared
returns_listread declared
returns_get_labelread declared
seller_get_meread declared
seller_set_fingerprintwrite inferred
pricing_oracleread declared
procurement_memory_getread declared
seller_onboarding_statusread declared
seller_list_listingsread declared
seller_get_listingread declared
seller_create_listingread inferred
seller_update_listingread inferred
seller_archive_listingdestructive declared
seller_update_stockwrite inferred
seller_list_ordersread declared
seller_get_orderread declared
seller_mark_shippedwrite assumed
seller_mark_deliveredwrite assumed
seller_attach_trackingwrite inferred
seller_list_returnsread declared
seller_get_returnread declared
seller_accept_returnwrite assumed
seller_reject_returndestructive declared
seller_list_reviewsread declared
seller_respond_to_reviewsend inferred

Record history

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

RecordedExposureSource
2026-10-2899 tools/list on https://app.bitroad.ai/api/v1/mcp, published in the official MCP registry as ai.bitroad/bitroad 1.0.0
2026-10-1199 tools/list on https://app.bitroad.ai/api/v1/mcp, published in the official MCP registry as ai.bitroad/bitroad 1.0.0
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.