Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.tomjwxf/scopeblind-mcp

NPM · SCOPEBLIND-MCP · SCANNED AUG 3

Scan, protect, and monitor APIs from AI coding tools. Device-level rate limiting.

Available components

+20 this week 66 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 332 tokens (~83/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · scopeblind-mcp

# add to Claude Code
claude mcp add tomjwxf-scopeblind-mcp -- npx -y scopeblind-mcp
# add to Codex CLI
codex mcp add tomjwxf-scopeblind-mcp -- npx -y scopeblind-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tomjwxf-scopeblind-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "scopeblind-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add tomjwxf-scopeblind-mcp --command npx --arg -y --arg scopeblind-mcp
# ~/.hermes/config.yaml
mcp_servers:
  tomjwxf-scopeblind-mcp:
    command: "npx"
    args: ["-y", "scopeblind-mcp"]
// mcp.json
{
  "mcpServers": {
    "tomjwxf-scopeblind-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "scopeblind-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +3
    • Stability: unverified → 0.23 functional
  • 2 Aug 26 +42
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • License: unverified → fail functional
    • Security disclosure: fail → unverified functional
    • Tool coverage: 100 → unverified functional
    • Schema quality: unverified → excellent functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Licence: FSL-1.1-MIT functional
  • 31 Jul 26 −3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −22
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 46

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 4 exposed · ~332 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
get_abuse_report ~111

Fetch real-time abuse statistics for a ScopeBlind tenant. Shows total requests, unique devices, abuse rate, and estimated dollar waste.

NameTypeReqDescription
cost_per_requestnumberCost per request in dollars (e.g. 0.01 for LLM API calls). Used to estimate dollar waste from abuse.
slugstringyesThe tenant slug (e.g. "a1b2c3d4e5f6"). Get this from provision_tenant or the ScopeBlind dashboard URL.

No output schema declared.

No examples provided.

get_integration_code ~76

Generate ScopeBlind integration code for a specific framework. Supports: script-tag, express, fastapi, nextjs, agent-sdk, gateway.

NameTypeReqDescription
frameworkstringyesThe framework to generate code for
slugstringTenant slug. If not provided, uses a placeholder. Get a slug from provision_tenant.

No output schema declared.

No examples provided.

provision_tenant ~84

Create a ScopeBlind tenant for an API endpoint. Returns a slug, verifier URL, and deploy config. The tenant starts in shadow mode (observes traffic, blocks nothing).

NameTypeReqDescription
emailstringOptional email for dashboard access and abuse reports
target_urlstringyesThe API endpoint to protect (e.g. https://api.example.com/v1/signup)

No output schema declared.

No examples provided.

scan_endpoint ~61

Scan an API endpoint for abuse vulnerabilities (missing rate limiting, replay protection, CORS exposure). Returns a risk assessment with specific issues found.

NameTypeReqDescription
urlstringyesThe API endpoint URL to scan (e.g. https://api.example.com/v1/signup)

No output schema declared.

No examples provided.