synthex-mcp-server@1.0.0
VERIFIED· startup onlyPublisher claims: "Exposes a remote catalogue of paid x402 routes as MCP tools, proxying calls and paying USDC on Base with the x402 protocol. Returns results alongside the on-chain settlement transaction hash, with a free catalogue tool for inspection." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
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
- no credential variables read in the code
- Where it talks to
- synthexforge.com (its own)Also base.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
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it under the guard. Startup only; authenticated tool behavior not tested. The code names no credential variable and talks to synthexforge.com, its own; the guard pins the network to what the honeypot saw and logs every call.
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 (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-12 and scored it 85/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 · 37 s · 2 scenarios · 0 deviationsStatic findings
"args": ["-y", "synthex-mcp-server", "--http", "--port", "8080"],Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.synthex-mcp-server --http --port 8080 streamable HTTP transportFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.console.log(`postbuild: chmod 755 ${target}`);Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.synthex-mcp-server --http --port 8080 streamable HTTP transportFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.MCP server hermeschoosenone-debug/synthex-mcp-server on Glama, built from https://github.com/hermeschoosenone-debug/synthex-mcp-server.Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them."build": "tsc -p tsconfig.build.json && node scripts/postbuild.mjs",Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(`postbuild: chmod 755 ${target}`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.'.env',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.`synthex-mcp-server listening on http://${options.host}:${options.port}/mcp ` +Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.process.stderr.write(`synthex-mcp-server listening on http://${options.host}:${options.port}/mcp ` +Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.it('ignores .env files', () => {Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.expect(gitignore).toMatch(/\.env/);Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.