@currents/mcp
npm
v2.4.2
Source verified
Published by currents-dev — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Currents MCP server
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Untrusted-input tools ([currents-get-test-evidence]) co-exist with external-action tools ([currents-list-webhooks, currents-create-webhook, currents-get-webhook, currents-update-webhook, currents-delete-webhook]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [currents-get-test-evidence] → sinks [currents-list-webhooks, currents-create-webhook, currents-get-webhook, currents-update-webhook, currents-delete-
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow currents-get-test-evidence → currents-list-webhooks
Each tool and what it can reach — statically extracted from the published source.
currents-create-webhooknetwork egresscurrents-delete-webhooknetwork egresscurrents-get-test-evidenceingests untrusted inputcurrents-get-webhooknetwork egresscurrents-list-webhooksnetwork egresscurrents-update-webhooknetwork egresscurrents-cancel-runno sensitive capabilitycurrents-cancel-run-github-cino sensitive capabilitycurrents-create-actionno sensitive capabilitycurrents-create-jira-issueno sensitive capabilitycurrents-delete-actionno sensitive capabilitycurrents-delete-runno sensitive capabilitycurrents-disable-actionno sensitive capabilitycurrents-enable-actionno sensitive capabilitycurrents-find-runno sensitive capabilitycurrents-get-actionno sensitive capabilitycurrents-get-affected-executionsno sensitive capabilitycurrents-get-affected-test-executionsno sensitive capabilitycurrents-get-contextno sensitive capabilitycurrents-get-errors-explorerno sensitive capabilitycurrents-get-projectno sensitive capabilitycurrents-get-project-insightsno sensitive capabilitycurrents-get-projectsno sensitive capabilitycurrents-get-run-detailsno sensitive capabilitycurrents-get-runsno sensitive capabilitycurrents-get-spec-files-performanceno sensitive capabilitycurrents-get-spec-instanceno sensitive capabilitycurrents-get-test-resultsno sensitive capabilitycurrents-get-tests-performanceno sensitive capabilitycurrents-get-tests-signaturesno sensitive capabilitycurrents-link-jira-issueno sensitive capabilitycurrents-list-actionsno sensitive capabilitycurrents-list-affected-testsno sensitive capabilitycurrents-list-jira-issue-typesno sensitive capabilitycurrents-list-jira-projectsno sensitive capabilitycurrents-list-project-termsno sensitive capabilitycurrents-list-pull-requestsno sensitive capabilitycurrents-reset-runno sensitive capabilitycurrents-update-actionno sensitive capabilityCross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.4.2 latest |
A 97/100 | 1 | 1.13.0 | 2026-08-30 |
v2.3.3 |
A 97/100 | 0 | 1.12.1 | 2026-08-16 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @currents/mcp --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
Public-safe MCP admin discovery contract descriptors and response builders.
Pokemon Champions battle advisor MCP server
Airflow MCP server — DAG list, runs, task instances, log tails, trigger and clear over the Airflow REST API
MCP analytics wrapper SDK that instruments MCP tool declarations with telemetry.
AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.
AI-native social listening. Monitor buying signals and run GTM workflows via natural language.