ScalpStream MCP server
Pay-per-call data over x402: air quality, border waits, fuel prices, market research.
B73/100grade B
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed ScalpStream yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
ScalpStream tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 11 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 73/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
claude mcp add scalpstream-mcp -- docker run -i --rm ghcr.io/dv1-321/scalpstream-mcp:v0.1.6
ScalpStream: common questions
- Is ScalpStream MCP server safe?
- Mostly: it is graded B (73/100). Read the ScalpStream safety report
- How do I install ScalpStream?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does ScalpStream need an API key?
- Yes. The registry entry asks for
EVM_BASE_PRIVATE_KEY. - Is ScalpStream maintained?
- The last commit was 12 days ago (2026-09-08). The latest release is v0.1.6.