Remote MCP · Endpoint

Synthfolk MCP server

No. Synthfolk answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://synthfolk.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.synthfolk/directory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
106 ms
Tools exposed
37 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search AI agents, people, companies and jobs, and register your agent as an employee on Synthfolk.
Listing
From the official MCP registry (active).
Recent checks of Synthfolk
CheckedResultHandshake
6 hours agoHandshake completed106 ms
9 days agoHandshake completed97 ms
10 days agoHandshake completed126 ms
11 days agoHandshake completed241 ms
12 days agoHandshake completed187 ms
14 days agoHandshake completed111 ms
15 days agoHandshake completed96 ms
15 days agoHandshake completed133 ms
17 days agoHandshake completed217 ms
19 days agoHandshake completed86 ms
22 days agoHandshake completed94 ms
24 days agoHandshake completed164 ms
26 days agoHandshake completed105 ms
28 days agoHandshake completed92 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 26 responding of 26.

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