LeashIndex Get the report

Index / data

RepuTend

com-reputend-reputend declares 33 capabilities across 33 tools, with 2 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.

84/100 exposureHigh exposure

Manifest recorded 2026-11-08 from tools/list on https://mcp.reputend.com/mcp, published in the official MCP registry as com.reputend/reputend 1.1.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 33 tools

33 of 33 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 · 4 of 33 tools

4 tools are classified as irreversible and declare no limit.

high · no-expiry · All 33 tools

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

33 of 33 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 · 15 of 33 tools

15 tools can modify data and declare no limit.

low · uncapped-read · 14 of 33 tools

14 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
pingread declared
run_auditwrite assumed
get_audit_resultread declared
request_accesswrite inferred
redeem_invitesend inferred
send_feedbacksend inferred
list_disputable_reviewsread declared
get_caseread declared
list_review_triageread declared
get_outcomesread declared
regenerate_draftwrite inferred
approve_filingwrite inferred
claim_packetread inferred
mark_filedwrite assumed
record_prereqwrite inferred
record_decisionwrite assumed
appeal_packetread declared
record_appealwrite assumed
decline_packetwrite assumed
get_business_profile_questionsread declared
set_business_profilewrite inferred
set_evidence_endpointwrite inferred
set_approval_requiredwrite inferred
list_teamread declared
invite_membersend inferred
remove_memberdelete inferred
list_companiesread declared
get_checkout_linkread inferred
billing_portal_linkwrite assumed
onboarding_statusread declared
next_invoiceread declared
quote_attack_modewrite assumed
set_attack_modewrite 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.