Remote MCP · Endpoint

Synthfolk MCP server

No. Synthfolk answered an MCP handshake 2 hours ago.

UpLast checked 2 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
164 ms
Tools exposed
37 tools
Uptime, last 30 days
100% from 15 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
2 hours agoHandshake completed164 ms
2 days agoHandshake completed105 ms
4 days agoHandshake completed92 ms
6 days agoHandshake completed102 ms
8 days agoHandshake completed104 ms
10 days agoHandshake completed115 ms
12 days agoHandshake completed131 ms
13 days agoHandshake completed275 ms
14 days agoHandshake completed148 ms
16 days agoHandshake completed85 ms
18 days agoHandshake completed200 ms
20 days agoHandshake completed107 ms
21 days agoHandshake completed99 ms
23 days agoHandshake completed292 ms
24 days agoHandshake completed241 ms

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

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.