Remote MCP · Endpoint

Mockdata MCP server

No. Mockdata answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://gateway.pipeworx.io/mockdata/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/mockdata
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
57 ms
Tools exposed
38 tools
Uptime, last 30 days
93.8% from 16 checks
Described by its publisher as
Mock data generator MCP.
Listing
From the official MCP registry (active).
Recent checks of Mockdata
CheckedResultHandshake
2 days agoHandshake completed57 ms
4 days agoHandshake completed50 ms
5 days agoHandshake completed61 ms
7 days agoHandshake completed79 ms
8 days agoHandshake completed45 ms
9 days agoHandshake completed48 ms
12 days agoHandshake completed45 ms
13 days agoHandshake completed49 ms
15 days agoFailed - the request timed out—
17 days agoHandshake completed66 ms
18 days agoHandshake completed39 ms
19 days agoHandshake completed66 ms
20 days agoHandshake completed42 ms
20 days agoHandshake completed36 ms
21 days agoHandshake completed43 ms
23 days agoHandshake completed48 ms

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

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