LeashIndex Get the report

Index / payments

InsureLink

io-github-skewing1-insurelink declares 32 capabilities across 32 tools, with 3 critical issues.

91/100 exposureHigh exposure

Manifest recorded 2026-10-11 from tools/list on https://ivnmscuuljqubunqcgkh.supabase.co/functions/v1/mcp-server/mcp, published in the official MCP registry as io.github.skewing1/insurelink 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 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 · 4 of 32 tools

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

10 tools can modify data and declare no limit.

low · uncapped-read · 15 of 32 tools

15 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
discover_capabilitiesread inferred
get_reputationread inferred
get_leaderboardread inferred
get_sla_historyread inferred
get_activityread inferred
get_attestationread inferred
verify_attestationread inferred
get_attestation_freshnessread inferred
subscribe_attestation_freshnesssend inferred
unsubscribe_attestation_freshnessdelete inferred
list_attestation_freshness_subscriptionsread inferred
network_lookupread inferred
voice_intentwrite assumed
check_agent_insuranceread inferred
get_agent_risk_scoreread inferred
verify_transaction_safetyread inferred
get_agent_claim_historyread inferred
mint_slawrite inferred
renew_slawrite assumed
wrap_usdcwrite assumed
micro_resetwrite assumed
early_exitwrite assumed
claim_breach_creditwrite assumed
mitigation_receiptwrite assumed
verify_reputation_snapshotread inferred
attest_reputationwrite assumed
subscribe_reputation_drift_alertssend inferred
simulate_actionwrite assumed
simulate_paid_actionpay inferred
simulate_paid_action_batchpay inferred
pay_then_callpay inferred
insurelink_chargepay 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.