72hours security check
REMOTE · OBOE-HANDINESS-ENROLL.NGROK-FREE.DEV
Scan a public GitHub repo, explain risks, get fix prompts and rescan to confirm fixes.
Available components
Last scanned (19 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (close_workspace). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 1967 tokens (~131/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (7% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.ngrok-free.dev | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5a41afeaafbd267d543db00f6d9469106fe |
| SANs: *.ngrok-free.dev, ngrok-free.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of oboe-handiness-enroll.ngrok-free.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| ngrok-free.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc | Verified | 200 | |
| http (plaintext) | http://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc | HTTPS enforced | 307 | https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_repository ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| authorized | boolean | – | – |
| max_analyses | integer | – | – |
| repository_url | string | yes | – |
| request_id | string | yes | – |
| workspace_token | string | – | – |
No output schema declared.
No examples provided.
audit_status ~45
Scan summary, analysis statuses and which fix prompts (get_fix_prompt) are ready, in one call.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | string | yes | – |
| workspace_token | string | yes | – |
No output schema declared.
No examples provided.
check_fix ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| authorized | boolean | – | – |
| request_id | string | yes | – |
| scan_id | string | yes | – |
| workspace_token | string | yes | – |
No output schema declared.
No examples provided.
close_workspace ~33
Revoke this workspace and its result access. Does not cancel already submitted backend jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_token | string | yes | – |
No output schema declared.
No examples provided.
create_workspace ~26
Create a private, expiring workspace. Save its capability only in the user's AI conversation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
generate_report ~41
Generate the service's report from owned server scan and available analyses, indicating incomplete work.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | string | yes | – |
| workspace_token | string | yes | – |
No output schema declared.
No examples provided.
get_analysis ~42
Poll GPU status and delivery gates; inference can take several minutes. Never fake ready results.
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_id | string | yes | – |
| workspace_token | string | yes | – |
No output schema declared.
No examples provided.
get_fix_prompt ~50
Get a gated real LLM proposal. Agent must inspect code, check repo/commit, fix and test in its workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_id | string | yes | – |
| workspace_token | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_scan ~47
Poll every >=10 seconds; on done return actual commit, coverage and up to 50 LLM-input findings.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | string | yes | – |
| workspace_token | string | yes | – |
No output schema declared.
No examples provided.
incident_report ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| incident | object | yes | – |
| kind | string | yes | – |
| scan_id | string | yes | – |
| workspace_token | string | yes | – |
No output schema declared.
No examples provided.
rescan ~61
Rescan the SAME repository default branch. Only published changes are visible; unpushed edits are not.
| Name | Type | Req | Description |
|---|---|---|---|
| authorized | boolean | – | – |
| previous_scan_id | string | yes | – |
| request_id | string | yes | – |
| workspace_token | string | yes | – |
No output schema declared.
No examples provided.
service_info ~20
Learn the whole workflow and available service capabilities before creating work.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_analysis ~48
Start GPU Red/Blue review of one real scan finding. Same inputs deduplicate.
| Name | Type | Req | Description |
|---|---|---|---|
| fingerprint | string | yes | – |
| scan_id | string | yes | – |
| workspace_token | string | yes | – |
No output schema declared.
No examples provided.
start_scan ~59
Start a REAL public GitHub scan. User authorization required. Reuse request_id on identical retries.
| Name | Type | Req | Description |
|---|---|---|---|
| authorized | boolean | – | – |
| repository_url | string | yes | – |
| request_id | string | yes | – |
| workspace_token | string | yes | – |
No output schema declared.
No examples provided.
verify_demo ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | – |
| verify_job_id | string | – | – |
No output schema declared.
No examples provided.
How do I install the 72hours security check MCP server?
72hours security check is a hosted endpoint at https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · oboe-handiness-enroll.ngrok-free.dev
claude mcp add --transport http maebsy-72hours 'https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc'
What is the 72hours security check MCP server?
72hours security check is an MCP server listed in the public MCP registry as io.github.maebsy/72hours. Scan a public GitHub repo, explain risks, get fix prompts and rescan to confirm fixes. This page covers its hosted endpoint (https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpc).
Is the 72hours security check MCP server safe to use?
72hours security check scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the 72hours security check MCP server expose?
72hours security check exposes 15 tools: service_info, create_workspace, close_workspace, start_scan, get_scan, and 10 more. Their descriptions and schemas cost roughly 891 tokens of context every time the server is loaded.
Does the 72hours security check MCP server require authentication?
No. We connected to 72hours security check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 72hours security check MCP server still maintained?
72hours security check is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.