HAPI MCP Server
HAPI MCP server: Dynamically exposes OpenAPI REST APIs as MCP tools for AI assistants
Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.
Own this server? Screen its description →
HAPI_FQDNFully Qualified Domain Name for the HAPI server (used in MCP tool URLs)
HAPI_HOMEDirectory path for HAPI configuration and specs. Should be mounted as a volume in Docker
PROJECT_NAMEThe name of the project/API (alternative to positional argument)
HAPI_OPENAPIOpenAPI spec URL or path (alternative to --openapi flag)
HAPI_URLBackend API base URL (alternative to --url flag)
HAPI_PORTServer port (alternative to --port flag) - this is the internal container port
HAPI_HEADLESSEnable headless mode (alternative to --headless flag)
HAPI_MCPEnable MCP mode (alternative to --mcp flag)
HAPI_DEVEnable development mode (alternative to --dev flag)
HAPI_CORSComma-separated allowed CORS origins (alternative to --cors flag)
HAPI_CONFIG_FILESComma-separated configuration files (alternative to --filename flag)
NODE_ENVNode environment (development, production). 'development' enables verbose logging and debugging features.
AI-powered trading strategy development: backtesting, market data, and portfolio analysis
Feature flagging and A/B testing platform with AI-first experimentation workflows.
Query Meta Ads performance data — accounts, campaigns, ad sets, ads, metrics & settings.