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/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/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/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="Reviewed on agentmods" width="80" 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 1mo 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.
- 1mo 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 (6 stars, last pushed 1mo 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
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.
mcpify
CLI tool that generates an MCP server from OpenAPI specs automatically. Runs locally from the @bahridev/mcpify npm package.
openapi-mcp-proxy
CLI tool to create an MCP server exposing services from an OpenAPI specification. Runs locally from the openapi-mcp-proxy npm package.
smbcloud-cli
Email infrastructure and authentication for developers: domains, inbox routes, auth apps, deploys. Runs locally from the @smbcloud/cli npm package. Needs 1 environment variable to run.
mcp-server-saxo-openapi
MCP server for Saxo Bank OpenAPI spec lookup with pitfalls guide (offline; no trading). Runs locally from the mcp-server-saxo-openapi Python package.
openapi-mcp-server
A Model Context Protocol (MCP) server that exposes OpenAPI endpoints as MCP tools. Runs locally from the @lucid-spark/openapi-mcp-server npm package.