Remote MCP · Endpoint

Hex.pm MCP MCP server

No. Hex.pm MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://hexpm-mcp.fly.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.joshrotenberg/hexpm-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
3.85 s
Tools exposed
24 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
MCP server for hex.pm and hexdocs.pm: search, inspect, compare, and audit Elixir packages
Website
https://github.com/joshrotenberg/hexpm-mcp
Repository
https://github.com/joshrotenberg/hexpm-mcp
Listing
From the official MCP registry (active).
Recent checks of Hex.pm MCP
CheckedResultHandshake
1 hour agoHandshake completed3.85 s
2 days agoHandshake completed4.49 s
4 days agoHandshake completed3.83 s
5 days agoHandshake completed115 ms
7 days agoHandshake completed136 ms
8 days agoHandshake completed100 ms
9 days agoHandshake completed164 ms
12 days agoHandshake completed156 ms
13 days agoHandshake completed98 ms
15 days agoHandshake completed164 ms
17 days agoHandshake completed167 ms
18 days agoHandshake completed104 ms
19 days agoHandshake completed170 ms
20 days agoHandshake completed167 ms
20 days agoHandshake completed120 ms
21 days agoHandshake completed97 ms
23 days agoHandshake completed111 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Hex.pm MCP and makes no claim about it beyond what these checks measured.