72hours security check

Reliability

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

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

15 tools

• service_info

  Learn the whole workflow and available service capabilities before creating work.

• create_workspace

  Create a private, expiring workspace. Save its capability only in the user's AI conversation.

• close_workspace

  Revoke this workspace and its result access. Does not cancel already submitted backend jobs.

• start_scan

  Start a REAL public GitHub scan. User authorization required. Reuse request_id on identical retries.

• get_scan

  Poll every >=10 seconds; on done return actual commit, coverage and up to 50 LLM-input findings.

• start_analysis

  Start GPU Red/Blue review of one real scan finding. Same inputs deduplicate.

• get_analysis

  Poll GPU status and delivery gates; inference can take several minutes. Never fake ready results.

• get_fix_prompt

  Get a gated real LLM proposal. Agent must inspect code, check repo/commit, fix and test in its workspace.

• rescan

  Rescan the SAME repository default branch. Only published changes are visible; unpushed edits are not.

• generate_report

  Generate the service's report from owned server scan and available analyses, indicating incomplete work.

• incident_report

  Draft only; NEVER submits. kind: assess/incident-24h/privacy-72h. incident requires discovered_at ISO time; optional organization {name,service_name,contact_email}, summary, incident_types, damage, actions_taken, personal_info {leaked: confirmed/suspected/none…

• audit_repository

  One call security audit of a PUBLIC GitHub repo the user is authorized to scan. Creates a workspace if workspace_token is empty (keep the returned token private), scans, waits up to 90 s, starts GPU analysis for the top max_analyses (0-5) findings and returns…

• audit_status

  Scan summary, analysis statuses and which fix prompts (get_fix_prompt) are ready, in one call.

• check_fix

  After fixes are PUSHED to the default branch: rescan the same repo against scan_id and list resolved, persisting, new and key-reissue-needed findings. Same commit means the fix was not pushed yet.

• verify_demo

  Runtime proof on the DEMO target only: isolated sandbox replays attacks before/after the fix and runs functional tests. mode: reference (human fix) or ai (Red/Blue generated attacks and fix). Not the user's repo. If a previous call returned status queued/running…

Security scan

Recent checks