Home / MCP registry index / io.tooloracle/contractoracle
io.tooloracle/contractoracle
io.tooloracle/contractoracle in the official MCP registry.
Endpoint https://tooloracle.io/contract/mcp/. Source: github.com/ToolOracle/contractoracle.
The registry describes it as: ContractOracle - 10 contract analysis tools: clause extraction, redlines, DORA mappings.
We read its 11 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
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
register_contract list_contracts clause_check subcontracting_chain exit_readiness cif_analysis contract_gaps contract_scoring contract_expiry contract_analyze_llm health_check
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-tooloracle-contractoracle)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.