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/tiago-marques/x-openapi-flow/x-openapi-flow-mcpgit clone --depth 1 https://github.com/tiago-marques/x-openapi-flowWrote 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/tiago-marques/x-openapi-flow/x-openapi-flow-mcp)<a href="https://agentmods.dev/mcp/tiago-marques/x-openapi-flow/x-openapi-flow-mcp"><img src="https://agentmods.dev/badge/mcp/tiago-marques/x-openapi-flow/x-openapi-flow-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
x-openapi-flow-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 5d 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
{
"x-openapi-flow-mcp": {
"command": "npx",
"args": [
"-y",
"x-openapi-flow"
],
"env": {}
}
}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.
- 5d ago First seen · 10 lines scan A 24a28e15ac7c
x-openapi-flow-mcp is an MCP server published in the GitHub repository tiago-marques/x-openapi-flow (5 stars, last pushed 4mo 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
engram-server
MCP server "engram-server" as configured in jamjet-labs/jamjet. Runs in Docker (ghcr.io/jamjet-labs/engram-server:0.5.0).
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.
manifold
MCP server "manifold" as configured in nonchan7720/manifold. Runs in Docker (ghcr.io/nonchan7720/manifold:v1.9.0). Needs 2 environment variables to run.
tempguru-event-staffing
MCP server "tempguru-event-staffing", hosted remotely at mcp.tempguru.co, as configured in Tempguru-co/tempguru-agent-skills.
phone-validation
Validate phone numbers worldwide: carrier, line type, country, E.164. x402. Remote server at phone-validation.api.klymax402.com.
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.