usaspending-awards
https://usaspending-awards-production.up.railway.app
Registry code: 2183ca7b3503bf0d
See who wins US federal contracts and grants (USAspending.gov). $0.02/call via x402.
from a public catalogue that lists it, not from the operator
- endpoint
- https://usaspending-awards-production.up.railway.app/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is usaspending-awards live?
- Yes — it answered the hub's last check (checked 24m ago). It answered 100% of checks over the last 30 days.
- Is usaspending-awards free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does usaspending-awards have?
- 1 tool: search_us_federal_awards.
- Is usaspending-awards safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 1 tools
- unknown → live
Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 26 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-09
concentrated, shared-payto
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
search_us_federal_awards open 24m ago
Find out who wins US federal contracts and grants, or what a company has been awarded. Searches USAspending.gov (official US Treasury data) across contracts, IDVs, grants or loans by keyword, recipient, awarding agency, NAICS and date range: award ID, recipient, UEI, amount, agency, dates, description, place of performance and links. Use for competitor research, partner finding or US public-sector sales leads. $0.02 per call, USDC on Base (x402).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "days": { "type": "integer", "maximum": 3650, "minimum": 1, "description": "Look-back days (default 365)" }, "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Max results (default 20)" }, "naics": { "type": "string", "description": "NAICS codes" }, "query": { "type": "string", "description": "Keywords" }, "agency": { "type": "string", "description": "Awarding agency" }, "recipient": { "type": "string", "description": "Recipient name" }, "award_type": { "enum": [ "contracts", "idvs", "grants", "loans" ], "type": "string", "description": "Default contracts" }, "payment_signature": { "type": "string", "description": "x402 v2 PAYMENT-SIGNATURE header value. Omit to receive payment requirements." } }, "additionalProperties": false }arguments 49 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id2183ca7b3503bf0d.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/2183ca7b3503bf0d/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/2183ca7b3503bf0d?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.