io.github.JusticeUA/connecticut-company-check
Connecticut Company Check
Is the Connecticut Company Check MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-10.
Connecticut company checks by Business ID: status, legal form, dissolution flags, LEI and sanctions.
needs auth probed 2026-11-15 · unchanged since 2026-11-10 · HTTP 401
Streamable HTTP error: Error POSTing to endpoint: {
"error": {
"type": "api-token-missing",
"message": "This is a standby Actor. To use it, you need t- Endpoint
- https://kyb-data--connecticut-company-check.apify.actor/mcp (streamable-http)
- Host
- kyb-data--connecticut-company-check.apify.actor
- Getting access
- The server answers HTTP 401 with no WWW-Authenticate header and no OAuth metadata, so the publisher's documentation is the only guide.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://apify.com/kyb-data/connecticut-company-check
- Registry
- active, updated 2026-11-09 · registry entry
Compare this server with others.
More servers
Servers that mention connecticut.
- Connecticut Code io.github.pipeworx-io/connecticut-code · alive
- Ct Dmv io.github.pipeworx-io/ct-dmv · alive
- Data Connecticut io.github.pipeworx-io/data-connecticut · not MCP
- Mode VC Atlas: Brighton Park Capital Partner & Fund Intelligence com.modevc/firm-brighton-park-capital · alive
- DrMaker3D: custom 3D printing, figures, cookie cutters and gifts com.drmaker3d/shop · alive
- CT Injury Cases com.ctinjurycases/ct-injury-cases · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.