mcp-registry/io.tooloracle/governanceoracle · v1.0.0
As of 2026-10-27 07:55 UTC, the Tooloracle Governanceoracle MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 9 minutes.
GovernanceOracle - 10 governance tools: board packs, policies, attestations, evidence.
Point your MCP client at this streamable-http endpoint: https://tooloracle.io/governance/mcp/
11 of 11 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 →
28 parameter(s) across 4 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 →
1 tool(s) have descriptions under 20 characters.
Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. 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. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.tooloracle%2Fgovernanceoracle/fixes
{
"name": "control_status",
"description": "Control effectiveness dashboard across all DORA control domains.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "health_check",
"description": "Server status.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "list_findings",
"description": "List findings with optional filters.",
"inputSchema": {
"type": "object",
"properties": {
"owner": {
"type": "string"
},
"domain": {
"enum": [
"access_management",
"change_management",
"incident_management",
"business_continuity",
"third_party_risk",
"data_protection",
"network_security",
"vulnerability_management",
"logging_monitoring",
"cryptography",
"physical_security",
"awareness_training"
],
"type": "string"
},
"status": {
"enum": [
"open",
"in_progress",
"remediated",
"accepted",
"overdue"
],
"type": "string"
},
"severity": {
"enum": [
"critical",
"high",
"medium",
"low",
"info"
],
"type": "string"
}
},
"additionalProperties": false
},
"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.tooloracle/governanceoracle"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.tooloracle/governanceoracle"}) over MCP.
register_finding ~281 tokenslist_findings ~175 tokensexception_register ~138 tokensboard_report_llm ~120 tokensaction_tracker ~119 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.tooloracle%2Fgovernanceoracle?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.tooloracle%2Fgovernanceoracle?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.tooloracle%2Fgovernanceoracle.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.tooloracle%2Fgovernanceoracle.svg :target: https://glimind.com/server/mcp-registry%2Fio.tooloracle%2Fgovernanceoracle?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:7a3f84e6c520124d…, first seen 2026-10-17, included at leaf 4038 of 78,171. Version history · verify what your client received.
Compare: most reliable productivity servers · most reliable ml servers · most reliable security servers · most reliable devops servers · most reliable data 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-27 07:55 UTC, the Tooloracle Governanceoracle MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 9 minutes.
Tooloracle Governanceoracle MCP server advertises 11 tools, including action_tracker, annual_review, board_report, board_report_llm, control_status.
Point your MCP client at this streamable-http endpoint: https://tooloracle.io/governance/mcp/
Glimind scanned all 11 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.