Remote MCP · Endpoint

tinyfish MCP server

Yes, as of 5 hours ago: the server returned an HTTP error.

DownLast checked 5 hours ago

Server URL

https://www.doc2mcp.site/api/mcp/1048e4a1-f431-4694-8297-c573624c4ed4/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.doc2mcp/tinyfish
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Not measured yet
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
MCP server for tinyfish documentation, generated by doc2mcp.
Listing
From the official MCP registry (active).
Recent checks of tinyfish
CheckedResultHandshake
5 hours agoFailed - the server returned an HTTP error—
9 days agoHandshake completed272 ms
10 days agoHandshake completed294 ms
11 days agoHandshake completed1.08 s
12 days agoHandshake completed314 ms
14 days agoHandshake completed267 ms
14 days agoHandshake completed355 ms
15 days agoHandshake completed443 ms
17 days agoHandshake completed299 ms
19 days agoHandshake completed277 ms
21 days agoHandshake completed347 ms
24 days agoHandshake completed331 ms
26 days agoHandshake completed291 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 12 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 tinyfish and makes no claim about it beyond what these checks measured.