Remote MCP · Endpoint

io.github.ryuamarines/json-schema-validator MCP server

No — it is up, but it requires credentials. io.github.ryuamarines/json-schema-validator answered 1 hour ago with an authentication challenge rather than a session.

Auth requiredLast checked 1 hour ago

Server URL

https://faceted-napped-debtless.ngrok-free.dev/json-schema-validator/mcp

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
io.github.ryuamarines/json-schema-validator
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
1 tool
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Validates JSON against a JSON Schema, lists violations. x402 payment required (testnet USDC).
Listing
From the official MCP registry (active).
Recent checks of io.github.ryuamarines/json-schema-validator
CheckedResultHandshake
1 hour agoCredentials required—
1 day agoHandshake completed403 ms
2 days agoHandshake completed401 ms
3 days agoHandshake completed370 ms
4 days agoCredentials required—
5 days agoCredentials required—
6 days agoCredentials required—
9 days agoCredentials required—
11 days agoHandshake completed433 ms
14 days agoHandshake completed355 ms
16 days agoHandshake completed449 ms
18 days agoHandshake completed343 ms
20 days agoHandshake completed333 ms
22 days agoHandshake completed320 ms
24 days agoHandshake completed340 ms
26 days agoHandshake completed344 ms
27 days agoHandshake completed334 ms
29 days agoHandshake completed325 ms

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

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 io.github.ryuamarines/json-schema-validator and makes no claim about it beyond what these checks measured.