Remote MCP · Endpoint

Achromat MOM MCP server

No. Achromat MOM answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://mom.achromat.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.achromat/mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
381 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Recall and calibrate policy-compliant tool-call arguments before execution. Does not run the tool.
Listing
From the official MCP registry (active).
Recent checks of Achromat MOM
CheckedResultHandshake
42 minutes agoHandshake completed381 ms
3 days agoHandshake completed233 ms
13 days agoHandshake completed189 ms
13 days agoHandshake completed179 ms
15 days agoHandshake completed255 ms
15 days agoHandshake completed124 ms
17 days agoHandshake completed149 ms
18 days agoHandshake completed144 ms
18 days agoHandshake completed125 ms
20 days agoHandshake completed181 ms
22 days agoHandshake completed226 ms
25 days agoHandshake completed145 ms
27 days agoHandshake completed227 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 Achromat MOM and makes no claim about it beyond what these checks measured.