Remote MCP · Endpoint

com.saymetry/saymetry MCP server

No. com.saymetry/saymetry answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://saymetry.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.saymetry/saymetry
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
68 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Measure what ChatGPT, Claude, Gemini and 4 more AI engines say about any business. No auth.
Website
https://saymetry.com/agents
Listing
From the official MCP registry (active).
Recent checks of com.saymetry/saymetry
CheckedResultHandshake
1 hour agoHandshake completed68 ms
2 days agoHandshake completed195 ms
4 days agoHandshake completed70 ms
5 days agoHandshake completed127 ms
7 days agoHandshake completed109 ms
8 days agoHandshake completed82 ms
9 days agoHandshake completed74 ms
12 days agoHandshake completed72 ms
13 days agoHandshake completed84 ms
15 days agoHandshake completed66 ms
16 days agoHandshake completed88 ms
18 days agoHandshake completed238 ms
19 days agoHandshake completed72 ms
20 days agoHandshake completed66 ms
20 days agoHandshake completed361 ms
21 days agoHandshake completed58 ms
22 days agoHandshake completed101 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with com.saymetry/saymetry and makes no claim about it beyond what these checks measured.