io. tooloracle/ contractoracle
by tooloracle.io · remote · no sign-in to list tools · v1.0.0 · published by io.tooloracle
ContractOracle - 10 contract analysis tools: clause extraction, redlines, DORA mappings.
11 tools: 7 change things and 4 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things7Claude Code: ask: see these tools
- Only reads4Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http contractoracle https://tooloracle.io/contract/mcp/Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
11 tools
Changes things 7Claude Code: ask
contract_expiryUpcoming contract expirations and renewal deadlines.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Upcoming contract expirations and renewal deadlines.
contract_gapsIdentify missing mandatory clauses across all contracts.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Identify missing mandatory clauses across all contracts.
contract_scoringRed-flag risk scoring: exit risk, lock-in, jurisdiction, subcontracting gaps.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Red-flag risk scoring: exit risk, lock-in, jurisdiction, subcontracting gaps.
exit_readinessEvaluate exit plan readiness for a contract — Art.No findings
Why it is in this group
- The description's first verb is "evaluate": a word for a change.
Description, as the server wrote it Evaluate exit plan readiness for a contract — Art. 28(8) exit strategies.
health_checkServer status.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Server status.
register_contractAdd or update an ICT third-party contract.No findings
Why it is in this group
- The description's first verb is "add": a word for a change.
Description, as the server wrote it Add or update an ICT third-party contract. Tracks all DORA Art. 30 mandatory clauses.
subcontracting_chainMap and assess the subcontracting chain of a contract (RTS on subcontracting).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Map and assess the subcontracting chain of a contract (RTS on subcontracting).
Only reads 4Claude Code: allow
cif_analysisAnalyze all Critical/Important Function contracts for enhanced Art.No findings
Why it is in this group
- The description's first verb is "analyze": a word for reading.
Description, as the server wrote it Analyze all Critical/Important Function contracts for enhanced Art. 30(3) requirements.
clause_checkValidate a contract against all DORA Art.No findings
Why it is in this group
- The description's first verb is "validate": a word for reading.
Description, as the server wrote it Validate a contract against all DORA Art. 30 mandatory clauses (standard + CIF).
contract_analyze_llmAI-powered deep analysis of contract text against DORA Art.No findings
Why it is in this group
- The name "contract_analyze_llm" says "analyze": a word for reading.
Description, as the server wrote it 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.
list_contractsList contracts with optional filters.No findings
Why it is in this group
- The name "list_contracts" says "list": a word for reading.
Description, as the server wrote it List contracts with optional filters.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http contractoracle https://tooloracle.io/contract/mcp/Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__contractoracle__list_contracts",
"mcp__contractoracle__clause_check",
"mcp__contractoracle__cif_analysis",
"mcp__contractoracle__contract_analyze_llm"
],
"ask": [
"mcp__contractoracle__register_contract",
"mcp__contractoracle__subcontracting_chain",
"mcp__contractoracle__exit_readiness",
"mcp__contractoracle__contract_gaps",
"mcp__contractoracle__contract_scoring",
"mcp__contractoracle__contract_expiry",
"mcp__contractoracle__health_check"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as contractoracle. Review it before you use it.