Remote MCP · Endpoint

Ohio Code MCP server

No. Ohio Code answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/ohio-code/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/ohio-code
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
62 ms
Tools exposed
37 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Ohio Revised Code — state statutes by citation.
Listing
From the official MCP registry (active).
Recent checks of Ohio Code
CheckedResultHandshake
1 hour agoHandshake completed62 ms
2 days agoHandshake completed63 ms
4 days agoHandshake completed57 ms
5 days agoHandshake completed61 ms
7 days agoHandshake completed82 ms
8 days agoHandshake completed53 ms
9 days agoHandshake completed53 ms
12 days agoHandshake completed47 ms
13 days agoHandshake completed41 ms
15 days agoHandshake completed80 ms
17 days agoHandshake completed53 ms
18 days agoHandshake completed41 ms
19 days agoHandshake completed40 ms
20 days agoHandshake completed100 ms
21 days agoHandshake completed41 ms
21 days agoHandshake completed52 ms
23 days agoHandshake completed62 ms

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

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