← Index

HAPI MCP Server

ai.com.mcp/hapi-mcp·v0.6.0·Other

HAPI MCP server: Dynamically exposes OpenAPI REST APIs as MCP tools for AI assistants

Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

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 →

Environment variables
HAPI_FQDN

Fully Qualified Domain Name for the HAPI server (used in MCP tool URLs)

HAPI_HOME

Directory path for HAPI configuration and specs. Should be mounted as a volume in Docker

PROJECT_NAME

The name of the project/API (alternative to positional argument)

HAPI_OPENAPI

OpenAPI spec URL or path (alternative to --openapi flag)

HAPI_URL

Backend API base URL (alternative to --url flag)

HAPI_PORT

Server port (alternative to --port flag) - this is the internal container port

HAPI_HEADLESS

Enable headless mode (alternative to --headless flag)

HAPI_MCP

Enable MCP mode (alternative to --mcp flag)

HAPI_DEV

Enable development mode (alternative to --dev flag)

HAPI_CORS

Comma-separated allowed CORS origins (alternative to --cors flag)

HAPI_CONFIG_FILES

Comma-separated configuration files (alternative to --filename flag)

NODE_ENV

Node environment (development, production). 'development' enables verbose logging and debugging features.

MCP quality score · maturity, not trust · methodology
freshness
15
completeness
20
installability
25
documentation
15
stability
5
Alternatives in Other