72hours security check

Name: 72hours security check
Author: maebsy

MCP serverMCP

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

by maebsyrepository ↗v1.30.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"72hours-security-check","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability8/8 checks ok

30 days ago

when	check	result	http	latency	detail
8 h ago	mcp initialize	ok	200	291 ms	server 72hours-service 1.30.0 · protocol 2025-06-18 · 15 tools
16 h ago	mcp initialize	ok	200	281 ms	server 72hours-service 1.30.0 · protocol 2025-06-18 · 15 tools
24 h ago	mcp initialize	ok	200	280 ms	server 72hours-service 1.30.0 · protocol 2025-06-18 · 15 tools
32 h ago	mcp initialize	ok	200	297 ms	server 72hours-service 1.30.0 · protocol 2025-06-18 · 15 tools
2 d ago	mcp initialize	ok	200	274 ms	server 72hours-service 1.30.0 · protocol 2025-06-18 · 15 tools
2 d ago	mcp initialize	ok	200	295 ms	server 72hours-service 1.30.0 · protocol 2025-06-18 · 15 tools
2 d ago	mcp initialize	ok	200	273 ms	server 72hours-service 1.30.0 · protocol 2025-06-18 · 15 tools
3 d ago	mcp initialize	ok	200	389 ms	server 72hours-service 1.30.0 · protocol 2025-06-18 · 15 tools

Tools observed via MCP handshake

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,con
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
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. S
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 a

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.maebsy/72hours

first seen 3 d ago · fetched 3 d agoopen ↗

Field history (6 recent events)

3 d ago · declared · summary → "Scan a public GitHub repo, explain risks, get fix prompts and rescan to confirm fixes."
3 d ago · declared · description → "Scan a public GitHub repo, explain risks, get fix prompts and rescan to confirm fixes."
3 d ago · declared · publisherName → "maebsy"
3 d ago · declared · repoUrl → "https://github.com/maebsy/YMCA-hackathon-2026"
3 d ago · declared · version → "1.1.0"
3 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from