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/mitchellopzero/agentwork-api/agentwork-outcomesgit clone --depth 1 https://github.com/mitchellOpZero/agentwork-apiGrade A, and why
agentwork-outcomes 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 today.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- today First seen · 6 lines scan A 32b97125cc88
agentwork-outcomes is an MCP server published in the GitHub repository mitchellOpZero/agentwork-api (0 stars, last pushed 2d ago), with no licence file. 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
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
toolport-openapi-mcp
Turn any OpenAPI/Swagger spec into an MCP server: one tool per endpoint. A showcase for Toolport (toolport.app). Runs locally from the toolport-openapi-mcp npm package.
cloro
MCP server "cloro", hosted remotely at mcp.cloro.dev, as configured in cloro-dev/mcp-server.
api2mcp
Serve any OpenAPI 3.x / Swagger 2.x API as a local MCP (Model Context Protocol) server over stdio, proxying tool calls to the upstream HTTP API. Runs locally from the @swayam5342/api2mcp npm package.
mcpgate
A stateless gateway that turns any OpenAPI spec into MCP tools on the fly. Runs locally from the mcpgate Python package.
terminal49
Find and monitor ocean shipments and containers, and create new tracking requests. Remote server at mcp.terminal49.com.