Remote MCP · Endpoint

Data Connecticut MCP server

No. Data Connecticut answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/data-connecticut/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/data-connecticut
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
107 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Connecticut Open Data — US government open data (data.ct.gov) via the Socrata SoQL API: state…
Website
https://pipeworx.io/packs/data-connecticut
Repository
https://github.com/pipeworx-io/mcp-data-connecticut
Listing
From the official MCP registry (active).
Recent checks of Data Connecticut
CheckedResultHandshake
1 hour agoHandshake completed107 ms
1 day agoHandshake completed401 ms
2 days agoHandshake completed66 ms
3 days agoHandshake completed95 ms
4 days agoHandshake completed93 ms
5 days agoHandshake completed146 ms
6 days agoHandshake completed135 ms
9 days agoHandshake completed99 ms
12 days agoHandshake completed55 ms
14 days agoHandshake completed61 ms
16 days agoHandshake completed73 ms
18 days agoHandshake completed67 ms
20 days agoHandshake completed86 ms
23 days agoHandshake completed72 ms
25 days agoHandshake completed54 ms
26 days agoHandshake completed58 ms
28 days agoHandshake completed52 ms
29 days agoHandshake completed238 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Data Connecticut and makes no claim about it beyond what these checks measured.