@currents/mcp — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor this implementation for changes in adoption, MCP interface, maintenance and permission boundary.

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

Best fit

Use Currents testing-service MCP tools

What we know

Currents MCP server Use Currents testing-service MCP tools.

Maintenance / activity evidence

npm downloads 261887 in 2026-09-08..2026-10-07

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation. Complete write authority is not verified.
Currents access credentials
Test runs, status and project data

Cloud testing account scopes and write/control operations require exact tool verification.

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

Popularity

· 261.9k package downloads / 30 days

Downloads observed Oct 9, 2026.

Exact npm package @currents/mcp; provider interval 2026-09-08–2026-10-07 (inclusive); observed 2026-10-09.

All limitations / Review context

Has @currents/mcp changed its specific MCP integration, install method or privilege scope, and does it justify shortlist promotion?

High-impact permissions explicitly documented; no known blocker to an accurately caveated public Radar listing in limited first-party review.

Cloud testing account scopes and write/control operations require exact tool verification.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Currents access credentials
Test runs, status and project data
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.
No exhaustive advisory or runtime review performed; never infer installation safety.
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.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
npm package downloads explicitly observed

Original activity observations

npm downloads 261887 in 2026-09-08..2026-10-07

Technical identity

npm/@currents/mcp

Exact implementation source: https://www.npmjs.com/package/@currents/mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@currents/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 ↗
@currents/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 documents `claude mcp add --transport stdio currents --env CURRENTS_API_KEY=<KEY> -- npx -y @currents/mcp`; optional hosted HTTP requires Authorization Bearer.
publisher install or stdio launch · Claude Code only · Publisher instructions
claude mcp add --transport stdio currents --env CURRENTS_API_KEY=YOUR_KEY -- npx -y @currents/mcp
Configure / authenticate
MCP100 setup guide
Publisher Claude Code command: `claude mcp add --transport stdio currents --env CURRENTS_API_KEY=<key> -- npx -y @currents/mcp`.
Check connection
Suggested check
Check MCP tool discovery/read-only recent test information; HTTP `/healthz` is process liveness, not proof of authenticated upstream access.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `currents-mcp`, run `claude mcp remove currents-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove currents-mcp

Official Documentation & Sources

What it does

Currents MCP server Use Currents testing-service MCP tools.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Use Currents testing-service MCP tools

Representative uses

Inspect repository and project data
Support development or testing tasks
Automate bounded tool workflows
Use Currents testing-service MCP tools

Limitations

Cloud testing account scopes and write/control operations require exact tool verification.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
npm package downloads explicitly observed

Reviewed access

Access & risk

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

Authentication: Currents access credentials
Permissions: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Data handling: Test runs, status and project data
Cost: may incur external API or infrastructure charges; unverified
Risk and cautions: Cloud testing account scopes and write/control operations require exact tool verification.

Access scope and cautions

Write actions: Not verified
Risk level: moderate
Security notes: Cloud testing account scopes and write/control operations require exact tool verification.

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-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Inspect repository and project data; Support development or testing tasks; Automate bounded tool workflows; Use Currents testing-service MCP tools.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Command provided only where first-party command or package existence is established; verify the client configuration against upstream documentation. Installation/authentication detail is incomplete; do not infer settings from package name. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Currents access credentials

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.

What data-handling boundary should I consider?

Test runs, status and project data

What limitations and risks should I check before use?

Cloud testing account scopes and write/control operations require exact tool verification. Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation. npm package downloads explicitly observed. No exhaustive advisory or runtime review performed; never infer installation safety.