Currents
Last tested 2026-10-22
Score 75/100 · Last tested 2026-10-22 · Version tested 2.7.0 · Package @currents/mcp · Repo currents-dev/currents-mcp
Summary: Currents requires credentials or a backing service before it will list tools.
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install @currents/mcp (Node 20, Linux) succeeded in 2s. |
| handshake | auth-gated | 5 | Auth-gated: without credentials the server only printed a missing-credential message and did not list tools ("[01:15:48.237] ERROR (639102): CURRENTS_API_KEY is not set. Add your Currents API key to the environment (f"). Not tested with real credentials; not counted as working. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 21 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Automated check of the package's own README (README shipped in npm package). |
| license | pass | 10 | Apache-2.0 (OSI-approved). |
Local-model readiness
Not yet tested (no tools/list response without credentials).
Not tested
We did not test behavior with real credentials, security, or performance under load. These are planned; see methodology.
Tools listed
Not available (handshake did not complete without credentials).
Config used in our test
{
"mcpServers": {
"currents": {
"command": "npx",
"args": [
"-y",
"@currents/mcp"
]
}
}
}FAQ
Is Currents deprecated?
No. @currents/mcp was not deprecated or archived when we last tested it on 2026-10-22.
What replaces Currents?
Nothing; Currents is not deprecated as of 2026-10-22.
Does Currents need an API key?
Yes. Without credentials it only printed a missing-credential message and did not list tools (auth-gated).
Embed the badge
The badge always shows the current score; payment never changes it.