Remote MCP · Endpoint

CedarGrant MCP server

No. CedarGrant answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://cedargrant.com/mcp

The last check completed an MCP handshake.

Registry name
com.cedargrant/federal-grants
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
121 ms
Tools exposed
0 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Open federal grants from Grants.gov, plus a kit to draft and review applications in your assistant.
Listing
From the official MCP registry (active).
Recent checks of CedarGrant
CheckedResultHandshake
20 minutes agoHandshake completed121 ms
3 days agoHandshake completed80 ms
14 days agoHandshake completed111 ms
14 days agoHandshake completed196 ms
15 days agoHandshake completed162 ms
16 days agoHandshake completed90 ms
18 days agoHandshake completed91 ms
18 days agoHandshake completed86 ms
19 days agoHandshake completed76 ms
21 days agoHandshake completed106 ms
22 days agoHandshake completed206 ms
25 days agoHandshake completed139 ms
27 days agoHandshake completed78 ms

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

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 CedarGrant and makes no claim about it beyond what these checks measured.