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/ADIKANT/datalens-dev-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/adikant/datalens-dev-mcp/datalens)<a href="https://agentmods.dev/mcp/adikant/datalens-dev-mcp/datalens"><img src="https://agentmods.dev/badge/mcp/adikant/datalens-dev-mcp/datalens/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/adikant/datalens-dev-mcp/datalens"><img src="https://agentmods.dev/badge/mcp/adikant/datalens-dev-mcp/datalens.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
datalens 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
{
"datalens": {
"command": "datalens-dev-mcp",
"args": [
"stdio"
]
}
}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 · 8 lines scan A 182d5ddf60fd
datalens is an MCP server published in the GitHub repository ADIKANT/datalens-dev-mcp (5 stars, last pushed today), 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-08.
Other mcp servers, from other repositories
daxops-mcp
DaxOps MCP server - drive your DaxOps cloud account from Claude Code or any MCP client: build Power BI .pbix dashboards from your data, use the AI prompter, browse Solution starters, and manage saved dashboards, authenticated with your DaxOps license key. Runs locally from the daxops-mcp npm package.
ghidra-mcp
MCP server "ghidra-mcp" as configured in bethington/ghidra-mcp. Runs locally from the c:/Users/benam/source/mcp/ghidra-mcp Python package. Needs 3 environment variables to run.
unraid-mcp
MCP Server for Unraid API - provides tools to interact with an Unraid server's GraphQL API. Runs locally from the unraid-mcp Python package. Needs 3 environment variables to run.
sap-gui
MCP server "sap-gui" as configured in kts982/mcp-sap-gui. Runs locally from the python Python package.
mcp-sap-gui
MCP Server for SAP GUI Scripting automation. Runs locally from the mcp-sap-gui Python package.
wet-mcp
Open-source MCP Server for web search, extract, crawl, academic research, and library docs with embedded SearXNG. Runs locally from the wet-mcp Python package. Needs 2 environment variables to run.