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/krakonjac300-pixel/agent-media-toolkit-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/krakonjac300-pixel/agent-media-toolkit-mcp/agent-media-toolkit)<a href="https://agentmods.dev/mcp/krakonjac300-pixel/agent-media-toolkit-mcp/agent-media-toolkit"><img src="https://agentmods.dev/badge/mcp/krakonjac300-pixel/agent-media-toolkit-mcp/agent-media-toolkit/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/krakonjac300-pixel/agent-media-toolkit-mcp/agent-media-toolkit"><img src="https://agentmods.dev/badge/mcp/krakonjac300-pixel/agent-media-toolkit-mcp/agent-media-toolkit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agent-media-toolkit 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 12d 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
{
"agent-media-toolkit": {
"url": "https://podcast-shorts-a2a-production.up.railway.app/mcp/",
"type": "streamable-http"
}
}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.
- 12d ago First seen · 6 lines scan A 3656f5e2c0bd
agent-media-toolkit is an MCP server published in the GitHub repository krakonjac300-pixel/agent-media-toolkit-mcp (1 stars, last pushed 2mo 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
thingctx
Drive any agent against any W3C WoT Thing, over any transport. No per-integration server. Runs locally from the thingctx Python package. Needs 3 environment variables to run.
omnireach
MCP server "omnireach" as configured in Daily-AC/omnireach. Launched with omnireach mcp.
selat
The unified tool gateway for AI agents: one credential, every upstream, over MCP and REST. Runs locally from the @fajarhide/selat npm package.
xcatcher
Fetch recent public X/Twitter posts by named handle for monitoring, comparison, OSINT, and research. Remote server at xcatcher.top.
agentdata-mcp
Crypto data for AI agents via x402. 31 tools, 4 free. Recorded history, anchored daily on Base. Remote server at agentdata-api.com.
current-sea
MCP server "current-sea", hosted remotely at current-sea.fastapicloud.dev, as configured in Bowieboii/current-sea.