Remote MCP · Endpoint

Hokmah MCP server

No. Hokmah answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://hokmah.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.davidangularme/hokmah
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
626 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
AI Agent with Architectural Memory. Impact analysis (free), tests and code from the graph (pro).
Listing
From the official MCP registry (active).
Recent checks of Hokmah
CheckedResultHandshake
2 hours agoHandshake completed626 ms
2 days agoHandshake completed441 ms
4 days agoHandshake completed441 ms
5 days agoHandshake completed132 ms
7 days agoHandshake completed450 ms
8 days agoHandshake completed385 ms
9 days agoHandshake completed403 ms
12 days agoHandshake completed430 ms
13 days agoHandshake completed464 ms
15 days agoHandshake completed447 ms
17 days agoHandshake completed435 ms
18 days agoHandshake completed406 ms
19 days agoHandshake completed408 ms
20 days agoHandshake completed503 ms
20 days agoHandshake completed424 ms
21 days agoHandshake completed400 ms
23 days agoHandshake completed412 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 Hokmah and makes no claim about it beyond what these checks measured.