Other · Local MCP server
MCP Sam Gov
Keyless-first MCP: 153 tools for US federal + state/local (SLED) contracting, spending & regulation.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.cliwant/mcp-sam-gov- Version
- 1.17.0
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-29
- Updated
- 2026-09-29
- Publisher
- cliwant (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/cliwant) · how
- Repository
- github.com/cliwant/mcp-sam-gov
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @cliwant/mcp-sam-gov | 1.17.0 | stdio |
How to connect MCP Sam Gov
MCP Sam Gov runs locally from a Node.js package published to the npm registry: @cliwant/mcp-sam-gov version 1.17.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @cliwant/mcp-sam-gov@1.17.0. It reads these environment variables: SAM_GOV_API_KEY (secret), CENSUS_API_KEY (secret), FRED_API_KEY (secret), BEA_API_KEY (secret), BLS_API_KEY (secret), DOL_API_KEY (secret), DATA_GOV_API_KEY (secret), NVD_API_KEY (secret), OPENFDA_API_KEY (secret), SOCRATA_APP_TOKEN (secret), COURTLISTENER_API_TOKEN (secret), LDA_API_KEY (secret), EDGAR_USER_AGENT and MCP_SAM_GOV_TOOLSETS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp-sam-gov": {
"command": "npx",
"args": [
"-y",
"@cliwant/mcp-sam-gov@1.17.0"
],
"env": {
"SAM_GOV_API_KEY": "<secret>",
"CENSUS_API_KEY": "<secret>",
"FRED_API_KEY": "<secret>",
"BEA_API_KEY": "<secret>",
"BLS_API_KEY": "<secret>",
"DOL_API_KEY": "<secret>",
"DATA_GOV_API_KEY": "<secret>",
"NVD_API_KEY": "<secret>",
"OPENFDA_API_KEY": "<secret>",
"SOCRATA_APP_TOKEN": "<secret>",
"COURTLISTENER_API_TOKEN": "<secret>",
"LDA_API_KEY": "<secret>",
"EDGAR_USER_AGENT": "<value>",
"MCP_SAM_GOV_TOOLSETS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| MCP Risk Ledger MCPPaid remote MCP for server intake risk reports, tool review, approvals, and readiness. | Remote · HTTPLive check: ✗ no handshake |
| MCP RoadmapshMCP server for roadmap.sh: roadmaps, best practices, interview questions, projects & progress. | Local · stdio |
| MCP S3Read-only S3/MinIO/R2 object storage for AI agents - list buckets/objects, metadata, fetch. | Local · stdio |
| MCP SafrapayMCP server for Safrapay - Banco Safra acquirer: credit, Pix, boleto + split, 3DS, chargebacks. | Local · stdio |
| MCP SantanderMCP server for Santander Brasil - Pix, Cobrança (boleto), Arrecadação, Extrato (OAuth2 + mTLS) | Local · stdio |
| MCP Schema AuditAudits MCP tool definitions for patterns that make models call tools wrong or mis-fill args. | Remote · HTTPLive check: sign-in required |
| MCP ScorecardAgent-readiness scorecard for any MCP server: 10 checks, 0-100 score, actionable findings. | Local · stdio |
| MCP ScreenshotScreenshot capture with PII masking and cross-platform support for AI agents. | Local · stdio |