Court Records MCP vs Utah Code
A side-by-side look at the Court Records MCP and Utah Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
Court Records MCPLegal · Remote HTTP/SSESearch US federal and state court records through CourtListener and the RECAP archive42FairAuth: not declaredU
Utah CodeLegal · Local subprocess (stdio)Utah Code — state statutes by citation, plus topic search.40FairAuth: no auth requiredVerdict: choose Court Records MCP for legal work over a hosted endpoint; choose Utah Code for legal as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
CChoose Court Records MCP when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
UChoose Utah Code 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 | C Court Records MCP | U Utah Code |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 42/100 · Fair | 40/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 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Court Records MCP | View Utah Code |
Tools & capabilities
Court Records MCP tools
No tool names declared yet. Check the project README from the listing page.
Utah Code 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.
Court Records MCP
{
"mcpServers": {
"court-records-mcp": {
"url": "https://mcp.nexlab.net/s/court-records"
}
}
}
Utah Code
{
"mcpServers": {
"utah-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-utah-code"
]
}
}
}
Frequently asked questions
Court Records MCP is categorized under Legal and uses a remote HTTP/SSE transport. Utah Code belongs to Legal and uses a local stdio subprocess. Pick Court Records MCP for legal work and Utah Code 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.
Court Records MCP has no declared pricing — check the project's own site. Utah Code 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 court-records-mcp and utah-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Court Records MCP has a quality signal of 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Utah Code has 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.