LeashIndex Get the report

Index / other

AdAnvil

io-github-maxbuildog-adanvil declares 43 capabilities across 43 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.

85/100 exposureHigh exposure

Manifest recorded 2026-10-27 from tools/list answered by the PyPI package adanvil==0.4.0 (published to PyPI as adanvil, listed in the official MCP registry as io.github.maxbuildog/adanvil 0.4.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 43 tools

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

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

43 of 43 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 · 25 of 43 tools

25 tools can modify data and declare no limit.

low · uncapped-read · 18 of 43 tools

18 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
project_initwrite inferred
project_read_textread inferred
brand_onboardwrite assumed
brand_getread inferred
library_indexwrite assumed
library_viewread inferred
library_annotatewrite inferred
library_searchread inferred
vision_setupwrite assumed
speech_viewread inferred
speech_refinewrite assumed
speech_takeswrite assumed
reference_decodewrite assumed
reference_breakdownwrite assumed
library_overviewwrite assumed
frame_viewread inferred
timeline_exportwrite assumed
recipe_listread inferred
recipe_getread inferred
editing_guidewrite inferred
storyboard_schemaread inferred
storyboard_savewrite assumed
storyboard_patchwrite inferred
caption_previewread inferred
end_cardwrite assumed
storyboard_validateread inferred
render_startread inferred
variants_buildwrite assumed
render_batchwrite assumed
render_formatswrite assumed
voice_generatewrite assumed
sfx_listread inferred
music_beatswrite assumed
storyboard_snapwrite inferred
music_profilewrite assumed
music_searchread inferred
music_fetchread inferred
music_generatewrite assumed
voice_viewread inferred
job_statusread inferred
qc_runwrite assumed
ad_scorewrite assumed
compare_pairread 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.