Remote MCP · Endpoint

Criptograma MCP server

No. Criptograma answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://words-nine-gamma.vercel.app/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.rlphillips/criptograma
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.92 s
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Daily acrostics ES/EN/FR. Preview free; playable $0.01, solved $0.03 USDC (x402, Base).
Listing
From the official MCP registry (active).
Recent checks of Criptograma
CheckedResultHandshake
1 hour agoHandshake completed1.92 s
2 days agoHandshake completed946 ms
4 days agoHandshake completed1.52 s
6 days agoHandshake completed293 ms
8 days agoHandshake completed2.17 s
10 days agoHandshake completed836 ms
12 days agoHandshake completed1.73 s
14 days agoHandshake completed1.04 s
15 days agoHandshake completed143 ms
16 days agoHandshake completed787 ms
18 days agoHandshake completed151 ms
20 days agoHandshake completed1.57 s
22 days agoHandshake completed111 ms
24 days agoHandshake completed1.07 s

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

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