72hours security check
Scan a public GitHub repo, explain risks, get fix prompts and rescan to confirm fixes.
What it does
72hours security check is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 3h ago (live check)Hosted endpoint
https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpcstreamable-http
In Claude Code: claude mcp add --transport http 72hours-security-check https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"72hours-security-check": {
"url": "https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc"
}
}
}Live check
Electra Index connected to the hosted endpoint 3h agoONLINE 72hours security check answered an MCP connection on 31 Oct 2026 and introduced itself as 72hours-service 1.30.0 (MCP protocol 2025-06-18).
15 tools offered to AI assistants
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: confaudit_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) f
Show 3 more
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
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc | DECLARED | SRC-001 Official MCP Registry | 3h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 3h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 3h ago |
| Repository | https://github.com/maebsy/YMCA-hackathon-2026 | DECLARED | SRC-001 Official MCP Registry | 3h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 3h ago |
| Version | 1.1.0 | DECLARED | SRC-001 Official MCP Registry | 3h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 3h ago |
Change history
- NEW31 Oct 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is 72hours security check still online?
Free alerts · no account▲ 0Do you run 72hours security check? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about 72hours security check
How do I connect 72hours security check?
Use the hosted endpoint https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does 72hours security check offer?
When Electra Index connected on 31 Oct 2026, it listed 15 tools: service_info, create_workspace, close_workspace, start_scan, get_scan, start_analysis, get_analysis, get_fix_prompt and more. The full list is in "Live check" above.
Is 72hours security check online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 3h ago.