Is the Tooloracle Contractoracle MCP server down?

mcp-registry/io.tooloracle/contractoracle · v1.0.0

healthy
Last checked 2026-10-24 19:43 UTC · handshake 495ms

As of 2026-10-24 19:43 UTC, the Tooloracle Contractoracle 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 6 outages in 90 days, with a median recovery of 9 minutes.

uptime (30d checks)
99.9%
checks observed
4,615
outages (90d)
6
tools
11

ContractOracle - 10 contract analysis tools: clause extraction, redlines, DORA mappings.

Install Tooloracle Contractoracle MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http tooloracle-contractoracle-mcp-server https://tooloracle.io/contract/mcp/

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "tooloracle-contractoracle-mcp-server": {
      "type": "http",
      "url": "https://tooloracle.io/contract/mcp/"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (69/100)

D (69/100): 0 error(s), 4 warning(s) across 11 tool(s); ~1,080 tokens of tool definitions.
Scores higher than 4% of 15,642 MCP servers Glimind has audited.
Its tool list costs an agent ~1,080 tokens per session — lighter than 75% of servers.
69 → 69 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions37
Safety hints30
Token cost100
Client compatibility70
Protocol40
Reliability100
Stability100

What to fix (5)

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 →

Tools: cif_analysis, clause_check, contract_analyze_llm, contract_expiry, contract_gaps and 6 more

33 parameter(s) across 6 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 →

Tools: clause_check, contract_scoring, exit_readiness, list_contracts, register_contract and 1 more

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 →

Tools: health_check

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 →

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 6 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.tooloracle%2Fcontractoracle/fixes

clause_check 1 change
{
  "name": "clause_check",
  "description": "Validate a contract against all DORA Art. 30 mandatory clauses (standard + CIF).",
  "inputSchema": {
    "type": "object",
    "required": [
      "contract_id"
    ],
    "properties": {
      "contract_id": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
contract_analyze_llm 1 change
{
  "name": "contract_analyze_llm",
  "description": "AI-powered deep analysis of contract text against DORA Art. 30(2) mandatory clauses using local Gemma 4 LLM. Provide raw contract text or a contract_id for structured analysis.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "text": {
        "type": "string",
        "description": "Raw contract text to analyze"
      },
      "contract_id": {
        "type": "string",
        "description": "Existing contract ID for structured analysis"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
exit_readiness 1 change
{
  "name": "exit_readiness",
  "description": "Evaluate exit plan readiness for a contract — Art. 28(8) exit strategies.",
  "inputSchema": {
    "type": "object",
    "required": [
      "contract_id"
    ],
    "properties": {
      "contract_id": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

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/contractoracle"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.tooloracle/contractoracle"}) over MCP.

Passed

Largest tool definitions

Static 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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.tooloracle%2Fcontractoracle.svg)](https://glimind.com/server/mcp-registry%2Fio.tooloracle%2Fcontractoracle?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.tooloracle%2Fcontractoracle?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.tooloracle%2Fcontractoracle.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.tooloracle%2Fcontractoracle.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.tooloracle%2Fcontractoracle?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7eb9b01a8d087e2d…, first seen 2026-10-17, included at leaf 6146 of 60,832. Version history · verify what your client received.

Tools (11)

Compare: most reliable other servers · most reliable knowledge servers · most reliable ml servers · most reliable productivity servers · most reliable database servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Tooloracle Contractoracle MCP server down right now?

As of 2026-10-24 19:43 UTC, the Tooloracle Contractoracle 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 6 outages in 90 days, with a median recovery of 9 minutes.

How many tools does Tooloracle Contractoracle MCP server provide?

Tooloracle Contractoracle MCP server advertises 11 tools, including cif_analysis, clause_check, contract_analyze_llm, contract_expiry, contract_gaps.

How do I install Tooloracle Contractoracle MCP server?

Point your MCP client at this streamable-http endpoint: https://tooloracle.io/contract/mcp/

Is the Tooloracle Contractoracle MCP server safe to connect to an AI agent?

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.

Operator of Tooloracle Contractoracle MCP server?

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.

Feedback
Help us improve