AI Act Radar vs Contracko
A side-by-side look at the AI Act Radar and Contracko MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AI Act Radar for legal work; choose Contracko 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 AI Act Radar when
- You need dedicated capabilities in the Legal domain.
- You have the keys it needs:
AIA_SECRET.
Choose Contracko when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 31/100 · Emerging | 70/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | AIA_SECRET | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View AI Act Radar | View Contracko |
Tools & capabilities
AI Act Radar tools
No tool names declared yet. Check the project README from the listing page.
Contracko 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.
AI Act Radar
No confirmed install command for AI Act Radar yet — follow the setup steps linked from its listing page rather than a guessed package name.
Contracko
{
"mcpServers": {
"contracko": {
"command": "npx",
"args": [
"-y",
"@contracko/mcp"
]
}
}
}