Synapse MCP server
io.github.Aadeshjain25/synapseAadeshjain25streamable-httpv1.0.0Scanned
Codebase memory for AI coding agents: files, lines, callers and tests for any public GitHub repo.
7 tools: 5 change things and 2 only read.
- Reads private data · 2
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Synapse MCP server can do
The Synapse MCP server is published by the GitHub account Aadeshjain25. It has 7 tools. It can create or change data (5 tools: plan_change, why, blast_radius, tests_for and 1 more), but cannot delete data. 2 tools only read.
2 tools read private data (read_code and find_existing).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 21, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 5Claude Code: ask
blast_radiusEvery call site of a file or one of its functions, with the calling line of code, plus importers and tests.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Every call site of a file or one of its functions, with the calling line of code, plus importers and tests. Use before changing a signature or deleting code.
Annotations the server declares
- title: What breaks if this changes
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
plan_changeCall ONCE at the start of a coding task.1 finding
Why it is in this group
- The description's first verb is "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "plan_change" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.
Description, as the server wrote it Call ONCE at the start of a coding task. A complete brief: files and line ranges to change, the key functions in full with their callers, the existing pattern to follow, decisions not to break and the only tests to run. From the code graph, not guesses.
Annotations the server declares
- title: Plan a code change
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
repo_mapOne screen on an unfamiliar repo: main areas with their most used code, entry points, API routes and pages, where tests live, and the stack.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it One screen on an unfamiliar repo: main areas with their most used code, entry points, API routes and pages, where tests live, and the stack. Call once instead of exploring folders.
Annotations the server declares
- title: Map of the repository
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
tests_forThe test files that cover the given files (direct importers, same-name tests, and tests one import away), so you run only those instead of the whole suite.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The test files that cover the given files (direct importers, same-name tests, and tests one import away), so you run only those instead of the whole suite.
Annotations the server declares
- title: Which tests to run
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whyReasons behind a file or line: decisions from PRs, reviews and reverts, the commit that last changed the line (with its message), the function there and who knows the code.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Reasons behind a file or line: decisions from PRs, reviews and reverts, the commit that last changed the line (with its message), the function there and who knows the code. Use before changing or deleting code that looks odd.
Annotations the server declares
- title: Why is this code like this?
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
find_existingSearch existing functions, classes and methods by what they do (e.g.Reads private dataNo findings
Why it is in this group
- The name "find_existing" says "find": a word for reading.
What it can reach
- private-dataThe input names a repository (input.repository), and the tool reads: it reads repositories.
Description, as the server wrote it Search existing functions, classes and methods by what they do (e.g. "format currency"). Use before writing a new helper.
Annotations the server declares
- title: Find existing code to reuse
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
read_codeRead code without opening whole files.Reads private dataNo findings
Why it is in this group
- The name "read_code" says "read": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "file": it reads files.
- private-dataThe input names a repository (input.repository), and the tool reads: it reads repositories.
Description, as the server wrote it Read code without opening whole files. With `symbol`: just that function, method or class (numbered lines). Without: the file's outline (every declaration with its signature and line range). Use instead of reading a full file.
Annotations the server declares
- title: Read one function, or a file outline
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 21, 2026, 19:19 UTC, unchanged since Nov 21, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://asksynapse.in/.well-known/oauth-protected-resource/api/v1/public/mcp
- Authorization servers
- https://asksynapse.in
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://asksynapse.in/api/v1/public/mcp: tools/list returned 7 tools to an anonymous client, including plan_change (write), why (write), blast_radius (write), tests_for (write), repo_map (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnplan_change
The server marks "plan_change" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http synapse https://asksynapse.in/api/v1/public/mcpclaude mcp add --transport http synapse https://asksynapse.in/api/v1/public/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__synapse__read_code",
"mcp__synapse__find_existing"
],
"ask": [
"mcp__synapse__plan_change",
"mcp__synapse__why",
"mcp__synapse__blast_radius",
"mcp__synapse__tests_for",
"mcp__synapse__repo_map"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as synapse. Review it before you use it.
Capability tags behind 2 rules
- mcp__synapse__read_code private-data
- mcp__synapse__find_existing private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Aadeshjain25/synapse/verify?hash=8d986843264009000b1bca396347d2c49567add6143f9668819cb4dfdf3c1df6" | jq -e '.changed == false'Pinned hash 8d9868432640, from Nov 21, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Aadeshjain25/synapse/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Aadeshjain25/synapse)Source: MCP Registry. Synced Nov 21, 2026, 10:17 UTC.
Synapse MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Synapse MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Synapse MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Synapse MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Synapse MCP server have?
- 7 tools: 5 write, 2 read. plan_change, why, blast_radius, tests_for, repo_map, read_code and find_existing.
Does the Synapse MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Synapse MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Synapse MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.