Public API · Read-only · No auth

Handshake probe

Call a remote MCP URL the same way Influzer does in the catalog: initialize then tools/list. You get live status, tool count, and whether an auth gate answered — not a safe-to-install badge. Embed this in CI, internal catalogs, and README checks.

PROBE ENDPOINT

https://www.influzer.ai/api/v1/probe

curl

curl -sS "https://www.influzer.ai/api/v1/probe?url=https://www.influzer.ai/mcp/discovery"

CI check

STATUS=$(curl -sS "https://www.influzer.ai/api/v1/probe?url=$MCP_URL" | jq -r .live_status)
# live_ok or auth_required are handshakes. unreachable is a ticket.
test "$STATUS" != "unreachable"

GitHub Action on mcp.json

Handshake every HTTPS URL in Cursor/VS Code mcp.json. Stdio entries are skipped. Not a SAFE badge.

- uses: rmencke2/logo/.github/actions/probe-mcp-json@main
  with:
    file: .cursor/mcp.json

node scripts/probe-mcp-json.js --file .cursor/mcp.json

What you get

live_status — live_ok, auth_required, or unreachable
auth_gate — 401/403 seen vs none detected
tool_count + tool names from live tools/list
catalog — Influzer listings that already use this URL
safety_badge is always null

MCP Discovery · Agent skill · Not “safe” — just honest · Browse Top 100