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

io.github.XXO47OXX/spa-reader-mcp

NPM · SPA-READER-MCP · SCANNED SEP 20

MCP Server that renders JavaScript SPA pages and extracts LLM-ready Markdown content

Available components

0 this week 80 Trust /100
Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 40 of 144 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 303 tokens (~151/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.XXO47OXX/spa-reader-mcp server?

io.github.XXO47OXX/spa-reader-mcp runs locally as an npm package, launched with npx -y spa-reader-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · spa-reader-mcp

# add to Claude Code
claude mcp add xxo47oxx-spa-reader-mcp -- npx -y spa-reader-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "xxo47oxx-spa-reader-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "spa-reader-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "xxo47oxx-spa-reader-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "spa-reader-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add xxo47oxx-spa-reader-mcp -- npx -y spa-reader-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xxo47oxx-spa-reader-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "spa-reader-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add xxo47oxx-spa-reader-mcp --command npx --arg -y --arg spa-reader-mcp
# ~/.hermes/config.yaml
mcp_servers:
  xxo47oxx-spa-reader-mcp:
    command: "npx"
    args: ["-y", "spa-reader-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "xxo47oxx-spa-reader-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "spa-reader-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add xxo47oxx-spa-reader-mcp -t stdio -c npx -a -y spa-reader-mcp
// mcp.json
{
  "mcpServers": {
    "xxo47oxx-spa-reader-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "spa-reader-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.

  • 20 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 19 Sept 26 +1
    • Stability: 0.97 → pass security
  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 12 Sept 26 +1
    • Stability: 0.97 → pass security
  • 10 Sept 26 +1
    • Security disclosure: unverified → fail functional
  • 9 Sept 26 0
    • Security disclosure: fail → unverified functional
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 20 Sept 2026 · Analysed npm/spa-reader-mcp@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 144 packages
Packages resolved 144
Stale 40
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~303 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
spa_read ~146

Render a JavaScript SPA page and extract its content as LLM-ready Markdown. Uses a headless browser to execute JavaScript, then extracts the main article content.

NameTypeReqDescription
cookiesarrayCookies to inject before page load (e.g., session tokens)
headersobjectCustom HTTP headers (e.g., Authorization)
includeMetadatabooleanInclude title/author/excerpt as YAML frontmatter (default: true)
urlstringyesThe URL of the SPA page to read
waitForSelectorstringCSS selector to wait for before extraction
waitTimeoutnumberNavigation timeout in ms (default: 30000)

No output schema declared.

No examples provided.

spa_screenshot ~157

Take a screenshot of a JavaScript SPA page after rendering. Uses a headless browser to execute JavaScript and capture the visual output as PNG.

NameTypeReqDescription
cookiesarrayCookies to inject before screenshot
fullPagebooleanCapture full scrollable page (default: false)
headersobjectCustom HTTP headers
heightnumberViewport height in pixels (default: 720)
urlstringyesThe URL to screenshot
waitForSelectorstringCSS selector to wait for before capturing
waitTimeoutnumberNavigation timeout in ms (default: 30000)
widthnumberViewport width in pixels (default: 1280)

No output schema declared.

No examples provided.

Common questions

What is the io.github.XXO47OXX/spa-reader-mcp server?

io.github.XXO47OXX/spa-reader-mcp is listed in the public MCP registry as io.github.XXO47OXX/spa-reader-mcp. MCP Server that renders JavaScript SPA pages and extracts LLM-ready Markdown content. This page covers its npm package (spa-reader-mcp).

Is the io.github.XXO47OXX/spa-reader-mcp server safe to use?

io.github.XXO47OXX/spa-reader-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.XXO47OXX/spa-reader-mcp server expose?

io.github.XXO47OXX/spa-reader-mcp exposes 2 tools: spa_read, spa_screenshot. Their descriptions and schemas cost roughly 303 tokens of context every time the server is loaded.

Is the io.github.XXO47OXX/spa-reader-mcp server still maintained?

io.github.XXO47OXX/spa-reader-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.XXO47OXX/spa-reader-mcp server under?

io.github.XXO47OXX/spa-reader-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.