Remote MCP · Endpoint

501c3.HELP nonprofit compliance MCP server

No. 501c3.HELP nonprofit compliance answered an MCP handshake 40 minutes ago.

UpLast checked 40 minutes ago

Server URL

https://mcp.501c3.help/

The last check completed an MCP handshake.

Registry name
help.501c3/compliance
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
182 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Nonprofit compliance rules for all 50 US states, each with its official citation and status
Listing
From the official MCP registry (active).
Recent checks of 501c3.HELP nonprofit compliance
CheckedResultHandshake
40 minutes agoHandshake completed182 ms
3 days agoHandshake completed494 ms
12 days agoHandshake completed133 ms
12 days agoHandshake completed48 ms
14 days agoHandshake completed43 ms
15 days agoHandshake completed69 ms
16 days agoHandshake completed60 ms
17 days agoHandshake completed45 ms
18 days agoHandshake completed295 ms
19 days agoHandshake completed90 ms
22 days agoHandshake completed86 ms
25 days agoHandshake completed157 ms
27 days agoHandshake completed317 ms
29 days agoHandshake completed51 ms

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

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 501c3.HELP nonprofit compliance and makes no claim about it beyond what these checks measured.