LeashIndex Get the report

Index / devtools

io.github.Beever-AI/beever-atlas

io-github-beever-ai-beever-atlas declares 28 capabilities across 28 tools, with 2 critical issues.

56/100 exposureElevated

Manifest recorded 2026-10-12 from tools/list answered by the container image ghcr.io/beever-ai/beever-atlas version 0.3.0 (published as the image ghcr.io/beever-ai/beever-atlas:0.3.0, listed in the official MCP registry as io.github.Beever-AI/beever-atlas 0.3.0), 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 28 tools

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

1 tool is classified as irreversible and declares no limit.

high · no-expiry · All 28 tools

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

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

4 tools can modify data and declare no limit.

low · uncapped-read · 23 of 28 tools

23 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
search_channel_knowledgeread inferred
whoamiwrite assumed
list_connectionsread inferred
list_channelsread inferred
ask_channelwrite assumed
search_channel_factsread inferred
get_wiki_pageread inferred
get_recent_activityread inferred
search_media_referencesread inferred
search_memoryread inferred
lint_wikiread inferred
get_extraction_statusread inferred
read_wiki_pageread inferred
list_wiki_pagesread inferred
get_wiki_graphread inferred
read_wiki_moduleread inferred
find_decisionsread inferred
get_tensionsread inferred
find_factsread inferred
read_wiki_sectionread inferred
read_provenanceread inferred
find_expertsread inferred
search_relationshipsread inferred
trace_decision_historyread inferred
start_new_sessionwrite assumed
trigger_syncsend inferred
refresh_wikiwrite assumed
get_job_statusread 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.