72hours security check MCP Server

by maebsy Your server? Claim it

answering

72hours security check is answering right now. Last checked 1 min ago. It exposes 15 tools. Last commit 1 Nov 2026.

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

Uptime history 11 hours of history

11 hours agonow

100.0%

Uptime 24h

39 of 39 checks

Tools

read from the server

637 ms

Response time

average over 24h

Stars

last commit 1 Nov 2026

Nothing serious here today

Today is the operative word: we check 72hours security check every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc

~/.codex/config.toml

[mcp_servers.72hours]
url = "https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

audit

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 summary + next steps. Reuse request_id only for the SAME request.

audit_status

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

fix

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.

get_fix_prompt

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

start

start_analysis

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

start_scan

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

analysis

get_analysis

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

close_workspace

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

generate

generate_report

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

incident

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, affected_count, items}. Use only user-confirmed facts.

rescan

rescan

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

scan

get_scan

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

service

service_info

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

verify

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, pass its verify_job_id to keep polling the same job.

workspace

create_workspace

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

Endpoints

URL	Transport	State	Latency	Checked
https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc	streamable-http	answering	633 ms	1 min ago

Alternatives to 72hours security check

same job, measured the same way

Cra Check

by holistis

Free read-only check of a public GitHub repo for eight security signals related to the EU CRA.

1 tools answering

SecScan

by secscan

Scan, monitor and fix a live web app from your editor: graded security reports with fix prompts.

12 tools answering

Evolize

by evolize

Accessibility scans with evidence, public reports, and fresh checks after fixes.

3 tools answering

Jikida

by jikida

Security tools for your AI: scan, pentest, check headers, guard code and scan repos for secrets.

147 installs/wk local only

Compuute MCP Security Scanner

by compuute

Scan any public GitHub MCP-server repo for security issues. 37 MCP-specific L1 rules, 8 languages.

1 tools answering

ProdForge

by cloudcorprecords

Connects MCP servers, packages, security checks, and release gates in one repo.

270 installs/wk local only

Regulatory Signals

by rikocr8orh8

Audit GitHub repos for security, compliance, and EU AI Act exposure from Claude or Cursor.

67 installs/wk local only

Repo Security Scanner — Malicious Code & Supply Chain

by eltociear

Audit GitHub repos for malicious and supply-chain code before you depend on them.

answering

72hours security check — questions

Answers built from our own checks of this server.

What can 72hours security check do?

It exposes 15 tools, read directly from the server on our last check. Among them: audit_repository, audit_status, check_fix, close_workspace, create_workspace, generate_report and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is 72hours security check mostly used for?

Its tools cluster around start, audit and fix. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is 72hours security check working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 39 of 39 checks got a reply (100.0%), average response time 637 ms. The bar chart above shows every period we have measured.

How do I connect 72hours security check?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does 72hours security check need an API key?

No. 72hours security check completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is 72hours security check?

It answers our handshake in 637 ms on average, which is faster than 16% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is 72hours security check open source?

We cannot say either way: written in Python, 0 stars on GitHub and 2 open issues, but we could not determine the licence, and without one the code is not open source by default.