Contractoracle vs Texas Ag Opinions
A side-by-side look at the Contractoracle and Texas Ag Opinions MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Contractoracle for legal work over a hosted endpoint; choose Texas Ag Opinions for legal as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Contractoracle when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
register_contract, list_contracts, clause_check.
Choose Texas Ag Opinions when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 48/100 · Fair | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 11 | Not listed |
| Full listing | View Contractoracle | View Texas Ag Opinions |
Tools & capabilities
Contractoracle tools 11
register_contractAdd or update an ICT third-party contract. Tracks all DORA Art. 30 mandatory clauses.list_contractsList contracts with optional filters.clause_checkValidate a contract against all DORA Art. 30 mandatory clauses (standard + CIF).subcontracting_chainMap and assess the subcontracting chain of a contract (RTS on subcontracting).exit_readinessEvaluate exit plan readiness for a contract — Art. 28(8) exit strategies.cif_analysisAnalyze all Critical/Important Function contracts for enhanced Art. 30(3) requirements.contract_gapsIdentify missing mandatory clauses across all contracts.contract_scoringRed-flag risk scoring: exit risk, lock-in, jurisdiction, subcontracting gaps.contract_expiryUpcoming contract expirations and renewal deadlines.contract_analyze_llmAI-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.health_checkServer status.
Texas Ag Opinions tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Contractoracle
{
"mcpServers": {
"contractoracle": {
"url": "https://tooloracle.io/contract/mcp/"
}
}
}
Texas Ag Opinions
{
"mcpServers": {
"texas-ag-opinions": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-texas-ag-opinions"
]
}
}
}
Frequently asked questions
Contractoracle is categorized under Legal and uses a remote HTTP/SSE transport. Texas Ag Opinions belongs to Legal and uses a local stdio subprocess. Pick Contractoracle for legal work and Texas Ag Opinions for legal.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Contractoracle has no declared pricing — check the project's own site. Texas Ag Opinions is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add contractoracle and texas-ag-opinions as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Contractoracle has a quality signal of 48/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Texas Ag Opinions has 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.