OpenWorkProof vs North Dakota Code
A side-by-side look at the OpenWorkProof and North Dakota Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose OpenWorkProof for legal work as a local process; choose North Dakota 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?
Choose OpenWorkProof when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
Choose North Dakota 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 | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 44/100 · Fair | 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 | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 262 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View OpenWorkProof | View North Dakota Code |
Tools & capabilities
OpenWorkProof tools
No tool names declared yet. Check the project README from the listing page.
North Dakota 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.
OpenWorkProof
{
"mcpServers": {
"openworkproof": {
"command": "uvx",
"args": [
"openworkproof"
]
}
}
}
North Dakota Code
{
"mcpServers": {
"north-dakota-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-north-dakota-code"
]
}
}
}
Frequently asked questions
OpenWorkProof is categorized under Legal and uses a local stdio subprocess. North Dakota Code belongs to Legal and uses a local stdio subprocess. Pick OpenWorkProof for legal work and North Dakota 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.
OpenWorkProof has no declared pricing — check the project's own site. North Dakota 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 openworkproof and north-dakota-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, OpenWorkProof has a quality signal of 44/100 (Fair) with 2 views, 0 installs and 262 GitHub stars. North Dakota Code has 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.