mcp@3.25.0
VERIFIED· startup onlyPublisher claims: "Official 0xinsider CLI and MCP server: Polymarket analytics & infrastructure for sports and esports markets" 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
API_KEY_ENV_VARAPI_KEY_PREFIXOXINSIDER_API_KEYConfiguration, not credentials: NEUTRALIZED_META_KEY, OXINSIDER_API_URL, OXINSIDER_CONFIG_DIR- Where it talks to
- 0xinsider.com (its own)Also rfc-editor.org, nodejs.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 with a scoped credential, under the guard, and read the third-party hosts first. The code names rfc-editor.org, nodejs.org as well as its own vendor. The guard injects API_KEY_ENV_VAR, API_KEY_PREFIX, OXINSIDER_API_KEY only into requests to 0xinsider.com (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 (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-15 and scored it 80/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 · 29 s · 2 scenarios · 0 deviationsStatic findings
[mcp_servers."${SERVER_NAME}".env]Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.npx -y ${PACKAGE_NAME}Fix: Pin versions and sources; vendor anything fetched at install time.npx -y ${PACKAGE_NAME} initFix: Pin versions and sources; vendor anything fetched at install time.`[mcp_servers."${SERVER_NAME}".env]`,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.log("Replace the placeholder with your API key in the config file. Do not paste the key into a command or terminal output.");Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.`[mcp_servers.${SERVER_NAME}.env]`,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.The `batch_get_traders`, `batch_get_market_flow` and `batch_get_market_intel` rows below are GENERATED: they publish the batch item cap, which is owned by `MAX_Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.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 @0xinsider/mcp@3.25.0 as of 34 min ago. This is the package itself, not its dependencies.