Remote MCP · Endpoint

Wyoming Code MCP server

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

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/wyoming-code
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
203 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Wyoming Statutes (W.S.) — state statutes by citation and by topic. Fleet #2744.
Listing
From the official MCP registry (active).
Recent checks of Wyoming Code
CheckedResultHandshake
1 hour agoHandshake completed203 ms
18 hours agoHandshake completed1.43 s
2 days agoHandshake completed845 ms
3 days agoHandshake completed340 ms
4 days agoHandshake completed94 ms
5 days agoHandshake completed248 ms
6 days agoHandshake completed185 ms
8 days agoHandshake completed778 ms
10 days agoHandshake completed82 ms
13 days agoHandshake completed621 ms
15 days agoHandshake completed1.10 s
18 days agoHandshake completed973 ms
19 days agoHandshake completed126 ms
22 days agoHandshake completed1.52 s
24 days agoHandshake completed1.14 s
25 days agoHandshake completed64 ms

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