Remote MCP · Endpoint
com.giveradar/charity-registry MCP server
No. com.giveradar/charity-registry answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://giveradar.com/mcp/
The last check completed an MCP handshake.
- Registry name
- com.giveradar/charity-registry
- Transport
- Streamable HTTP
- Protocol negotiated
- 2024-11-05
- Handshake latency
- 432 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Search, verify and compare 7.9M+ nonprofits from official charity registries in 100+ countries.
- Website
- https://giveradar.com/mcp/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 432 ms |
| 18 hours ago | Handshake completed | 402 ms |
| 2 days ago | Handshake completed | 400 ms |
| 3 days ago | Handshake completed | 432 ms |
| 4 days ago | Handshake completed | 544 ms |
| 5 days ago | Handshake completed | 417 ms |
| 6 days ago | Handshake completed | 421 ms |
| 7 days ago | Handshake completed | 244 ms |
| 10 days ago | Handshake completed | 440 ms |
| 13 days ago | Handshake completed | 425 ms |
| 15 days ago | Handshake completed | 399 ms |
| 17 days ago | Handshake completed | 410 ms |
| 19 days ago | Handshake completed | 399 ms |
| 21 days ago | Handshake completed | 411 ms |
| 23 days ago | Handshake completed | 414 ms |
| 25 days ago | Handshake completed | 395 ms |
| 27 days ago | Handshake completed | 494 ms |
| 28 days ago | Handshake completed | 404 ms |
| 29 days ago | Handshake completed | 360 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 com.giveradar/charity-registry and makes no claim about it beyond what these checks measured.