Developer · Remote MCP server
Sixta Connect
DBRE-grade SQL analysis inside any MCP client. No connection. No install. Paste a query.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.sixta/sixta-connect- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-06-22
- Updated
- 2026-06-22
- Publisher
- ai.sixta
- Namespace
- Namespace verified by the MCP Registry via the domain sixta.ai · how
- Website
- connect.sixta.ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://connect.sixta.ai/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Sixta Connect
Sixta Connect is a remote MCP server: there is nothing to install. Its endpoint is https://connect.sixta.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| SiteHealth MCPFull website health audit - SSL, DNS, DMARC/SPF/DKIM, performance, uptime, links. | Local · stdio |
| Sitelauncher MCP ServerDeploy live HTTPS websites in seconds. Instant subdomains or custom.xyz domains via USDC. | Local · stdio |
| SitelemetryOAuth website audits: security, SEO, AI visibility, integrations, accessibility and performance. | Remote · HTTPLive check: sign-in required |
| SiteVitalsMonitor website health, uptime, SEO, security and performance via your AI assistant. | Remote · SSELive check: ✗ no handshake |
| SkarnScans AI coding sessions and assistant configs for leaked secrets and risky hooks; local, redacted. | Local · stdio |
| SkeletIQHand a released SkeletIQ architecture to a coding agent: brief, build order, drift check. | Local · stdio |
| SkeletongraphZero-LLM structural code retrieval for AI coding agents, served over MCP. | Local · stdio |
| SkifflyDeploy apps and databases on Skiffly: projects, services, deployments, logs, variables, domains. | Remote · HTTPLive check: sign-in required |