Skip to content

MCP Gateway Verification#

After setup and starting the gateway, run a few checks to ensure it’s operational.

Using the provided script#

make gateway-verify
# or
scripts/verify_servers.sh

This will:

  1. Check health endpoint
curl -fsS http://$HOST:$PORT/health | jq .
# Expect: { "status": "ok" }
  1. List registered servers
# Generate a short‑lived admin JWT
ADMIN_TOKEN=$(
  source mcpgateway/.venv/bin/activate
  python3 -m mcpgateway.utils.create_jwt_token \
    --username "$BASIC_AUTH_USER" \
    --secret   "$JWT_SECRET_KEY" \
    --exp 60
)

curl -u "$BASIC_AUTH_USER:$BASIC_AUTH_PASSWORD" \
  -H "Authorization: Bearer $ADMIN_TOKEN" \
  http://$HOST:$PORT/servers | jq .
# Expect an empty list: []

  1. (Optional) Additional smoke tests

  2. Probe any custom agent endpoints you may have registered

  3. Tail logs: tail -f mcpgateway/logs/mcpgateway.log for errors/warnings

Manual Verification#

  1. Open browser Navigate to http://localhost:4444/admin/, log in with your Basic Auth user (default admin/changeme).

  2. Inspect Dashboard

  3. No agents listed initially

  4. Check “Servers” tab to confirm the gateway itself is registered

  5. API calls Try a few calls with curl or Postman to /health, /servers, etc.