Developer · Remote MCP server
Synapse - GEO Growth Layer
Lints + auto-fixes how AI coding agents discover any new product. 24 rules, 6 tools, score 0-100.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.calvinling2021-star/synapse-geo- Version
- 0.1.2
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-05-14
- Updated
- 2026-05-14
- Publisher
- calvinling2021-star (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/calvinling2021-star) · how
- Website
- runsynapse.dev
- Repository
- github.com/calvinling2021-star/synapse
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://runsynapse.dev/api/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 404)
- Handshake
- HTTP 404
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @calvin8miles/mcp-server | 0.1.2 | stdio |
How to connect Synapse - GEO Growth Layer
Synapse - GEO Growth Layer is a remote MCP server: there is nothing to install. Its endpoint is https://runsynapse.dev/api/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.
It can also run locally from a Node.js package published to the npm registry: @calvin8miles/mcp-server version 0.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @calvin8miles/mcp-server@0.1.2. It reads these environment variables: SYNAPSE_API_KEY (secret) and SYNAPSE_BACKEND; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"synapse-geo": {
"command": "npx",
"args": [
"-y",
"@calvin8miles/mcp-server@0.1.2"
],
"env": {
"SYNAPSE_API_KEY": "<secret>",
"SYNAPSE_BACKEND": "<value>"
}
}
}
}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 |
|---|---|
| Symfony Agent MCPRead-only Symfony introspection: routes, services, entities, Doctrine, security, Twig and more. | Local · stdio |
| SymvantaHosted code graph over MCP: exact callers, dependencies, and cross-repo blast radius for AI agents. | Remote · HTTPLive check: ✓ handshake |
| SynapSynap (pool.linkrra.com/v1), Linkrra's OpenAI-compatible LLM API, as an MCP server. | Remote · HTTPLive check: ✓ handshake |
| Synap MemoryPersistent memory for AI agents - log and recall conversation context over MCP. | Remote · HTTPLive check: ✓ handshake |
| 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 |