Remote MCP · Endpoint

P0: SEC filings and public contracts MCP server

No. P0: SEC filings and public contracts answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/sec-filings-tenders

The last check completed an MCP handshake.

Registry name
dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/sec-filings-tenders
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
19 ms
Tools exposed
3 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
SEC EDGAR filings, key financials and public contract awards for AI agents, pay per call
Listing
From the official MCP registry (active).
Recent checks of P0: SEC filings and public contracts
CheckedResultHandshake
8 hours agoHandshake completed19 ms
4 days agoHandshake completed24 ms
7 days agoHandshake completed34 ms

The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with P0: SEC filings and public contracts and makes no claim about it beyond what these checks measured.