co.pepys/pepys-mcp — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track identity, package activity, privileges, documentation and data handling

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

Best fit

Pepys transcription of audio and video

What we know

Transcribe media, diarize speakers and export timestamped text and subtitles. Transcribe audio & video: diarization, timed SRT/VTT, podcasts, paste-a-link, whole-feed batch.

Maintenance / activity evidence

142 downloads from 2026-09-09 through 2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium_identity_and_metrics; published-function claims not execution verified.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Uploaded voice recordings and transcription content go to a third-party API; respect participant consent. Complete write authority is not verified.
See package authentication documentation; not independently tested.
Sensitive access: Account or infrastructure data accessible with supplied credentials

Uploaded voice recordings and transcription content go to a third-party API; respect participant consent.
Public listing does not imply a safe runtime or security audit.

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

Popularity

· 142 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package pepys-mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T17:26:34Z.

All limitations / Review context

Have pepys-mcp permissions, hosted data retention, publication identity or supported MCP operations changed?

Bounded public tracking review; known consequences disclosed: Uploaded voice recordings and transcription content go to a third-party API; respect participant consent.

Uploaded voice recordings and transcription content go to a third-party API; respect participant consent.
Public listing does not imply a safe runtime or security audit.
See package authentication documentation; not independently tested.
Sensitive access: Account or infrastructure data accessible with supplied credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Operator must review permissions and remote data processing before installation.
runtime_installer_exact
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Original activity observations

142 downloads from 2026-09-09 through 2026-10-08

Technical identity

npm/pepys-mcp

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

Evidence & Sources

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

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Package registry ↗
pepys-mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Publisher instructions
npx -y pepys-mcp
Configure / authenticate
MCP100 setup guide
Add publisher stdio mcpServers config with PEPYS_API_KEY in env. OAuth is on roadmap, not supported for this local Phase-1 server.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Environment settings: PEPYS_API_KEY
Check connection
Suggested check
Verify tools listed or use a supported low-impact listing/status call; transcription may be billable.
Remove / uninstall / revoke
MCP100 setup guide
If registered as `pepys-mcp` in Claude Code, remove its exact client entry with `claude mcp remove pepys-mcp`; for Cursor/Claude Desktop/Codex, remove the matching MCP entry in that host settings. This client removal is MCP100-composed, not a vendor uninstall instruction. Npx does not imply a global install; do not delete user data or revoke credentials implicitly.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide
claude mcp remove pepys-mcp

Official Documentation & Sources

What it does

Transcribe media, diarize speakers and export timestamped text and subtitles. Transcribe audio & video: diarization, timed SRT/VTT, podcasts, paste-a-link, whole-feed batch.

Capability: Design & Creative
Resource type: MCP Server
Best fit: Pepys transcription of audio and video

Representative uses

Transcribe recordings
Export SRT/VTT captions

Limitations

Uploaded voice recordings and transcription content go to a third-party API; respect participant consent.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Reviewed access

Access & risk

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

Authentication: See package authentication documentation; not independently tested.
Permissions: Uploaded voice recordings and transcription content go to a third-party API; respect participant consent.
Data handling: Uploaded voice recordings and transcription content go to a third-party API; respect participant consent.
Cost: Not verified; check vendor terms
Risk and cautions: Uploaded voice recordings and transcription content go to a third-party API; respect participant consent.

Access scope and cautions

Write actions: Not verified
Sensitive access: Account or infrastructure data accessible with supplied credentials
Risk level: high
Security notes: Uploaded voice recordings and transcription content go to a third-party API; respect participant consent. Public listing does not imply a safe runtime or security audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T17:26:34Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Transcribe recordings; Export SRT/VTT captions.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Never infer missing startup flags or credentials. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: API credential or authenticated app account required; exact setup should be checked in upstream package

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Uploaded voice recordings and transcription content go to a third-party API; respect participant consent.

What data-handling boundary should I consider?

Uploaded voice recordings and transcription content go to a third-party API; respect participant consent. Recorded sensitive-access context: Account or infrastructure data accessible with supplied credentials.

What limitations and risks should I check before use?

Uploaded voice recordings and transcription content go to a third-party API; respect participant consent. Exact install command and full env contract unverified except where explicitly documented; check official package before running. Exact npm download observation only; no independent installation test. Public listing does not imply a safe runtime or security audit. Operator must review permissions and remote data processing before installation.