Operations
Production health checks, source freshness, cache, and deployment gates.
Use operations endpoints before high-volume automation, launch checks, or freshness-sensitive agent workflows.
Health
curl -fsS https://mcp.aiworkflowmcp.com/healthHealthy production response:
{
"service": "aiworkflowmcp-cloudflare-v2",
"status": "ok",
"version": "2.0.0-cloudflare-native",
"data_quality": {
"freshness_status": "fresh",
"latest_eval_status": "PASS",
"top1_accuracy": 1,
"top3_recall": 1,
"trust_violations": 0
}
}Treat this as green:
statusisokdata_quality.freshness_statusisfreshdata_quality.latest_eval_statusisPASSdata_freshness.stale_entitiesis0data_freshness.source_errorsis0runtime.cache_statusisok
Source Status
curl -fsS https://api.aiworkflowmcp.com/v1/sources/statusUse source status when health is not green or a specific vendor result looks stale. The source list shows recent sync timestamps, hash state, error state, and refresh due status.
Rate-Limit Mode
/health exposes the active rate limiter:
{
"runtime": {
"rate_limit": {
"mode": "kv",
"limit_per_minute": 120,
"scope": "ip-minute",
"protected_mcp_methods": ["tools/call"]
}
}
}If mode is kv, Cloudflare KV is enforcing per-minute limits. Public calls are scoped by IP. Authenticated calls are scoped by API key.
Protected Paths
The Worker rate-limits high-volume read paths:
/v1/search/v1/models/list/v1/tools/list/v1/skills/list/v1/tutorials/list/v1/mcp-servers/list/v1/sources/status/v1/frameworks/list/v1/frameworks/search/v1/frameworks/route- detail paths for models, tools, skills, MCP servers, and frameworks
- MCP
tools/call
Deployment Gate
Before deploying docs or service changes:
bun run lint
bun --filter docs typecheck
bun --filter docs build
bun --filter docs cf:buildFor full repository releases:
bun run typecheck
bun run lint
bun run test
bun run buildProduction Smoke
curl -fsS https://mcp.aiworkflowmcp.com/health
curl -fsS "https://mcp.aiworkflowmcp.com/v1/models/list?limit=1"
curl -fsS "https://mcp.aiworkflowmcp.com/v1/search?type=DOC&q=claude%20code&limit=1"
curl -fsS https://aiworkflowmcp.com/en/docsAuthenticated smoke:
curl -fsS \
-H "Authorization: Bearer ${AIWORKFLOWMCP_API_KEY}" \
"https://mcp.aiworkflowmcp.com/v1/tools/list?limit=1"Incident Triage
Use this order:
- Check
/health. - Check
/v1/sources/status. - Check the failing REST or MCP call without
fresh_only=true. - Check the same call with an API key to separate public rate limit from service failure.
- If docs changed, verify
aiworkflowmcp.com/en/docs/...and/en/llms.mdx. - If web account changed, verify sign-in and API key creation from the production account page.