mcpbeat Sign in

Synapse — GEO Growth Layer MCP Server

by calvinling2021-star Your server? Claim it
not responding

Synapse — GEO Growth Layer is listed as active in the registry but did not answer our last check. 27 installs a week from npm. Last commit 14 May 2026.

Lints + auto-fixes how AI coding agents discover any new product. 24 rules, 6 tools, score 0-100.

Installs per day peak 12 · avg 4 · +90% w/w
a month agotoday
Uptime history 51 days of history · worst day 0%
51 days agonow
0.0%
Uptime 24h
0 of 91 checks
Tools
hidden behind auth
257 ms
Response time
average over 24h
27
Installs / week
npm and PyPI

What the code does

We read the source, 17 h ago · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Builds a file path from a variable packages/geo-lint/src/framework.ts:42
    const p = path.join(root, rel);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add synapse-geo --transport http https://runsynapse.dev/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "synapse-geo": {
      "url": "https://runsynapse.dev/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.synapse-geo]
url = "https://runsynapse.dev/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "synapse-geo": {
      "url": "https://runsynapse.dev/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "synapse-geo": {
      "url": "https://runsynapse.dev/api/mcp"
    }
  }
}

This one needs environment variables set before it will start: SYNAPSE_API_KEY (Optional. Required only for geo_fix and geo_track_init tools. Read-only tools work without a key.), SYNAPSE_BACKEND (Override the Synapse backend URL. Defaults to https://runsynapse.dev.). The author declared them in the registry entry; get the values from the project itself.

Endpoints

URLTransportStateLatencyChecked
https://runsynapse.dev/api/mcp streamable-http answering 257 ms 6 min ago

Alternatives to Synapse — GEO Growth Layer

same job, measured the same way
Scopewalker MCP
by timohaa

Codebase analysis tools for AI agents: complexity, prop drilling, doc coverage, code smells.

132 installs/wk local only
Automatised Pipeline
by cdeust

Codebase intelligence MCP server — index any repo into a property graph; 26 tools for agents.

local only
Code Synapse — Fit Repo Finder
by leewaystudio

Finds real, maintained open-source repos that fit your project. MCP grounding for coding agents.

2 tools answering
Rams
by rams

Design review for UI code: 291 rules, scored 0-100 with fixes and git-applyable patches.

4 tools answering
SQLGuard — permission before production writes
by sqlguard

AI agents need permission before production SQL writes. Pilot $100 · Gateway $299. Lint≠authorize.

24 tools answering
Chestnyi Znak MCP Server
by woyaxnini

MCP server for Chestnyi Znak — Russian product marking system. 10 tools: codes, documents, stocks.

36 installs/wk local only
AI Architect MCP Codebase
by cdeust

Codebase intelligence MCP — index any repo into a property graph; 26 tools for agents.

local only
consolelog dev tools
by mbdev3

Deterministic dev tools for AI agents over MCP: hashing, encoding, formatting, codegen, and more.

17 installs/wk local only

Synapse — GEO Growth Layer — questions

Answers built from our own checks of this server.

Is Synapse — GEO Growth Layer working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 257 ms. The bar chart above shows every period we have measured.
The registry lists Synapse — GEO Growth Layer as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Synapse — GEO Growth Layer?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Synapse — GEO Growth Layer need an API key?
No. Synapse — GEO Growth Layer completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.
How many people use Synapse — GEO Growth Layer?
The npm package @calvin8miles/mcp-server was installed 27 times in the last week. Week over week that is +90%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Synapse — GEO Growth Layer open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.