Remote MCP · Endpoint

MEOM MCP server

No. MEOM answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://www.meom.fi/wp-json/meom-public/v1/mcp

The last check completed an MCP handshake.

Registry name
fi.meom/public
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
492 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only public info from MEOM, a Finnish B2B website agency: services, references, team, booking.
Listing
From the official MCP registry (active).
Recent checks of MEOM
CheckedResultHandshake
37 minutes agoHandshake completed492 ms
4 days agoHandshake completed529 ms
7 days agoHandshake completed508 ms
16 days agoHandshake completed482 ms
16 days agoHandshake completed508 ms
18 days agoHandshake completed543 ms
19 days agoHandshake completed520 ms
20 days agoHandshake completed514 ms
21 days agoHandshake completed576 ms
22 days agoHandshake completed493 ms
23 days agoHandshake completed518 ms
26 days agoHandshake completed505 ms
29 days agoHandshake completed608 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 MEOM and makes no claim about it beyond what these checks measured.