Remote MCP · Endpoint

Dc Code MCP server

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

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/dc-code
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
114 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
District of Columbia Code — DC statutes by citation, and topic/chapter search. Fleet #2887 (one of…
Listing
From the official MCP registry (active).
Recent checks of Dc Code
CheckedResultHandshake
1 hour agoHandshake completed114 ms
1 day agoHandshake completed207 ms
2 days agoHandshake completed98 ms
2 days agoHandshake completed90 ms
4 days agoHandshake completed134 ms
6 days agoHandshake completed61 ms
9 days agoHandshake completed143 ms
12 days agoHandshake completed80 ms
14 days agoHandshake completed2.96 s
16 days agoHandshake completed91 ms
18 days agoHandshake completed1.00 s
20 days agoHandshake completed1.48 s
22 days agoHandshake completed2.75 s
24 days agoHandshake completed217 ms

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

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