LeashIndex Get the report

Index / messaging

ai.autonomad/computeback

ai-autonomad-computeback declares 32 capabilities across 32 tools, with 3 critical issues.

87/100 exposureHigh exposure

Manifest recorded 2026-10-11 from tools/list answered by the npm package @autonomad1/computeback-mcp@1.1.4 (published to npm as @autonomad1/computeback-mcp, listed in the official MCP registry as ai.autonomad/computeback 1.1.4), run in an isolated container with no network access and placeholder credentials. 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 32 tools

32 of 32 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 · 7 of 32 tools

7 tools are classified as irreversible and declare no limit.

critical · uncapped-spend · 1 of 32 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 32 tools

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

32 of 32 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 · 9 of 32 tools

9 tools can modify data and declare no limit.

low · uncapped-read · 16 of 32 tools

16 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
search_productsread inferred
get_productread inferred
get_categoriesread inferred
check_balanceread inferred
create_orderwrite inferred
get_ordersread inferred
get_recommendationsread inferred
buy_nomdpay inferred
get_audience_dataread inferred
list_audiencesread inferred
get_business_profileread inferred
get_product_inforead inferred
fetch_urlread inferred
dispatch_email_campaignsend inferred
dispatch_voice_campaignsend inferred
dispatch_sms_campaignsend inferred
configure_landing_pagewrite inferred
dispatch_landing_pagessend inferred
send_landing_chatsend inferred
list_workflow_templatesread inferred
start_workflowsend inferred
accept_offerwrite assumed
decline_offerwrite assumed
start_offerwrite assumed
complete_offerwrite assumed
place_bidwrite inferred
withdraw_bidwrite assumed
list_my_inboxread inferred
get_agent_profileread inferred
edit_agent_profilewrite inferred
get_settlement_statusread inferred
list_my_settlementsread inferred
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.