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/WYRE-AI/action1-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/wyre-ai/action1-mcp/action1-mcp)<a href="https://agentmods.dev/mcp/wyre-ai/action1-mcp/action1-mcp"><img src="https://agentmods.dev/badge/mcp/wyre-ai/action1-mcp/action1-mcp/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/wyre-ai/action1-mcp/action1-mcp"><img src="https://agentmods.dev/badge/mcp/wyre-ai/action1-mcp/action1-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
action1-mcp 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 10d 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
{
"action1-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-ai/action1-mcp:v1.1.7"
],
"env": {
"ACTION1_CLIENT_ID": "",
"ACTION1_CLIENT_SECRET": "",
"ACTION1_TENANT": "",
"ACTION1_BASE_URL": "",
"MCP_TRANSPORT": "stdio",
"AUTH_MODE": "env",
"LOG_LEVEL": "info"
}
}
}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.
- 10d ago First seen · 20 lines scan A 21cf25c7369a
action1-mcp is an MCP server published in the GitHub repository WYRE-AI/action1-mcp (2 stars, last pushed yesterday), 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. 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
Windows-MCP
Lightweight MCP Server for interacting with Windows Operating System. Runs locally from the windows-mcp Python package.
kip-mcp-server
Reads a boat's Signal K data and helps an AI assistant design and install KIP dashboards. Runs locally from the kip-mcp-server npm package. Needs 7 environment variables to run.
mijia
MCP server "mijia" as configured in oadank/miot-mcp. Launched with C:\D\opt\miot-mcp\venv\Scripts\python.exe C:\D\opt\miot-mcp\mcp_server\mcp_serve. Needs 3 environment variables to run.
z1-walkingpad-mcp
MCP server "z1-walkingpad-mcp" as configured in slandau3/z1-walkingpad-mcp. Runs locally from the z1-walkingpad-mcp Python package.
obsbot-mcp
Control an OBSBOT Tiny 2 camera: pan/tilt/zoom, AI tracking, focus, exposure, snapshots, recording. Runs locally from the obsbot-mcp npm package. Needs 1 environment variable to run.
netmiko-mcp-server
MCP server "netmiko-mcp-server" as configured in nagayon-935/netmiko-mcp-server. Runs locally from the netmiko-mcp-server Python package.