Remote MCP · Endpoint

Forkmate MCP server

No. Forkmate answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://mcp.forkmate.ai/

The last check completed an MCP handshake.

Registry name
ai.forkmate/forkmate
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
253 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Free AI calorie & macro tracker: tell your AI what you ate and it logs it to your private food diary
Listing
From the official MCP registry (active).
Recent checks of Forkmate
CheckedResultHandshake
8 hours agoHandshake completed253 ms
2 days agoHandshake completed58 ms
4 days agoHandshake completed150 ms
5 days agoHandshake completed125 ms
7 days agoHandshake completed119 ms
8 days agoHandshake completed230 ms
9 days agoHandshake completed76 ms
12 days agoHandshake completed40 ms
13 days agoHandshake completed73 ms
15 days agoHandshake completed74 ms
16 days agoHandshake completed61 ms
17 days agoHandshake completed64 ms
18 days agoHandshake completed73 ms
19 days agoHandshake completed71 ms
20 days agoHandshake completed114 ms
21 days agoHandshake completed29 ms
23 days agoHandshake completed109 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 Forkmate and makes no claim about it beyond what these checks measured.