EveryPage MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to EveryPage PDF sharing and readership analytics: Do recipient tracking and signed share links retain clear privacy and access boundaries?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Upload PDFs as tracked share links and inspect readership/engagement.

What we know

Local MCP that can read PDFs from local disk, upload them to EveryPage with sharing controls, list/update/delete/replace documents and report readership. A read-only environment mode removes mutation tools.

Maintenance / activity evidence

everypage-mcp 1.0.0 published 2026-08-18T11:02:07.481Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Document/readership read-write authority; optional read-only mode. Writes: Upload/share PDF; Change sharing settings; Delete/replace file.
API key/OAuth token.
Sensitive access: PDF contents, Recipient/readership analytics, API key

Can upload potentially confidential PDFs and create external share links; enable read-only where appropriate.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do recipient tracking and signed share links retain clear privacy and access boundaries?

The bounded review of the publisher's documented EveryPage PDF sharing and readership analytics and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Can upload potentially confidential PDFs and create external share links; enable read-only where appropriate.
Document/readership read-write authority; optional read-only mode.
API key/OAuth token.
PDF contents and readership analytics are stored/processed by EveryPage.
Reviewed write actions: Upload/share PDF; Change sharing settings; Delete/replace file
Sensitive access: PDF contents, Recipient/readership analytics, API key
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Local server can read selected PDFs from disk.
Uploads create externally accessible tracked links subject to chosen controls.
Default mode includes write/delete tools; `EVERYPAGE_READ_ONLY=true` is safer for analysis-only workflows.
API key/OAuth scope determines access.

Original activity observations

everypage-mcp 1.0.0 published 2026-08-18T11:02:07.481Z

Technical identity

npm/everypage-mcp

Exact implementation source: https://www.npmjs.com/package/everypage-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:everypage-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
everypage-mcp
Recorded package identity, distribution or download evidence.
Evidence source ↗
everypage.co/docs/developers/mcp-server
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
everypage.co/integrations/mcp
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
everypage.co/developers
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Page publishing/write access; API key or scoped OAuth token
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
Page publishing/write access; API key or scoped OAuth token | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Claude Code only · Publisher instructions · Review before use
```
claude mcp add everypage --env EVERYPAGE_API_KEY=<KEY> -- npx -y everypage-mcp
```
Configure / authenticate
MCP100 setup guide
EVERYPAGE_API_KEY required; key or limited-scope OAuth token goes in secure client env.
Required environment variables: EVERYPAGE_API_KEY
Check connection
Suggested check
Inspect listed tools; no file upload or publication as connectivity test.
Remove / uninstall / revoke
MCP100 setup guide
If registered by the publisher Claude Code example under `everypage`, run the provided unregister command; for a different MCP client or name, delete the actual client registration. Removing a local client entry is distinct from deleting a vendor account/token.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove everypage

Official Documentation & Sources

What it does

Local MCP that can read PDFs from local disk, upload them to EveryPage with sharing controls, list/update/delete/replace documents and report readership. A read-only environment mode removes mutation tools.

Capability: Productivity & Collaboration
Resource type: MCP Server
Industry: Media & Marketing
Best fit: Upload PDFs as tracked share links and inspect readership/engagement.

Representative uses

Share local/remote PDF with tracked URL/QR/embed
List/get files
Update share settings
Delete/replace documents
Read who viewed and how far they got

Limitations

Local server can read selected PDFs from disk.
Uploads create externally accessible tracked links subject to chosen controls.
Default mode includes write/delete tools; `EVERYPAGE_READ_ONLY=true` is safer for analysis-only workflows.
API key/OAuth scope determines access.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: API key/OAuth token.
Permissions: Document/readership read-write authority; optional read-only mode.
Data handling: PDF contents and readership analytics are stored/processed by EveryPage.
Cost: freemium
Risk and cautions: Can upload potentially confidential PDFs and create external share links; enable read-only where appropriate.

Access scope and cautions

Write actions: Upload/share PDF Change sharing settings Delete/replace file
Sensitive access: PDF contents Recipient/readership analytics API key
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Share local/remote PDF with tracked URL/QR/embed; List/get files; Update share settings; Delete/replace documents; Read who viewed and how far they got.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y everypage-mcp. Recorded transport: stdio. Recorded environment-variable notes: EVERYPAGE_API_KEY; EVERYPAGE_BASE_URL (optional); EVERYPAGE_READ_ONLY (optional). No configuration values are supplied here. Prerequisites: Node 20+; EveryPage account. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: EveryPage API key or scoped OAuth access token.

Can it modify data or perform write operations?

Documented write actions include: Upload/share PDF; Change sharing settings; Delete/replace file. Recorded permission boundary: Document/readership read-write authority; optional read-only mode.

What data-handling boundary should I consider?

PDF contents and readership analytics are stored/processed by EveryPage. Recorded sensitive-access context: PDF contents; Recipient/readership analytics; API key.

What limitations and risks should I check before use?

Can upload potentially confidential PDFs and create external share links; enable read-only where appropriate. Local server can read selected PDFs from disk. Uploads create externally accessible tracked links subject to chosen controls. Default mode includes write/delete tools; `EVERYPAGE_READ_ONLY=true` is safer for analysis-only workflows. API key/OAuth scope determines access. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.