Remote MCP · Endpoint

org.opennih/opennih MCP server

No. org.opennih/opennih answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.opennih.org/mcp

The last check completed an MCP handshake.

Registry name
org.opennih/opennih
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
2.20 s
Tools exposed
14 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Entity-resolved NIH grant corpus (FY1985-2026) via 14 read-only, provenance-carrying MCP tools.
Listing
From the official MCP registry (active).
Recent checks of org.opennih/opennih
CheckedResultHandshake
1 hour agoHandshake completed2.20 s
18 hours agoHandshake completed301 ms
2 days agoHandshake completed89 ms
3 days agoHandshake completed95 ms
4 days agoHandshake completed120 ms
5 days agoHandshake completed98 ms
6 days agoHandshake completed281 ms
7 days agoHandshake completed188 ms
10 days agoHandshake completed211 ms
13 days agoHandshake completed570 ms
15 days agoHandshake completed64 ms
17 days agoHandshake completed76 ms
19 days agoHandshake completed61 ms
21 days agoHandshake completed60 ms
23 days agoHandshake completed104 ms

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

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