Is @currents/mcp secure?

Legit.Show measured @currents/mcp's Security frame at 45/100. Security headers present: HSTS. Served over HTTPS with a valid certificate.

How does Legit.Show measure @currents/mcp?

Legit.Show scores seven frames — Performance, Accessibility, Security, Privacy, Reliability, Standards and Discoverability — deterministically from the public surface (URL, HTTP headers, real Lighthouse), with no LLM in the scoring path. See legit.show/methodology.

Developer Tools

@currents/mcp

Last updated 2026-06-08 · benchmark measured 2026-09-15 — deterministic & reproducible

Cloud dashboard for running, debugging, and monitoring Playwright tests in CI.

68/100

7/7 frames

Top 79% of 14,457 measured · #27 of 31 in test automation platform

Legit Benchmark — the simple average of 7 measured frames. Frames we could not measure are left out of the average, never counted as zero. Every frame is shown below with its evidence.

Checked 2026-09-15 · scores move as sites change

Are you the maker of @currents/mcp? Claim this listing. It is free, takes a meta tag, a DNS record or GitHub admin rights, and never changes the score.

Launched something? Add your product, free.

To cite this score: legit.show/s/npm-currents-mcp/2026-09-15. That address never changes; this page moves with every re-measure.

Legit.Show scored @currents/mcp 68/100 on 2026-09-15, measured across all 7 frames from its public surface. legit.show/s/npm-currents-mcp/2026-09-15

Is @currents/mcp production-ready?

Legit.Show scores @currents/mcp 68 out of 100 — the simple average of its 7 measured frames. Legit.Show ran its deterministic 7-Frame production-readiness benchmark on @currents/mcp (public-surface assessment), measured from the public surface with no LLM in the scoring path. Its strongest frame is Reliability; its weakest is Performance. Every frame it averages is published with its evidence on the Legit.Show listing.

The 7 Frames

Performance — 36/100
Accessibility — 75/100
Security — 45/100
How this compares across the catalogue: The Web Security Baseline
Privacy — 45/100
How this compares across the catalogue: The Privacy Gap
Reliability — 100/100
Standards — 78/100
Discoverability — 100/100

What we measured

Security headers present: HSTS.
No Content-Security-Policy.
Served over HTTPS with a valid certificate.
Real Lighthouse performance run — 517 ms to first byte.
Returns a proper 404 for unknown routes.
3 of 3 sampled routes reachable.
Has a reachable privacy policy.
Sets cookies / loads scripts with no consent prompt.

Who built it

Andrew · product account @currents_dev

Who it's for

QA teams · DevOps engineers · Playwright users · CI/CD teams · Enterprise teams

Pricing

14-day free trial available

Sources and updates

Description: Taken from currents.dev's own website on 2026-06-08.
Benchmark: Measured by Legit.Show from the live site, the way any visitor sees it — with no access to its code or accounts. Same method for every product, and no AI decides the score. Last checked 2026-09-15.

Put together from public information, without @currents/mcp's involvement. If anything here is wrong, tell us and a person will check it.

Visit @currents/mcp → · Alternatives to @currents/mcp → · How this was measured →