Remote MCP · Endpoint

Scribiz MCP server

No. Scribiz answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://scribiz.com/mcp

The last check completed an MCP handshake.

Registry name
com.scribiz/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
753 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Transcripts, summaries, chapters and timestamped answers for video links, for AI agents.
Listing
From the official MCP registry (active).
Recent checks of Scribiz
CheckedResultHandshake
1 hour agoHandshake completed753 ms
2 days agoHandshake completed480 ms
5 days agoHandshake completed474 ms
7 days agoHandshake completed546 ms
9 days agoHandshake completed489 ms
11 days agoHandshake completed666 ms
13 days agoHandshake completed484 ms
15 days agoHandshake completed492 ms
17 days agoHandshake completed497 ms
19 days agoHandshake completed478 ms
20 days agoHandshake completed564 ms
21 days agoHandshake completed480 ms
23 days agoHandshake completed470 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 Scribiz and makes no claim about it beyond what these checks measured.