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/freema/openclaw-mcp/openclaw-openclawgit clone --depth 1 https://github.com/freema/openclaw-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/freema/openclaw-mcp/openclaw-openclaw)<a href="https://agentmods.dev/mcp/freema/openclaw-mcp/openclaw-openclaw"><img src="https://agentmods.dev/badge/mcp/freema/openclaw-mcp/openclaw-openclaw.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
openclaw 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- openclaw — 100% identical, 0 lines differ
What it actually says
{
"openclaw": {
"command": "npx",
"args": [
"-y",
"openclaw-mcp@latest"
]
}
}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.
- 7d ago First seen · 9 lines scan A b03cc25d5cda
openclaw is an MCP server published in the GitHub repository freema/openclaw-mcp (183 stars, last pushed 21d 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
postman-mcp-server
A basic MCP server to operate on the Postman API. Runs locally from the @postman/postman-mcp-server npm package. Needs 1 environment variable to run.
mcp-server
Model Context Protocol (MCP) server for AI-assisted development of CAP applications. Runs locally from the @cap-js/mcp-server npm package.
kafka-schema-registry
MCP server "kafka-schema-registry" as configured in aywengo/kafka-schema-reg-mcp. Runs kafka_schema_registry_unified_mcp.py with python. Needs 3 environment variables to run.
sfcc-dev-mcp
MCP server for Salesforce B2C Commerce Cloud development assistance. Runs locally from the sfcc-dev-mcp npm package.
stitchapi-docs
StitchAPI documentation search, running locally over MCP stdio. Bundled docs, no network calls per query — the offline/air-gapped counterpart to the hosted stitchapi.dev/api/mcp server. Runs locally from the @stitchapi/docs-mcp npm package.
better-telegram-mcp
Production-grade MCP server for Telegram — dual-mode Bot API + MTProto, domain-separated tools. Runs locally from the better-telegram-mcp Python package. Needs 3 environment variables to run.