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/bex-co/bex/expogit clone --depth 1 https://github.com/bex-co/bexWrote 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/bex-co/bex/expo)<a href="https://agentmods.dev/mcp/bex-co/bex/expo"><img src="https://agentmods.dev/badge/mcp/bex-co/bex/expo.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
expo 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 4d 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.
This is a copy
100% identical to expo — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"expo": {
"type": "http",
"url": "https://mcp.expo.dev/mcp"
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 4d ago First seen · 6 lines scan A 68f2b5585e42
expo is an MCP server published in the GitHub repository bex-co/bex (420 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. It is 100% identical to expo, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
devops-mcp
Unified MCP server for Kubernetes, ArgoCD, Prometheus, PagerDuty, and Loki. Runs locally from the @notharshhaa/devops-mcp npm package. Needs 9 environment variables to run.
argocd-mcp-server
MCP server for ArgoCD GitOps continuous delivery integration. Runs locally from the argocd-mcp-server Python package.
telecom-cli
MCP server "telecom-cli" as configured in thc1006/telecom-ops-claude-code-plugins. Launched with ${CLAUDE_PLUGIN_ROOT}/scripts/telecom-mcp-server.sh. Needs 1 environment variable to run.
kubernetes
MCP server for interacting with Kubernetes clusters via kubectl. Runs locally from the mcp-server-kubernetes npm package.
gopls-mcp
gopls, the Go language server, exposed as an MCP server: lets the agent query symbols, definitions, references and diagnostics in a Go codebase. Launched with ./scripts/run.sh.
langgraph-agent
MCP server "langgraph-agent" as configured in vishnu2kmohan/mcp-server-langgraph. Runs locally from the python Python package. Needs 1 environment variable to run.