Remote MCP · Endpoint

io.github.cyanheads/paleobiology-mcp-server MCP server

No. io.github.cyanheads/paleobiology-mcp-server answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://paleobiology.caseyjhand.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.cyanheads/paleobiology-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
152 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search fossil occurrences, taxon ranges, diversity through deep time, and the geologic time scale.
Listing
From the official MCP registry (active).
Recent checks of io.github.cyanheads/paleobiology-mcp-server
CheckedResultHandshake
2 hours agoHandshake completed152 ms
2 days agoHandshake completed137 ms
4 days agoHandshake completed107 ms
5 days agoHandshake completed98 ms
7 days agoHandshake completed143 ms
8 days agoHandshake completed611 ms
9 days agoHandshake completed153 ms
12 days agoHandshake completed104 ms
13 days agoHandshake completed205 ms
15 days agoHandshake completed154 ms
17 days agoHandshake completed129 ms
18 days agoHandshake completed107 ms
19 days agoHandshake completed120 ms
20 days agoHandshake completed101 ms
20 days agoHandshake completed101 ms
21 days agoHandshake completed111 ms
23 days agoHandshake completed143 ms

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

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 io.github.cyanheads/paleobiology-mcp-server and makes no claim about it beyond what these checks measured.