LeashIndex Get the report

Index / data

footnote-mcp

io-github-kazkozdev-footnote-mcp declares 45 capabilities across 45 tools, with 1 critical issue.

85/100 exposureHigh exposure

Manifest recorded 2026-10-13 from tools/list answered by the PyPI package footnote-mcp==0.2.6 (published to PyPI as footnote-mcp, listed in the official MCP registry as io.github.KazKozDev/footnote-mcp 0.2.6), run in an isolated container with no network access and no 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 45 tools

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

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

45 of 45 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 · 24 of 45 tools

24 tools can modify data and declare no limit.

low · uncapped-read · 21 of 45 tools

21 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
web_searchread inferred
web_deep_searchread inferred
web_readread inferred
web_extract_tablesread inferred
web_detect_downloadsread inferred
web_parse_filewrite assumed
web_fetch_jsonread inferred
check_date_completenessread inferred
classify_sourcewrite assumed
generate_search_queriesread inferred
resolve_unitswrite assumed
validate_unit_rowsread inferred
evidence_entailmentwrite assumed
tool_spec_proposewrite assumed
tool_code_generatewrite assumed
tool_code_validateread inferred
tool_code_run_sandboxedread inferred
tool_promoteread inferred
source_cache_getread inferred
source_cache_putwrite inferred
build_research_debug_reportwrite assumed
startup_health_checkread inferred
web_navigatewrite assumed
web_snapshotwrite assumed
web_clickwrite assumed
web_typewrite assumed
web_extractwrite assumed
web_scrollwrite assumed
browser_extract_tableswrite assumed
browser_set_date_rangewrite inferred
browser_extract_tables_for_date_rangewrite inferred
web_archive_fetchread inferred
papers_searchread inferred
encyclopedia_searchread inferred
github_searchread inferred
archive_searchread inferred
web_search_recentread inferred
corroborate_claimwrite assumed
locate_claim_spanwrite assumed
recipe_registrywrite assumed
web_fetch_authenticatedread inferred
web_crawlwrite assumed
export_datasetwrite inferred
reconcile_time_serieswrite assumed
web_screenshotwrite 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.