Kentucky Code vs Us Gov Contracts

A side-by-side look at the Kentucky 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.

Kentucky Code logoKentucky CodeLegal · Local subprocess (stdio)Kentucky Revised Statutes (KRS) — state statutes by citation and by topic.61GoodAuth: no auth requiredUs Gov Contracts logoUs Gov ContractsLegal · Local subprocess (stdio)US state & local awarded government contracts, normalized across jurisdictions — keyless53GoodAuth: not declared

Verdict: choose Kentucky 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?

Kentucky Code logoChoose Kentucky 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.
  • You want tools like ky_statute, ky_search.
Explore Kentucky Code

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecKentucky Code logoKentucky CodeUs Gov Contracts logoUs Gov Contracts
CategoryLegalLegal
Quality signal61/100 · Good53/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars00
Directory activity 2 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools23

Tools & capabilities

Kentucky Code tools 2

  • ky_statuteGet the FULL TEXT of a section of the Kentucky Revised Statutes (KRS) — Kentucky state law — by citation. "507.020" is murder; "383.580" is the landlord security-deposit statute. Accepts natural forms: "507.020", "KRS 507.020", "§ 507.020". Returns the current statutory text, the catchline, the "Effective:" date, and the legislative "History:" (the Acts that enacted and amended it). Kentucky publishes the CURRENT text only — a prior (pre-amendment) version's text is not available online, only its existence; this tool says so rather than guessing. Keyless. Use for "what does KRS 507.020 say" or to check a Kentucky statute a case or contract relies on.
  • ky_searchSearch the Kentucky Revised Statutes BY TOPIC or keyword rather than citation — "security deposit", "concealed carry", "DUI per se limit", "homicide". Real full-text search over the statutory body text, not just catchlines: a query like "landlord" surfaces KRS 383.580 ("Security deposits") even though that catchline contains neither word. Returns matching citations and catchlines; call ky_statute with a citation for the full text. Keyless.

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.

Kentucky Code

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

Us Gov Contracts

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

Frequently asked questions

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

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

On AllMCPs, Kentucky Code has a quality signal of 61/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Us Gov Contracts has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.