openapi-anything (schniggie/openapi-anything) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 4 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
6 days ago

openapi-anything

Enables creating and using REST APIs from natural language descriptions, with MCP tools to generate, manage, and interact with deployed API wrappers.

→ schniggie/openapi-anything· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

schniggie

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: GATEWAY_API_KEY, LITELLM_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configPROXY_TIMEOUTGateway → wrapper proxy timeout (s)
configMCP_SPEC_TTLopenapi.json (cached s).
configXDG_RUNTIME_DIR
configGATEWAY_PROXY_HOSTHost wrappers are reachable on from the gateway
🔐 secretGATEWAY_API_KEYOpt-in: unset (default) and the gateway is fully open, as before.
configHEALTH_SWEEP_INTERVALSeconds between registry health sweeps
configHEALTH_PROBE_TIMEOUTPer-wrapper /health probe timeout (s)
configJOBS_HISTORY_MAXTerminal jobs kept in history before pruning oldest
configMETRICS_FLUSH_INTERVALSeconds between metric flushes to redis
configNAME
configLITELLM_BASE_URLOpenAI-compatible LLM proxy
🔐 secretLITELLM_API_KEYProxy API key — set via .env, never commit it
configLLM_REQUEST_TIMEOUTPer-request timeout (s)
configLLM_MODELModel id (must match proxy /v1/models)
configLLM_JSON_MAX_TOKENSJSON-mode budget — reasoning models burn hidden thinking tokens against it
configWRAPPER_OUTPUT_BASEGenerated wrapper code directory
configPIPELINE_MAX_RETRIESLLM fix-loop attempts before the safe fallback
configSEARXNG_BASE_URLresearch via a SearxNG instance (, default
configSEARXNG_TIMEOUTSearch request timeout (s)
configSEARXNG_MAX_RESULTSResearch hits fed into inspection/design
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployREDIS_URL
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

4/4 tools missing one or more hints — list_apis (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); generate_api (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); regenerate_api (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +1 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/schniggie/openapi-anything)](https://m8ven.ai/mcp/schniggie/openapi-anything)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: bdc7a9d7003a798dcab7c94c5816e54273d86b02
code hash: 41b0223fb47539ca41d81282b978dcbe723235d138685e5cd0ffc7cebb68e863
verified: 9/6/2026, 7:30:49 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client