Remote MCP · Endpoint

The2410 Projects MCP server

No. The2410 Projects answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://projects.the2410.com/mcp

The last check completed an MCP handshake.

Registry name
com.the2410/projects
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
220 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Plan custom software with The2410: fit check, budget, timeline, inquiry and consultation booking.
Listing
From the official MCP registry (active).
Recent checks of The2410 Projects
CheckedResultHandshake
13 minutes agoHandshake completed220 ms
9 days agoHandshake completed232 ms
9 days agoHandshake completed199 ms
11 days agoHandshake completed240 ms
12 days agoHandshake completed309 ms
13 days agoHandshake completed303 ms
14 days agoHandshake completed201 ms
15 days agoHandshake completed212 ms
16 days agoHandshake completed516 ms
19 days agoHandshake completed220 ms
21 days agoHandshake completed208 ms
24 days agoHandshake completed302 ms
26 days agoHandshake completed268 ms
28 days agoHandshake completed235 ms

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

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