veto runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 15 Oct 2026.
Turn OpenAPI services into tools an agent can call under your rules.
What the code does
We read the source, 23 h ago · rules ccca72095570
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
return filepath.Join(dir, name)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to veto
same job, measured the same wayTurn any OpenAPI/Swagger spec into an MCP server - every API operation becomes an agent tool.
Turn any OpenAPI/Swagger spec into MCP tools. Zero config, zero code.
Auto-approve small agent actions under your rules; approval cards for the rest.
Turn OpenAPI / Postman specs into runnable MCP servers, or serve any API as live MCP tools.
Point Gecko at an OpenAPI spec; get first-call-correct, auth-hidden agent tools.
Database for your AI agent. Turn its output into data, docs, skills, and apps you can actually use.
MCP server that converts OpenAPI specs into tools which can query API endpoints
Turn any OpenAPI/Swagger spec into MCP tools — each operation an SSRF-guarded tool.
veto — questions
Answers built from our own checks of this server.