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/akashdeep01/emr-mcp-serverWrote 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/akashdeep01/emr-mcp-server/emr-cluster-manager)<a href="https://agentmods.dev/mcp/akashdeep01/emr-mcp-server/emr-cluster-manager"><img src="https://agentmods.dev/badge/mcp/akashdeep01/emr-mcp-server/emr-cluster-manager/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/akashdeep01/emr-mcp-server/emr-cluster-manager"><img src="https://agentmods.dev/badge/mcp/akashdeep01/emr-mcp-server/emr-cluster-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
emr-cluster-manager 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 9d 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
{
"emr-cluster-manager": {
"command": "python",
"args": [
"-m",
"mcp",
"client",
"http://localhost:3000"
],
"env": {
"EMR_MCP_API_KEY": "emr-mcp-default-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.
- 9d ago First seen · 14 lines scan A d43427ee471e
emr-cluster-manager is an MCP server published in the GitHub repository akashdeep01/emr-mcp-server (1 stars, last pushed 1y 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
cloudwatch
MCP server "cloudwatch" as configured in awslabs/mcp. Runs locally from the awslabs.cloudwatch-mcp-server@latest Python package. Needs 1 environment variable to run.
cloudwatch-appsignals
MCP server "cloudwatch-appsignals" as configured in awslabs/mcp. Runs locally from the awslabs.cloudwatch-applicationsignals-mcp-server@latest Python package. Needs 1 environment variable to run.
prefect
MCP server "prefect", hosted remotely at prefect.fastmcp.app, as configured in PrefectHQ/prefect-mcp-server.
mcp-pve
Manage Proxmox VE through AI assistants. Runs locally from the @samik081/mcp-pve npm package. Needs 3 environment variables to run.
ionoscloud-mcp
MCP server "ionoscloud-mcp" as configured in ionos-cloud/ionoscloud-mcp. Runs in Docker (ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.0). Needs 4 environment variables to run.
ionoscloud
MCP server "ionoscloud" as configured in ionos-cloud/ionoscloud-mcp. Launched with ionoscloud-mcp. Needs 2 environment variables to run.