Remote MCP · Endpoint

Blankas MCP server

No. Blankas answered an MCP handshake 59 minutes ago.

UpLast checked 59 minutes ago

Server URL

https://pvl.app.n8n.cloud/mcp/blankas-mcp

The last check completed an MCP handshake.

Registry name
io.github.sirsinatoriai-png/blankas
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
446 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Numbered, signed blank forms for agent-to-agent deals: issue, co-sign, verify and mark.
Listing
From the official MCP registry (active).
Recent checks of Blankas
CheckedResultHandshake
59 minutes agoHandshake completed446 ms
9 days agoHandshake completed508 ms
10 days agoHandshake completed571 ms
11 days agoHandshake completed527 ms
12 days agoHandshake completed473 ms
14 days agoHandshake completed510 ms
14 days agoHandshake completed474 ms
15 days agoHandshake completed511 ms
17 days agoHandshake completed523 ms
19 days agoHandshake completed545 ms
21 days agoHandshake completed450 ms
24 days agoHandshake completed511 ms
26 days agoHandshake completed495 ms

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

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