Home / MCP registry index / com.theartofservice/compliance-intelligence

com.theartofservice/compliance-intelligence

com.theartofservice/compliance-intelligence in the official MCP registry. Endpoint https://api.theartofservice.com/mcp. Source: github.com/GJB65/compliance-mcp-skill-example.

The registry describes it as: What one compliance standard already evidences of another, with the reasoning and the rejections.

We read its 33 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

agent_search_courses agent_get_course agent_courses_for_frameworks agent_list_course_frameworks agent_buy_course agent_course_contents agent_search_course_content agent_signals_this_week agent_capital_by_function agent_controls_touched_by agent_signal_exposure agent_search_frameworks agent_get_framework agent_get_framework_controls agent_get_framework_controls_by_name agent_get_control agent_get_control_cross_references agent_cross_framework_map agent_coverage_report agent_search agent_platform_stats agent_pricing_info agent_coverage_crosswalk agent_crosswalk_provenance agent_crosswalk_pair agent_crosswalk_refuted agent_combined_coverage agent_buy_crosswalk agent_buy_review agent_list_crosswalk_pairs adoption_list_engagements adoption_get_adoption_summary adoption_get_report

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-theartofservice-compliance-intelligence/badge.svg)](https://lazaretto.dev/mcp-registry/com-theartofservice-compliance-intelligence)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.