Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/currents-dev/currents-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/currents-dev/currents-mcp/currents)<a href="https://agentmods.dev/mcp/currents-dev/currents-mcp/currents"><img src="https://agentmods.dev/badge/mcp/currents-dev/currents-mcp/currents/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/currents-dev/currents-mcp/currents"><img src="https://agentmods.dev/badge/mcp/currents-dev/currents-mcp/currents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
currents scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"currents": {
"name": "Currents",
"description": "Currents MCP server",
"command": "npx",
"args": [
"node",
"./mcp-server/build/index.js"
],
"env": {
"CURRENTS_API_KEY": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 14 lines scan A 03aa11eb2647
currents is an MCP server published in the GitHub repository currents-dev/currents-mcp (20 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-10.
Other mcp servers, from other repositories
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.
stagehand
MCP server "stagehand" as configured in browserbase/stagehand. Runs ../core/dist/facade/stdio-server.mjs with node.
sniff
Autonomous QA scanner: point it at your running app and it walks the real user flows in a headless browser and reports what's actually broken — broken pages/links, console & network errors, empty/placeholder data, broken forms, state-loss, bad loading/err. Runs locally from the sniff-qa npm package.
tradingview-mcp
MCP server "tradingview-mcp" as configured in moeuu/tradingview-mcp. Runs locally from the @moeuu/tradingview-mcp npm package.
weeek-mcp
MCP server "weeek-mcp" as configured in adalekin/weeek-mcp. Runs locally from the weeek-mcp Python package.
html2style
MCP server "html2style" as configured in jackguihx-alt/html2style. Runs locally from the html2style npm package.