Remote MCP · Endpoint

UpFork MCP server

No. UpFork answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://upfork.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.upfork/upfork
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
303 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Search, view and install React + Tailwind CSS components and landing pages from UpFork.
Listing
From the official MCP registry (active).
Recent checks of UpFork
CheckedResultHandshake
1 hour agoHandshake completed303 ms
1 day agoHandshake completed328 ms
2 days agoHandshake completed550 ms
2 days agoHandshake completed309 ms
4 days agoHandshake completed475 ms
7 days agoHandshake completed347 ms
9 days agoHandshake completed297 ms
12 days agoHandshake completed290 ms
14 days agoHandshake completed279 ms
16 days agoHandshake completed308 ms
18 days agoHandshake completed339 ms
20 days agoHandshake completed287 ms
22 days agoHandshake completed312 ms
24 days agoHandshake completed273 ms
25 days agoHandshake completed304 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 UpFork and makes no claim about it beyond what these checks measured.