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.
npx agentmods add mcp/mikusnuz/meta-mcp/metagit clone --depth 1 https://github.com/mikusnuz/meta-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/mikusnuz/meta-mcp/meta)<a href="https://agentmods.dev/mcp/mikusnuz/meta-mcp/meta"><img src="https://agentmods.dev/badge/mcp/mikusnuz/meta-mcp/meta.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
meta 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 6d 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
{
"meta": {
"command": "npx",
"args": [
"-y",
"@mikusnuz/meta-mcp"
],
"env": {
"INSTAGRAM_ACCESS_TOKEN": "",
"INSTAGRAM_USER_ID": "",
"THREADS_ACCESS_TOKEN": "",
"THREADS_USER_ID": "",
"META_APP_ID": "",
"META_APP_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.
- 6d ago First seen · 17 lines scan A 8e74d5201b4b
meta is an MCP server published in the GitHub repository mikusnuz/meta-mcp (24 stars, last pushed 7d 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-30.
Other mcp servers, from other repositories
instagram-mcp
Instagram MCP — 23 tools for Instagram Graph API: posts, DMs, stories, reels, analytics. Runs locally from the @mcpware/instagram-mcp npm package. Needs 3 environment variables to run.
AynOps
A Model Context Protocol server that gives AI Clients real-time cybersecurity reconnaissance capabilities — WHOIS, DNS enumeration, port scanning, SSL inspection, CVE lookup, IP reputation, ASN lookup and more. Runs locally from the AynOps Python package. Needs 2 environment variables to run.
ninjaone-mcp
MCP server "ninjaone-mcp" as configured in WYRE-AI/ninjaone-mcp. Runs in Docker (ghcr.io/wyre-ai/ninjaone-mcp:v2.3.0). Needs 6 environment variables to run.
apibase
327 tools, 92 providers. Pay per call via x402 + MPP. One MCP endpoint. Runs locally from the apibase-mcp-client npm package.
calc-mcp
21 MCP tools for math, randomness, dates, encoding, hashing, and more — deterministic and accurate. Runs locally from the @coo-quack/calc-mcp npm package.
molecare-mcp
Educational dermatology knowledge and lesion tooling. No credentials needed. Not a medical device. Runs locally from the molecare-mcp npm package. Needs 5 environment variables to run.