LeashIndex Get the report

Index / devtools

io.github.mockzilla/mockzilla-mcp

io-github-mockzilla-mockzilla-mcp declares 36 capabilities across 36 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.

81/100 exposureHigh exposure

Manifest recorded 2026-10-29 from tools/list answered by the npm package @mockzilla/mcp@0.2.28 (published to npm as @mockzilla/mcp, listed in the official MCP registry as io.github.mockzilla/mockzilla-mcp 0.2.28), 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 36 tools

36 of 36 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 · 1 of 36 tools

1 tool is classified as irreversible and declares no limit.

high · no-expiry · All 36 tools

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

36 of 36 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 · 20 of 36 tools

20 tools can modify data and declare no limit.

low · uncapped-read · 15 of 36 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
check_cliread inferred
install_cliwrite assumed
serve_locallywrite assumed
call_endpointwrite inferred
mock_endpointwrite assumed
list_mock_endpointsread inferred
clear_mock_endpointswrite inferred
request_historyread inferred
diagnose_requestswrite inferred
setup_replaywrite assumed
list_replaysread inferred
check_github_deployableread inferred
list_github_reposread inferred
publish_to_githubsend inferred
wait_for_github_deploywrite inferred
unpublish_from_githubwrite assumed
stop_locallywrite assumed
mockzilla_docs_topicsread inferred
mockzilla_docs_readread inferred
mockzilla_docs_searchread inferred
bridge_statusread inferred
loginwrite inferred
logoutwrite assumed
discover_specswrite assumed
infowrite assumed
lintread inferred
simplifywrite assumed
generatewrite assumed
packwrite assumed
get_contextread declared
list_catalog_productsread declared
deploy_mock_from_catalogwrite inferred
deploy_mock_from_specwrite inferred
deploy_mock_from_urlwrite inferred
wait_for_deployread declared
list_simsread declared
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.