Remote MCP · Endpoint
Federal Grants — find funding you are actually eligible for MCP server
No. Federal Grants — find funding you are actually eligible for answered an MCP handshake 25 minutes ago.
UpLast checked 25 minutes ago
Server URL
https://x402-seller-m8nx.onrender.com/grants/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.wyattpalm2-eng/federal-grants
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 125 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 5 checks
- Described by its publisher as
- Find US federal grants your organization is actually eligible to apply for. Free, no API key.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 25 minutes ago | Handshake completed | 125 ms |
| 1 day ago | Handshake completed | 421 ms |
| 1 day ago | Handshake completed | 101 ms |
| 2 days ago | Handshake completed | 135 ms |
| 3 days ago | Handshake completed | 133 ms |
The last 5 checks. Full history is kept for 30 days; the all-time counter stands at 5 responding of 5.
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 Federal Grants — find funding you are actually eligible for and makes no claim about it beyond what these checks measured.