mseep-synapse-mcp@0.1.4
VERIFIED· not startedPublisher claims: "A Model Context Protocol (MCP) server that exposes Synapse Entities with Croissant metadata support" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
SYNAPSE_OAUTH_CLIENT_IDSYNAPSE_OAUTH_CLIENT_SECRETSYNAPSE_OAUTH_REDIRECT_URIConfiguration, not credentials: MCP_SERVER_URL, MCP_TRANSPORT- Where it talks to
- no vendor host named in the codeAlso sagebase.org, purl.org, synapse.org, creativecommons.org, sagebionetworks.org — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names sagebase.org, purl.org, synapse.org, creativecommons.org, sagebionetworks.org as well as its own vendor. The guard injects SYNAPSE_OAUTH_CLIENT_ID, SYNAPSE_OAUTH_CLIENT_SECRET, SYNAPSE_OAUTH_REDIRECT_URI only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-12 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 3 scenarios · 0 deviationsStatic findings
No findings across 2,889 lines in 35 files.
Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for mseep-synapse-mcp@0.1.4 as of 44 h ago. This is the package itself, not its dependencies.