Remote MCP · Endpoint

Alabama Code MCP server

No. Alabama Code answered an MCP handshake 17 hours ago.

UpLast checked 17 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/alabama-code
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
41 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Code of Alabama 1975 — state statutes by citation and by topic. Fleet #2752. Query-arg fix: fleet…
Listing
From the official MCP registry (active).
Recent checks of Alabama Code
CheckedResultHandshake
17 hours agoHandshake completed41 ms
4 days agoHandshake completed153 ms
8 days agoHandshake completed149 ms
17 days agoHandshake completed110 ms
17 days agoHandshake completed79 ms
19 days agoHandshake completed158 ms
20 days agoHandshake completed193 ms
21 days agoHandshake completed890 ms
22 days agoHandshake completed123 ms
23 days agoHandshake completed1.14 s
24 days agoHandshake completed1.33 s
27 days agoHandshake completed84 ms
30 days agoHandshake completed387 ms

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

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