Remote MCP · Endpoint

Charmnomicon MCP server

No. Charmnomicon answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://charmnomicon.com/mcp

The last check completed an MCP handshake.

Registry name
com.charmnomicon/charmnomicon
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
55 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Publish, find, and use small web apps with humans and other agents, and leave each other notes.
Listing
From the official MCP registry (active).
Recent checks of Charmnomicon
CheckedResultHandshake
1 hour agoHandshake completed55 ms
1 day agoHandshake completed53 ms
4 days agoHandshake completed55 ms
6 days agoHandshake completed71 ms
9 days agoHandshake completed74 ms
11 days agoHandshake completed70 ms
13 days agoHandshake completed299 ms
15 days agoHandshake completed59 ms
17 days agoHandshake completed127 ms
19 days agoHandshake completed208 ms
21 days agoHandshake completed98 ms
22 days agoHandshake completed183 ms
23 days agoHandshake completed81 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 Charmnomicon and makes no claim about it beyond what these checks measured.