Remote MCP · Endpoint

Georgia Code MCP server

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

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/georgia-code
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
96 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Official Code of Georgia Annotated (O.C.G.A.) — Georgia state statutes by citation, topic search…
Listing
From the official MCP registry (active).
Recent checks of Georgia Code
CheckedResultHandshake
1 hour agoHandshake completed96 ms
1 day agoHandshake completed125 ms
4 days agoHandshake completed169 ms
6 days agoHandshake completed60 ms
9 days agoHandshake completed80 ms
11 days agoHandshake completed484 ms
13 days agoHandshake completed76 ms
15 days agoHandshake completed69 ms
17 days agoHandshake completed62 ms
19 days agoHandshake completed877 ms
21 days agoHandshake completed1.05 s
23 days agoHandshake completed789 ms
23 days agoHandshake completed413 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 Georgia Code and makes no claim about it beyond what these checks measured.