Remote MCP · Endpoint

West Virginia Rules MCP server

No. West Virginia Rules answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://gateway.pipeworx.io/west-virginia-rules/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/west-virginia-rules
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
56 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
West Virginia Code of State Rules (CSR) -- the state's administrative rules.
Listing
From the official MCP registry (active).
Recent checks of West Virginia Rules
CheckedResultHandshake
7 hours agoHandshake completed56 ms
4 days agoHandshake completed82 ms
14 days agoHandshake completed109 ms
15 days agoHandshake completed162 ms
16 days agoHandshake completed786 ms
17 days agoHandshake completed1.01 s
19 days agoHandshake completed2.31 s
19 days agoHandshake completed827 ms
20 days agoHandshake completed736 ms
21 days agoHandshake completed172 ms
23 days agoHandshake completed186 ms
26 days agoHandshake completed68 ms
28 days agoHandshake completed91 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 West Virginia Rules and makes no claim about it beyond what these checks measured.