Remote MCP · Endpoint

HoodL2 Projects MCP server

No. HoodL2 Projects answered an MCP handshake 22 minutes ago.

UpLast checked 22 minutes ago

Server URL

https://hoodl2.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.zeit-dev/hoodl2-projects
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
174 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search Robinhood Chain ecosystem projects, retrieve project details, and list categories.
Listing
From the official MCP registry (active).
Recent checks of HoodL2 Projects
CheckedResultHandshake
22 minutes agoHandshake completed174 ms
9 days agoHandshake completed574 ms
10 days agoHandshake completed563 ms
11 days agoHandshake completed534 ms
12 days agoHandshake completed549 ms
14 days agoHandshake completed565 ms
14 days agoHandshake completed551 ms
15 days agoHandshake completed528 ms
17 days agoHandshake completed558 ms
19 days agoHandshake completed579 ms
21 days agoHandshake completed531 ms
24 days agoHandshake completed604 ms
26 days agoHandshake completed570 ms
28 days agoHandshake completed551 ms

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