OpenAPI Doctor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port number for the server | |
| FORCE_LISTEN | No | Force server to listen (for testing) | |
| PRO_API_KEYS | No | Comma-separated list of valid API keys for premium access | |
| X402_ENABLED | No | Enable x402 payment lane (true/false) | |
| KV_NAMESPACE_ID | No | Cloudflare KV namespace ID | |
| PUBLIC_BASE_URL | No | Public base URL (homepage) | |
| SERVICE_KEY_ENV | No | Environment variable name that holds the buyer's service key (e.g., DNS_DOCTOR_KEY) | |
| SERVICE_PRO_URL | No | URL for the hosted pro endpoint | |
| STRIPE_PLAN_NAME | No | Name of the Stripe plan | |
| STRIPE_KEY_PREFIX | No | Prefix for Stripe API keys (e.g., dns_) | |
| STRIPE_SECRET_KEY | No | Stripe secret key for payment processing | |
| CLOUDFLARE_API_TOKEN | No | Cloudflare API token for KV store | |
| CLOUDFLARE_ACCOUNT_ID | No | Cloudflare account ID for KV store | |
| STRIPE_WEBHOOK_SECRET | No | Stripe webhook signing secret |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_openapiA | Audit an OpenAPI/Swagger spec (URL to openapi.json or raw JSON) for API-security smells an agent won't catch reading prose: no security scheme, plaintext http servers, unauthenticated POST/PUT/DELETE, object-id endpoints with no auth (OWASP API1 BOLA/IDOR). Returns SECURE/REVIEW/INSECURE. deep=true lists the exact offending operations + fixes (premium). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no risk of ambiguity or confusion between tools.
A single tool follows a consistent naming pattern by default; no contradictions exist.
A single tool is slightly thin but appropriate for a focused security auditing server; the count does not feel excessive or insufficient for its niche purpose.
The tool covers the core auditing functionality well with options for deep analysis, though additional tools for spec validation or fixes could enhance completeness.