Us Gov Contracts vs North Dakota Code

A side-by-side look at the Us Gov Contracts 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.

Us Gov Contracts logoUs Gov ContractsLegal · Local subprocess (stdio)US state & local awarded government contracts, normalized across jurisdictions — keyless53GoodAuth: not declaredNorth Dakota Code logoNorth Dakota CodeLegal · Local subprocess (stdio)North Dakota Century Code — state statutes by citation and by topic.45FairAuth: no auth required

Verdict: choose Us Gov Contracts 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?

Us Gov Contracts logoChoose 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.
Explore Us Gov Contracts

North Dakota Code logoChoose 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.
Explore North Dakota Code

Feature & specification comparison

Rows where the two servers differ are marked.

SpecUs Gov Contracts logoUs Gov ContractsNorth Dakota Code logoNorth Dakota Code
CategoryLegalLegal
Quality signal53/100 · Good45/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars00
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools3Not listed

Tools & capabilities

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.

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.

Us Gov Contracts

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "us-gov-contracts": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-us-gov-contracts"
      ]
    }
  }
}

North Dakota Code

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "north-dakota-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-north-dakota-code"
      ]
    }
  }
}

Frequently asked questions

Us Gov Contracts is categorized under Legal and uses a local stdio subprocess. North Dakota Code belongs to Legal and uses a local stdio subprocess. Pick Us Gov Contracts 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.

Us Gov Contracts 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 us-gov-contracts and north-dakota-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Us Gov Contracts has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. North Dakota Code has 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.