Us Gov Contracts vs License Verify MCP
A side-by-side look at the Us Gov Contracts and License Verify MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Us Gov Contracts for legal work as a local process; choose License Verify MCP 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 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.
Choose License Verify MCP when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
jurisdiction, license_number, business_name.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 53/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 3 | 3 |
| Full listing | View Us Gov Contracts | View License Verify MCP |
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.
License Verify MCP tools 3
jurisdictionlicense_numberbusiness_name
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": {
"us-gov-contracts": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-us-gov-contracts"
]
}
}
}
License Verify MCP
{
"mcpServers": {
"lmaniraruta-license-verify-mcp": {
"command": "npx",
"args": [
"-y",
"apify"
]
}
}
}
Frequently asked questions
Us Gov Contracts is categorized under Legal and uses a local stdio subprocess. License Verify MCP belongs to Legal and uses a local stdio subprocess. Pick Us Gov Contracts for legal work and License Verify MCP 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. License Verify MCP is listed as a paid service. 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 lmaniraruta-license-verify-mcp 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. License Verify MCP has 57/100 (Good) with 5 views, 0 installs and 0 GitHub stars.