LeashIndex Get the report

Index / data

io.github.pathmodeio/mcp-server

io-github-pathmodeio-mcp-server declares 35 capabilities across 35 tools, with 1 critical issue. 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.

74/100 exposureHigh exposure

Manifest recorded 2026-11-03 from tools/list answered by the npm package @pathmode/mcp-server@1.43.3 (published to npm as @pathmode/mcp-server, listed in the official MCP registry as io.github.pathmodeio/mcp-server 1.43.3), 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 35 tools

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

high · no-expiry · All 35 tools

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

35 of 35 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 · 16 of 35 tools

16 tools can modify data and declare no limit.

low · uncapped-read · 19 of 35 tools

19 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
get_current_intentread declared
list_intentsread declared
get_intentread declared
get_review_feedbackread declared
respond_review_feedbackwrite assumed
get_intent_evidenceread declared
list_intent_change_requestsread declared
get_intent_change_requestread declared
reject_intent_change_requestwrite inferred
propose_spec_changewrite assumed
get_intent_relationsread declared
search_intentsread declared
analyze_intent_graphread declared
export_contextread declared
sync_contextwrite inferred
get_agent_promptread declared
get_workspaceread declared
get_constitutionread declared
update_intent_statusread inferred
log_implementation_notewrite assumed
record_implementation_contextwrite assumed
record_implementation_findingread inferred
record_outcome_measurementwrite assumed
create_intentwrite inferred
update_intentwrite inferred
query_evidenceread declared
create_evidencewrite inferred
attach_original_requestwrite inferred
link_evidencewrite assumed
verify_implementationread inferred
check_intent_readinessread declared
intent_savewrite assumed
intent_importwrite assumed
confirm_intent_dimensionwrite assumed
intent_exportwrite assumed
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.