Government Contracts MCP
REMOTE · GOV-CONTRACTS-MCP-PRODUCTION.UP.RAILWAY.APP
Government contract search and federal procurement data: SAM.gov opportunities + USASpending awards.
Available components
Last scanned (56 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 29 Jul 2026.
Category Finance and Payments
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 19 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 18 Aug 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- HSTS header: unverified → fail ▼ security
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- 1 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Aug 2026 · Probed https://gov-contracts-mcp-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gov-contracts-mcp-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 502 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gov-contracts-mcp-production.up.railway.app/mcp | HTTP error | 502 | |
| http (plaintext) | http://gov-contracts-mcp-production.up.railway.app/mcp | HTTPS enforced | 301 | https://gov-contracts-mcp-production.up.railway.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agency_spending ~211
Analyze U.S. federal government spending for an agency — contract dollars broken down by NAICS sector and the top awardees, computed live from USASpending.gov for the requested fiscal year (the full federal procurement record, not just the local table). PAID: $0.01 USDC per query after the daily free allowance. On a 402, pay the returned Solana memo and re-call with the SAME arguments plus payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses it.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | yes | awarding toptier agency name as USASpending labels it (e.g. "Department of Defense", "Department of Commerce"). |
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| fiscal_year | – | – | U.S. federal FY (e.g. 2026). Defaults to the current FY. |
| payment_tx | – | – | Solana tx signature, when re-calling after a 402. |
Structured output declared, but exposes no named fields.
No examples provided.
brief_summary ~169
Get the top 5 signals from today's brief as structured JSON — a cheap sample of the full daily_brief. Returns the day's highest-priority items (no prose) so an agent can decide whether to buy the full brief. PAID: $0.50 USDC (vs the full daily_brief price). Defaults to today (UTC). On a 402, pay the returned Solana memo and re-call with the SAME args plus payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses payment.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| date | – | – | brief date YYYY-MM-DD (default today, UTC). |
| payment_tx | – | – | Solana tx signature, when re-calling after a 402. |
Structured output declared, but exposes no named fields.
No examples provided.
contract_detail ~93
Get the full record for one U.S. federal government contract or solicitation by its solicitation number (for awards, the USASpending generated_internal_id) — including agency, NAICS code, value, and response deadline from SAM.gov / USASpending. FREE — no payment and no free-tier consumption.
| Name | Type | Req | Description |
|---|---|---|---|
| solicitation_number | string | yes | the natural key from a search_contracts result. |
Structured output declared, but exposes no named fields.
No examples provided.
daily_brief ~260
Get the curated daily U.S. federal government-contracts brief — the day's most significant federal procurement activity from SAM.gov and USASpending in one package: top new solicitations by value, solicitations with approaching response deadlines, major recent awards, and trending NAICS sectors + agencies. Each brief carries a provenance attestation so a buyer can verify it was produced by this server, unaltered. PAID: $10 USDC per brief. Defaults to today (UTC); a brief expires at the next midnight UTC. On a 402, pay the returned Solana memo and re-call with the SAME args plus payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses payment.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| date | – | – | brief date YYYY-MM-DD (default today, UTC). |
| payment_tx | – | – | Solana tx signature, when re-calling after a 402 (x402 rail). |
| stripe_token | – | – | Stripe Checkout Session id (cs_…), when re-calling after paying the Stripe payment link (alternative to x402). Can also be supplied via the X-Stripe-Token header. |
Structured output declared, but exposes no named fields.
No examples provided.
mint_info ~98
Get FoundryNet Data Network info + attestation / provenance details. FREE. Returns how to record verifiable provenance for your agent's government-contract / federal-procurement analysis (SAM.gov + USASpending), and the sister data servers in the network (brand-intel, patent-intel, financial-signals, weather-intel, cyber-intel, compliance, academic-intel, fact-check, oss-intel, social-intel).
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
search_contracts ~362
Search U.S. federal government contracts, solicitations, and awards by agency, value, NAICS code, keyword, state, or status — live from SAM.gov opportunities and USASpending/FPDS awards, newest-first. Covers federal procurement and government spending across one aggregated, deduplicated dataset of open SAM.gov solicitations and USASpending contract awards. PAID: $0.01 USDC per query after a daily free allowance. The first calls each day are free; once spent, the tool returns an HTTP-402 body with Solana payment instructions and a memo — pay it, then call again with the SAME arguments plus payment_tx=<signature>. Pass agent_id to scope your own free allowance; an Authorization: Bearer fnet_ key bypasses the paywall.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | – | – | awarding agency name, partial match (e.g. "Defense"). |
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| keyword | – | – | free-text matched against title + description (ILIKE). |
| limit | integer | – | max rows (1-100, default 25). |
| max_value | – | – | maximum award amount (USD). |
| min_value | – | – | minimum award amount (USD). |
| naics | – | – | exact 6-digit NAICS code (e.g. "334517"). |
| payment_tx | – | – | Solana tx signature, when re-calling after a 402. |
| posted_after | – | – | ISO date "YYYY-MM-DD"; only records posted on/after it. |
| state | – | – | 2-letter place-of-performance state code (e.g. "TX"). |
| status | – | – | one of "active", "closed", "awarded". |
Structured output declared, but exposes no named fields.
No examples provided.
trending_opportunities ~202
Analyze which sectors are seeing the most new U.S. federal government solicitations right now — buckets SAM.gov opportunities posted in the last `days` by NAICS code and ranks them by new-solicitation volume, with the agencies driving each. Surfaces emerging federal procurement demand. PAID: $0.01 USDC per query after the daily free allowance. On a 402, pay the returned Solana memo and re-call with the SAME arguments plus payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses it.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| days | integer | – | look-back window in days (1-365, default 30). |
| naics | – | – | optional exact 6-digit NAICS code to restrict to one sector. |
| payment_tx | – | – | Solana tx signature, when re-calling after a 402. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Government Contracts MCP server?
Government Contracts MCP is a hosted endpoint at https://gov-contracts-mcp-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · gov-contracts-mcp-production.up.railway.app
claude mcp add --transport http foundrynet-gov-contracts-mcp 'https://gov-contracts-mcp-production.up.railway.app/mcp'
What is the Government Contracts MCP server?
Government Contracts MCP is listed in the public MCP registry as io.github.FoundryNet/gov-contracts-mcp. Government contract search and federal procurement data: SAM.gov opportunities + USASpending awards. This page covers its hosted endpoint (https://gov-contracts-mcp-production.up.railway.app/mcp).
Is the Government Contracts MCP server safe to use?
Government Contracts MCP scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Government Contracts MCP server expose?
Government Contracts MCP exposes 7 tools: search_contracts, contract_detail, agency_spending, trending_opportunities, daily_brief, and 2 more. Their descriptions and schemas cost roughly 1,395 tokens of context every time the server is loaded.
Does the Government Contracts MCP server require authentication?
No. We connected to Government Contracts MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Government Contracts MCP server still maintained?
Government Contracts MCP has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 29 July 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.