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.

EveryPage

NPM · EVERYPAGE-MCP · SCANNED AUG 22

Share PDFs as tracked links and see who read them, how far they got, and where they stopped.

Available components

npm · everypage-mcp 49
0 this week 49 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 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
  • 30 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to EveryPageApp/everypage-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, 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) that our sandbox does not supply, 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) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package 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 →

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 · everypage-mcp

# add to Claude Code
claude mcp add co-everypage-mcp -- npx -y everypage-mcp
# add to Codex CLI
codex mcp add co-everypage-mcp -- npx -y everypage-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-everypage-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "everypage-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add co-everypage-mcp --command npx --arg -y --arg everypage-mcp
# ~/.hermes/config.yaml
mcp_servers:
  co-everypage-mcp:
    command: "npx"
    args: ["-y", "everypage-mcp"]
// mcp.json
{
  "mcpServers": {
    "co-everypage-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "everypage-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.

  • 18 Aug 26 0
    • Package version: 0.1.1 → 1.0.0 functional
  • 15 Aug 26 +11
    • Provenance: fail → pass ▲ security
    • The attested source repository moved: EveryPageApp/everypage-mcp security
    • Package version: 0.1.0 → 0.1.1 functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 9 Aug 26 38

    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 22 Aug 2026 · Analysed npm/everypage-mcp@1.0.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo EveryPageApp/everypage-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/EveryPageApp/everypage-mcp/.github/workflows/release.yml@refs/tags/v1.0.0
Rekor log index 2501630780
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:8b9bb37d9d42d58b79dfa00b9adff8dc0f1b019524c1205c55ad336e4f1806e2bfadde00ef5666ba8e3d4ac05eb5cfecd02e599249063024045168550
Dependencies 96 packages
Packages resolved 96
Stale 30
Tree resolution Complete
MCP tools

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.

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.