Remote MCP · Endpoint
PennyQuery MCP server
No. PennyQuery answered an MCP handshake 20 minutes ago.
UpLast checked 20 minutes ago
Server URL
https://api.pennyquery.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.carpdroid-commits/agent-data-broker
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 176 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 90.9% from 11 checks
- Described by its publisher as
- Company enrichment + SEC EDGAR filings, financials, insider trades for agents; $0.01 USDC via x402
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 20 minutes ago | Handshake completed | 176 ms |
| 3 days ago | Handshake completed | 223 ms |
| 14 days ago | Handshake completed | 193 ms |
| 14 days ago | Handshake completed | 211 ms |
| 15 days ago | Handshake completed | 199 ms |
| 16 days ago | Handshake completed | 241 ms |
| 18 days ago | Handshake completed | 158 ms |
| 18 days ago | Handshake completed | 143 ms |
| 19 days ago | Handshake completed | 332 ms |
| 21 days ago | Handshake completed | 235 ms |
| 22 days ago | Failed - the request timed out | — |
The last 11 checks. Full history is kept for 30 days; the all-time counter stands at 10 responding of 11.
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 PennyQuery and makes no claim about it beyond what these checks measured.