openapi-to-mcp
What this skill does
Build and deploy an MCP server from an OpenAPI / Swagger spec using the mcp-use TypeScript SDK. The skill ingests OpenAPI specs, maps operations to tools, scaffolds code, wires auth, tests, and deploy
github/mcp-use - Privilege Escalation - 10.5k stars
Threat analysis
Skill info
pkg:github/mcp-use/mcp-use@afcc55d?skill=openapi-to-mcpAssessments (3)
Privilege Escalation
Privilege Escalation via local-llm-review
references/deploy.md
Secrets in your local `.env` so you can transcribe them to the dashboard later. **Don't push `.env`** - confirm it's in `.gitignore`.Privilege Escalation via local-llm-review
references/testing.md
Make sure .env has the right secrets (and is gitignored)Privilege Escalation via local-llm-review
references/auth.md
The rule of thumb: never put secrets in the conversation, never commit them, and never bake them into `index.ts`. Everything goes through `process.env` so the same code runs locally and in production.Badge
Add the Anomity scan badge for openapi-to-mcp to your README.
How Anomity governs this at runtime
Scan-time vetting tells you what a skill says it will do. Anomity's Endpoint Sensor sees what agents actually do: it discovers skills alongside every other AI artifact on the endpoint, and runtime governance can allow, deny, or log the tool calls a skill triggers. Policy violations route to your SIEM, Slack, email, or Jira, backed by a queryable 90-day audit trail.
Book a 30-minute demo to see your own skill inventory.
Methodology and disputes
Every skill is assessed by the Anomity Skill Intelligence engine against its public source; findings indicate risk patterns, not confirmed exploitation. Maintainer of openapi-to-mcp? Report an issue or request a rescan.
