compliance-intelligence

warnings

api.theartofservice.com

What one compliance standard already evidences of another, with the reasoning and the rejections.

https://api.theartofservice.com/mcpWebsiteNo authMCP 2025-11-25vAccess 688 compliance frameworks, 21,539+ controls, and 397K+ cross-framework mappings. Query the compliance knowledge graph to research requirements, map controls across frameworks, and analyse coverage gaps.last checked 24 Aug 2026spoke MCP on 3 of 3 checks (30 days)initialize in 241 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 23 tools listable
Credentials demanded in prose	✕agent_search_courses, agent_get_course, agent_courses_for_frameworks, agent_list_course_frameworks, agent_platform_stats, agent_coverage_crosswalk, agent_list_crosswalk_pairs These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

7 of the 23 tools listed anonymously say in their own descriptions that they need an account or a key (agent_search_courses, agent_get_course, agent_courses_for_frameworks, agent_list_course_frameworks, agent_platform_stats, agent_coverage_crosswalk, agent_list_crosswalk_pairs), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

Tools

agent_buy_crosswalkagent_buy_reviewagent_combined_coverageagent_courses_for_frameworksagent_coverage_crosswalkagent_coverage_reportagent_cross_framework_mapagent_crosswalk_pairagent_crosswalk_provenanceagent_crosswalk_refutedagent_get_controlagent_get_control_cross_referencesagent_get_courseagent_get_frameworkagent_get_framework_controlsagent_get_framework_controls_by_nameagent_list_course_frameworksagent_list_crosswalk_pairsagent_platform_statsagent_pricing_infoagent_searchagent_search_coursesagent_search_frameworks

Contract history

24 Aug 2026vAccess 688 compliance frameworks, 21,539+ controls, and 397K+ cross-framework mappings. Query the compliance knowledge graph to research requirements, map controls across frameworks, and analyse coverage gaps.first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/compliance-intelligence/badge.svg)](https://mcpi.app/servers/compliance-intelligence)