tech.thecompound/parserail-mcp
NPM · PARSERAIL-MCP
Documents to schema-valid JSON plus 38 more finished-job AI tools, on one credit wallet.
Available components
Last scanned (2 days ago)
Scores higher than 0% of npm servers
Category Documents and Files
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security50
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency0
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: the declared version isn't published, so its provenance can't be verified. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Maintenance history not yet determined.Unverified
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
- Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
Checks we ran (4)
- Malware scan
- Source repository
- Provenance
- License
Checks we could not complete (10)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Known CVEs in Supply Chain SecurityKnown CVEs could not be checked: the version this server declares is not published in its registry.
- Install scripts in Supply Chain SecurityInstall-script risk not yet assessed.
- Dependency health in Supply Chain SecurityDependency health could not be checked: the version this server declares is not published in its registry.
- Maintenance in Provenance & TransparencyMaintenance history not yet determined.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Nov 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Nov 26 −6
The score moved with no change recorded against any check. We would rather say so than guess.
- 1 Nov 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 31 Oct 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 29 Oct 26 0
- Known CVEs: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Provenance: Provenance check failed: the declared version isn't published, so its provenance can't be verified. security
- Dependency health: 0.86 → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- License: License check failed: no license is declared. functional
- Licence: UNLICENSED functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 16 Oct 26 +3
- Source repository: pass → fail ▼ security
- Known CVEs: unverified → pass ▲ security
- Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare. security
- Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan. security
- Security disclosure: fail → unverified ▼ functional
- License: pass → fail ▼ functional
- Dependency health: unverified → 0.85 ▲ functional
- Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess. functional
- Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake. functional
- Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess. functional
- Licence: MIT → UNLICENSED functional
- Package version: 0.6.0 → 0.6.2 functional
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 4 Nov 2026 · Analysed npm/parserail-mcp@0.6.2
Provenance Version not published
The package exists but this version is not published, so there is no artifact to attest.
| Result | Version not published |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the tech.thecompound/parserail-mcp server?
tech.thecompound/parserail-mcp runs locally as an npm package, launched with npx -y parserail-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 · parserail-mcp
claude mcp add tech-thecompound-parserail-mcp -- npx -y parserail-mcp
What is the tech.thecompound/parserail-mcp server?
tech.thecompound/parserail-mcp is listed in the public MCP registry as tech.thecompound/parserail-mcp. Documents to schema-valid JSON plus 38 more finished-job AI tools, on one credit wallet. This page covers its npm package (parserail-mcp).
Is the tech.thecompound/parserail-mcp server safe to use?
tech.thecompound/parserail-mcp scores 0 out of 100 on VerifyMCP. 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.
Is the tech.thecompound/parserail-mcp server still maintained?
tech.thecompound/parserail-mcp has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 28 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the tech.thecompound/parserail-mcp server?
VerifyMCP ran 4 checks on tech.thecompound/parserail-mcp, covering Malware scan, Source repository, Provenance and License. 10 items could not be completed, a gap on our side rather than a finding about tech.thecompound/parserail-mcp: Known CVEs, Install scripts, Dependency health, Maintenance and 6 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.