quantcontext-mcp@0.1.2
VERIFIED· not startedPublisher claims: "MCP server for trade research and strategy backtesting. Deterministic quant tools for AI agents — stock screening, backtesting, and factor analysis." 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
- 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
RESEND_API_KEYConfiguration, not credentials: MARKET_DATA_BASE_URL, NEXT_PUBLIC_DOCS_URL, RESEND_AUDIENCE_ID, SEED_DATA_BASE_URL- Where it talks to
- quantcontext.ai (its own)Also x.com, gstatic.com, zommalabs.com, dartmouth.edu — 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 x.com, gstatic.com, zommalabs.com, dartmouth.edu as well as its own vendor. The guard injects RESEND_API_KEY only into requests to quantcontext.ai (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; not started: dependency install failed; the server itself was not observed) on 2026-11-15 and scored it 88/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 · 2 scenarios · 0 deviationsStatic findings
@import url("https://fonts.googleapis.com/css2?family=Instrument+Serif:ital@0;1&family=Inter:wght@400;500;600&family=JetBrains+Mono:wght@400;500&display=swap");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.href="https://fonts.googleapis.com/css2?family=Instrument+Serif:ital@0;1&family=Inter:wght@400;500;600&family=JetBrains+Mono:wght@400;500&display=swap"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
No advisories in OSV for quantcontext-mcp@0.1.2 as of 35 min ago. This is the package itself, not its dependencies.