Developer · Remote MCP server
Synaptic Code Intelligence
Code intelligence for repository graphs, change impact, test selection, and engineering memory.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ColinVaughn/synaptic- Version
- 1.2.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-08
- Updated
- 2026-09-08
- Publisher
- ColinVaughn (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/ColinVaughn) · how
- Website
- synapticgraph.com
- Repository
- github.com/ColinVaughn/Synaptic
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://synapticgraph.com/api/mcp/projects/{project_id} | Authorization (required, secret) |
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.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
How to connect Synaptic Code Intelligence
Synaptic Code Intelligence is a remote MCP server: there is nothing to install. Its endpoint is https://synapticgraph.com/api/mcp/projects/{project_id}, 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.
The URL contains placeholders to fill in before connecting: {project_id}.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry, not tested here. 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 |
|---|---|
| Synapse AuditAI-Powered Security Scanner for LLMs. Detects vulnerabilities and syncs with SynapseAudit. | Local · stdio |
| Synapse Layer - Trust Infrastructure for AI AgentsMCP-native Trust Infrastructure for AI Agents. Persistent encrypted memory with Trust Quotient. | Remote · HTTPLive check: ✓ handshake |
| Synapse RMCPHost, Docker, Compose, SSH, logs, ZFS, and file operations over MCP and CLI. | Local · stdio |
| Synapse RMCPRust MCP and CLI server for Docker, host inspection, SSH, logs, ZFS, and safe file operations. | Local · stdio |
| Syncbridge MCPBridges AI chat interfaces with Claude Code CLI via shared markdown control files. | Local · stdio |
| SynchronexConnect any AI agent to your Synchronex workspace - portable memory, decisions, and workers. | Local · stdio |
| Syncro MCPEvery Syncro PSA and RMM workflow in your terminal, plus a local database, offline search, and. | Local · stdio |
| Syndicate LinksCommission infrastructure for AI commerce - program discovery, attribution, and settlement. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |