ConnectSecure MCP
Vulnerability management across all ConnectSecure clients: exposure ranking, CVE impact, blind spots
The current version, v0.1.1, was published to the official MCP registry on 2026-10-16. It is distributed through a declared package, filed under Security by this index, and declares 10 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using ConnectSecure MCP in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.descriptionpassINFOevidence“Tool provides vulnerability management for ConnectSecure clients.”via static_description
- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
- - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.
That verdict was true at screening time (snapshot 2026-10-20).
Contracts can change after screening, with no version bump. The gate pins ConnectSecure MCP’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for ConnectSecure MCP](https://mcpindex.ai/server/io-github-servosity-connectsecure-mcp) - screening verdict, registry provenance, and contract drift monitoring.<a href="https://mcpindex.ai/server/io-github-servosity-connectsecure-mcp">Independent trust record for ConnectSecure MCP</a> - screening verdict, registry provenance, and contract drift monitoring.A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-servosity-connectsecure-mcp)<a href="https://mcpindex.ai/server/io-github-servosity-connectsecure-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-servosity-connectsecure-mcp" alt="mcpindex verdict" height="20" /></a>CONNECTSECURE_BASE_URLYour tenant's pod URL, e.g. https://pod104.myconnectsecure.com (Profile > API Documentation in the portal). Each tenant has its own pod; there is no working default.
CONNECTSECURE_TENANTTenant name you type on the ConnectSecure portal login screen.
CONNECTSECURE_CLIENT_IDAPI client ID from Settings > Users > (user) > API Key.
CONNECTSECURE_CLIENT_SECRETAPI client secret from Settings > Users > (user) > API Key.
CONNECTSECURE_ACCESS_TOKENOptional. A pre-minted JWT from /w/authorize; while it is unexpired it is used instead of minting one. The tenant, client ID and secret are still needed so the CLI can mint a fresh token once it expires.
CONNECTSECURE_USER_IDOptional user_id from /w/authorize. Only needed with a pre-minted access token; minting fills it automatically.
CONNECTSECURE_MCP_READ_ONLYSet to 1 to make the MCP server refuse every write and hide the sync, export and tail tools (import is never an MCP tool). Credential reads are still answered.
CONNECTSECURE_USER_AGENTOverrides the User-Agent the CLI sends on ConnectSecure requests.
CONNECTSECURE_MCP_HTTP_TOKENRequired only when running the MCP server with --transport http. Not needed for the default local stdio transport.
PRINTING_PRESS_CLIENT_PROFILEOptional: binds the MCP server to a tenant-gated Printing Press client profile. This connector registers none; leave unset.
Sourced, scored comparisons of crypto exchanges, wallets, savings accounts and brokerages.
Verified German HR data with legal source: minimum wage, social security, holidays, notice periods
WatchGuard Cloud Firebox, Endpoint Security, ThreatSync, NDR and AuthPoint APIs for every customer