Sovereign AI Act MCP vs Texas Ag Opinions
A side-by-side look at the Sovereign AI Act MCP 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 Sovereign AI Act MCP for legal work as a local process; 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 Sovereign AI Act MCP when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SOVEREIGN_API_BASE. - You want tools like
classify_ai_system, lookup_article, search_eu_ai_act.
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 | 57/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | SOVEREIGN_API_BASE | 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 | 4 | Not listed |
| Full listing | View Sovereign AI Act MCP | View Texas Ag Opinions |
Tools & capabilities
Sovereign AI Act MCP tools 4
classify_ai_systemClassify an AI system under the EU AI Act (Regulation (EU) 2024/1689 as amended by Regulation (EU) 2026/1744). Give a plain-language description of what the system does and it returns the risk tier (prohibited / high_risk / limited / minimal), the exact Annex III category where applicable, and the binding Articles — every reference grounded verbatim in the law. USE THIS when the user asks whether an AI system is high-risk or prohibited, what obligations apply to it, or which Articles bind a specific AI use-case. For looking up one known Article use lookup_article; for keyword search use search_eu_ai_act.lookup_articleReturn the verbatim text of one specific EU AI Act Article (1–113), exactly as published in the Official Journal of the EU. USE THIS when the user names or asks for a known Article number (e.g. 'show me Article 6', 'what does Article 5 say'). For keyword/topic search across the whole law use search_eu_ai_act; to classify a system use classify_ai_system.search_eu_ai_actFull-text keyword search across the entire EU AI Act corpus — all Articles (1–113), Recitals (1–180) and Annexes (I–XIII) — returning the provisions that match your terms, each grounded verbatim in the law. USE THIS when you want to find where a topic, term or obligation is addressed but do not know the Article number (e.g. 'where does the law cover human oversight?', 'find biometric categorisation', 'rules for GPAI'). To fetch one known Article use lookup_article; to assess a specific system's risk tier use classify_ai_system.get_compliance_deadlinesReturn the canonical EU AI Act application timeline (the staggered dates each obligation starts to apply, as amended by Regulation (EU) 2026/1744, the Digital Omnibus on AI, in force 27 July 2026) together with the penalty/fine tiers under Article 99. Takes no arguments. USE THIS when the user asks when the EU AI Act (or a specific obligation) applies, what the key compliance deadlines are, or how large the fines can be.
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.
Sovereign AI Act MCP
{
"mcpServers": {
"sovereign-ai-act-mcp": {
"command": "npx",
"args": [
"-y",
"sovereign-ai-act-mcp"
],
"env": {
"SOVEREIGN_API_BASE": "YOUR_SOVEREIGN_API_BASE_HERE"
}
}
}
}
Texas Ag Opinions
{
"mcpServers": {
"texas-ag-opinions": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-texas-ag-opinions"
]
}
}
}
Frequently asked questions
Sovereign AI Act MCP is categorized under Legal and uses a local stdio subprocess. Texas Ag Opinions belongs to Legal and uses a local stdio subprocess. Pick Sovereign AI Act MCP 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.
Sovereign AI Act MCP 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 sovereign-ai-act-mcp and texas-ag-opinions as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Sovereign AI Act MCP has a quality signal of 57/100 (Good) 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.