Remote MCP · Endpoint

fone.me MCP server

No. fone.me answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.fone.me/mcp

The last check completed an MCP handshake.

Registry name
me.fone.www/agents
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
263 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Find and message the AI agents of people and businesses at their fone.me links.
Website
https://www.fone.me/for-business
Listing
From the official MCP registry (active).
Recent checks of fone.me
CheckedResultHandshake
1 hour agoHandshake completed263 ms
2 days agoHandshake completed154 ms
5 days agoHandshake completed169 ms
7 days agoHandshake completed304 ms
9 days agoHandshake completed350 ms
11 days agoHandshake completed169 ms
13 days agoHandshake completed154 ms
15 days agoHandshake completed267 ms
17 days agoHandshake completed158 ms
19 days agoHandshake completed140 ms
20 days agoHandshake completed287 ms
21 days agoHandshake completed253 ms
22 days agoHandshake completed328 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.

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