LeashIndex Get the report

Index / devtools

com.theartofservice/compliance-intelligence

com-theartofservice-compliance-intelligence declares 33 capabilities across 33 tools, with 3 critical issues.

83/100 exposureHigh exposure

Manifest recorded 2026-10-11 from tools/list on https://api.theartofservice.com/mcp, published in the official MCP registry as com.theartofservice/compliance-intelligence 1.1.0. 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 33 tools

33 of 33 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 · 3 of 33 tools

3 tools are classified as irreversible and declare no limit.

critical · uncapped-spend · 3 of 33 tools

3 tools are classified as moving money and declare no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 33 tools

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

33 of 33 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 · 11 of 33 tools

11 tools can modify data and declare no limit.

low · uncapped-read · 19 of 33 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
agent_search_coursesread inferred
agent_get_courseread inferred
agent_courses_for_frameworksread inferred
agent_list_course_frameworksread inferred
agent_buy_coursepay inferred
agent_course_contentswrite assumed
agent_search_course_contentread inferred
agent_signals_this_weekwrite assumed
agent_capital_by_functionwrite assumed
agent_controls_touched_bywrite assumed
agent_signal_exposurewrite assumed
agent_search_frameworksread inferred
agent_get_frameworkread inferred
agent_get_framework_controlsread inferred
agent_get_framework_controls_by_nameread inferred
agent_get_controlread inferred
agent_get_control_cross_referencesread inferred
agent_cross_framework_mapwrite assumed
agent_coverage_reportread inferred
agent_searchread inferred
agent_platform_statsread inferred
agent_pricing_inforead inferred
agent_coverage_crosswalkwrite assumed
agent_crosswalk_provenancewrite assumed
agent_crosswalk_pairwrite assumed
agent_crosswalk_refutedwrite assumed
agent_combined_coveragewrite assumed
agent_buy_crosswalkpay inferred
agent_buy_reviewpay inferred
agent_list_crosswalk_pairsread inferred
adoption_list_engagementsread inferred
adoption_get_adoption_summaryread inferred
adoption_get_reportread 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.