← All servers

72hours security check

connects

oboe-handiness-enroll.ngrok-free.dev

Scan a public GitHub repo, explain risks, get fix prompts and rescan to confirm fixes.

https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpcNo authMCP 2025-11-25v1.30.0last checked 1 Nov 2026spoke MCP on 1 of 1 check (30 days)initialize in 580 ms

Last checked 1 Nov 2026

✓Answered the MCP handshake (MCP 2025-11-25)
✓Auth detected: No auth
✓Lists 15 tools
✓No blockers or warnings
✓Spoke MCP on 1 of 1 check (30 days)

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The endpoint answers an anonymous handshake, so no credential is needed.

claude mcp add --transport http 72hours-security-check https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Connectors → Add custom connector, then paste https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "mcpServers": {
    "72hours-security-check": {
      "url": "https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "servers": {
    "72hours-security-check": {
      "type": "http",
      "url": "https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 1 Nov 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 15 tools listable

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

No server card

Neither the reserved <endpoint>/server-card location nor the domain's /.well-known/ai-catalog.json describes this endpoint (SEP-2127), so a client that discovers servers by domain will not find it.

Tools

audit_repositoryaudit_statuscheck_fixclose_workspacecreate_workspacegenerate_reportget_analysisget_fix_promptget_scanincident_reportrescanservice_infostart_analysisstart_scanverify_demo

Contract history

1 Nov 2026v1.30.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Route it through the gateway

Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.

Add to my gateway

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/72hours-security-check/badge.svg)](https://mcpi.app/servers/72hours-security-check)