_ registry / mcp + a2a JSONRPC · checked 36m ago

fpds-mcp

https://fpds-mcp.mtree.workers.dev

Registry code: 96566714dc523277

api record

Pay-per-call MCP for the U.S. Federal Procurement Data System (FPDS-NG). Tools require x402 USDC payment on Base. tools/call returns a 402 envelope; settle X-PAYMENT and retry against the REST endpoint.

endpoint
https://fpds-mcp.mtree.workers.dev/
door code
a6230e58630b7891
protocol
JSONRPC ·0.2
authentication
x402
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is fpds-mcp live?
Yes — it answered the hub's last check (checked 36m ago). It answered 99% of checks over the last 30 days.
Is fpds-mcp free to use?
No — it charges per call, quoted in its own 402 answers.
What tools does fpds-mcp have?
2 tools: FPDS Vendor Contract Lookup, FPDS Federal Contract Search.
Is fpds-mcp 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.
reachable
live
uptime, 30 days
99.4%

90 days 99.3%· all time 99.7%

latency
350ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 956 checks · signed record
  • degraded → live
  • live → degraded· fetch failed
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
government & legal public records & government
used for
  • search us federal contract awards
  • look up federal contracts for a vendor
takes → gives
text → data
_ usage and payments 30 days

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 17 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
0

distinct

settlements
0

none in the window

received on chain
0 USDC

thin, shared-payto

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: no interface answered anonymously and the card declares security schemes

_ what it can do 2 tools
2 auth-required 2 of 2 classified

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.

  • contracts-by-vendor auth-required never probed

    Pull recent FPDS contract actions for a single vendor (by name) plus a quick aggregate (total obligated $, distinct agencies, distinct NAICS). Useful for vendor due-diligence agents and competitive-intel bots. $0.05/call.

    procurementgovernmentfederalfpdsvendordue-diligencecompetitive-intelligencesuppliergovcon

  • contracts-search auth-required never probed

    Search U.S. federal contract actions in FPDS-NG by description keyword, contracting agency code, NAICS, and signing-date window. Returns PIIDs, obligated amounts, vendors, NAICS, PSC, and direct FPDS UI links. $0.04/call.

    procurementgovernmentfederalfpdscontractsawardsnaicspscgovconvendor-due-diligence

_ try it over a2a through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 96566714dc523277.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/96566714dc523277/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/96566714dc523277/badge.svg)](https://brick.blue/agent/96566714dc523277?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.

_ how we knowoff the mcp door
card completeness
60%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.