mcp-registry/io.github.gjb65/compliance-intelligence · vAccess 1120 compliance frameworks, 51,079+ controls, and 315K+ cross-framework m
Also listed as mcp-registry/com.theartofservice/compliance-intelligence
As of 2026-10-26 17:09 UTC, the Gjb65 Compliance Intelligence MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 25 outages in 90 days, with a median recovery of 5 minutes.
Query 692+ compliance frameworks, 13,700+ controls, and 280K+ cross-framework mappings.
Point your MCP client at this streamable-http endpoint: https://api.theartofservice.com/mcp
33 of 33 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
29 parameter(s) across 20 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 20 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.gjb65%2Fcompliance-intelligence/fixes
{
"name": "adoption_get_adoption_summary",
"description": "Adoption Summary\n\nAdoption against baseline for one engagement: overall, by process area, and movement.\n\nSays whether the baseline was measured or reconstructed from artefacts, and whether the\ntwo waves are comparable at all. A pulse that used a different question set is reported\nas not comparable rather than differenced, because the difference would be between two\nrulers rather than two measurements.\n\n### Responses:\n\n**200**: Successful Response (Success Response)\nContent-Type: application/json",
"inputSchema": {
"type": "object",
"title": "adoption_get_adoption_summaryArguments",
"required": [
"engagement_id"
],
"properties": {
"engagement_id": {
"type": "integer",
"title": "engagement_id",
"minimum": 1
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "adoption_get_report",
"description": "Get Report\n\nThe latest management report as facts plus the evidence behind each one.\n\nReturns the fact sheet, not the rendered page. Every figure carries the responses or\nthe uploaded file it came from, so a claim can be checked rather than repeated.\n\n### Responses:\n\n**200**: Successful Response (Success Response)\nContent-Type: application/json",
"inputSchema": {
"type": "object",
"title": "adoption_get_reportArguments",
"required": [
"engagement_id"
],
"properties": {
"engagement_id": {
"type": "integer",
"title": "engagement_id",
"minimum": 1
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "adoption_list_engagements",
"description": "List Engagements\n\nEvery adoption engagement the signed in consultant runs, with its current state.\n\n### Responses:\n\n**200**: Successful Response (Success Response)\nContent-Type: application/json",
"inputSchema": {
"type": "object",
"title": "adoption_list_engagementsArguments",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.gjb65/compliance-intelligence"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.gjb65/compliance-intelligence"}) over MCP.
agent_search_frameworks ~388 tokensagent_controls_touched_by ~337 tokensagent_signals_this_week ~311 tokensagent_search ~283 tokensagent_coverage_crosswalk ~281 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.gjb65%2Fcompliance-intelligence?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.gjb65%2Fcompliance-intelligence?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.gjb65%2Fcompliance-intelligence.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.gjb65%2Fcompliance-intelligence.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.gjb65%2Fcompliance-intelligence?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:68218632a7b94975…, first seen 2026-10-17, included at leaf 11380 of 74,329. Version history · verify what your client received.
Compare: most reliable data servers · most reliable productivity servers · most reliable knowledge servers · most reliable finance servers · most reliable payments servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 17:09 UTC, the Gjb65 Compliance Intelligence MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 25 outages in 90 days, with a median recovery of 5 minutes.
Gjb65 Compliance Intelligence MCP server advertises 41 tools, including adoption_get_adoption_summary, adoption_get_report, adoption_list_engagements, advisory_query, agent_buy_course.
Point your MCP client at this streamable-http endpoint: https://api.theartofservice.com/mcp
Glimind scanned all 33 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.