North Dakota Code vs Us Gov Contracts
A side-by-side look at the North Dakota Code and Us Gov Contracts MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose North Dakota Code for legal work as a local process; choose Us Gov Contracts 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 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.
Choose Us Gov Contracts when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You want tools like
gov_contracts_search, gov_spending_search, gov_contracts_jurisdictions.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 45/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View North Dakota Code | View Us Gov Contracts |
Tools & capabilities
North Dakota Code tools
No tool names declared yet. Check the project README from the listing page.
Us Gov Contracts tools 3
gov_contracts_searchSearch AWARDED US state & local government contracts, normalized across jurisdictions (keyless open data). Filter by vendor (winning supplier), keyword (contract title/description), awarding agency, and minimum dollar amount. Covers state and county contract registries — pass a `jurisdiction` key (…gov_spending_searchSearch US STATE government spending / vendor payments — the 'checkbook' data of what an agency actually PAID a vendor (distinct from an awarded contract's value). Keyless. Filter by vendor, awarding agency, spending category keyword, and minimum amount. Pass a `jurisdiction` key (see gov_contracts_…gov_contracts_jurisdictionsList the US state & local jurisdictions covered by this pack, split into contract-award jurisdictions (gov_contracts_search) and spending/checkbook jurisdictions (gov_spending_search), with each one's key, level (state/county/city), data platform, source dataset URL, and live record count.
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.
North Dakota Code
{
"mcpServers": {
"north-dakota-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-north-dakota-code"
]
}
}
}
Us Gov Contracts
{
"mcpServers": {
"us-gov-contracts": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-us-gov-contracts"
]
}
}
}
Frequently asked questions
North Dakota Code is categorized under Legal and uses a local stdio subprocess. Us Gov Contracts belongs to Legal and uses a local stdio subprocess. Pick North Dakota Code for legal work and Us Gov Contracts 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.
North Dakota Code is listed as free. Auth: no auth required. Us Gov Contracts has no declared pricing — check the project's own site. 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 north-dakota-code and us-gov-contracts as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, North Dakota Code has a quality signal of 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Us Gov Contracts has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.