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/theYahia/dadata-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/theyahia/dadata-mcp/dadata)<a href="https://agentmods.dev/mcp/theyahia/dadata-mcp/dadata"><img src="https://agentmods.dev/badge/mcp/theyahia/dadata-mcp/dadata/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/theyahia/dadata-mcp/dadata"><img src="https://agentmods.dev/badge/mcp/theyahia/dadata-mcp/dadata.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dadata 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 1mo ago.
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
{
"dadata": {
"command": "npx",
"args": [
"-y",
"@metarebalance/dadata-mcp"
],
"env": {
"DADATA_API_KEY": "<YOUR_TOKEN>",
"DADATA_SECRET_KEY": "<YOUR_SECRET>"
}
}
}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.
- 1mo ago First seen · 13 lines scan A 134f93d4a32e
dadata is an MCP server published in the GitHub repository theYahia/dadata-mcp (3 stars, last pushed 1mo ago), licensed MIT. 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-08-31.
Other mcp servers, from other repositories
unraid
Rust MCP server and CLI for Unraid GraphQL operations across NAS, Docker, VM, and storage workflows. Runs locally from the @dinglebear/unraid npm package. Needs 6 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.
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 2 environment variables to run.
portkey-admin-mcp
Portkey Admin API MCP server with current coverage and Prisma AIRS interoperability guidance. Runs locally from the portkey-admin-mcp npm package. Needs 3 environment variables to run.
sendgrid-mcp
MCP server for SendGrid's v3 API: email marketing, transactional mail, templates, and analytics. Runs locally from the sendgrid-mcp npm package. Needs 2 environment variables to run.
cdek
MCP server for CDEK delivery API — 16 tools: calculate, orders, courier pickup, tracking, PVZ, print, webhooks. OAuth2 auth. Runs locally from the @theyahia/cdek-mcp npm package. Needs 3 environment variables to run.