Remote MCP · Endpoint

AI Blocks MCP server

No. AI Blocks answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://useaiblocks.com/mcp

The last check completed an MCP handshake.

Registry name
com.useaiblocks/library
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
329 ms
Tools exposed
22 tools
Uptime, last 30 days
4 checks from 4 checks
Described by its publisher as
Search and load free AI skills, workflows, agents and prompts. Read-only, no sign-in.
Listing
From the official MCP registry (active).
Recent checks of AI Blocks
CheckedResultHandshake
1 hour agoHandshake completed329 ms
3 days agoHandshake completed423 ms
12 days agoHandshake completed580 ms
13 days agoHandshake completed322 ms

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

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