SecScan
REMOTE · SECSCAN.US · SCANNED OCT 1
Scan, monitor and fix a live web app from your editor: graded security reports with fix prompts.
Available components
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1276 tokens (~106/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
How do I install the SecScan MCP server?
SecScan is a hosted endpoint at https://secscan.us/api/mcp, 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 · secscan.us
claude mcp add --transport http us-secscan-secscan 'https://secscan.us/api/mcp'
{
"mcpServers": {
"us-secscan-secscan": {
"url": "https://secscan.us/api/mcp"
}
}
} {
"servers": {
"us-secscan-secscan": {
"type": "http",
"url": "https://secscan.us/api/mcp"
}
}
} [mcp_servers.us-secscan-secscan] url = "https://secscan.us/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"us-secscan-secscan": {
"type": "remote",
"url": "https://secscan.us/api/mcp",
"enabled": true
}
}
} openclaw mcp add us-secscan-secscan --url 'https://secscan.us/api/mcp' --transport streamable-http
mcp_servers:
us-secscan-secscan:
url: "https://secscan.us/api/mcp" {
"McpServers": {
"us-secscan-secscan": {
"Transport": "http",
"Url": "https://secscan.us/api/mcp"
}
}
} assistant mcp add us-secscan-secscan -t streamable-http -u 'https://secscan.us/api/mcp'
{
"mcpServers": {
"us-secscan-secscan": {
"type": "http",
"url": "https://secscan.us/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 1 Oct 26 +1
- Tool “scan_url” rewrote its description, which is the text the model reads security
- “scan_url” added an optional parameter “github_repo” cosmetic
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +2
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- Stability: unverified → 0.03 ▲ functional
- 26 Sept 26 +43
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Tool coverage: 93 functional
- First check of Schema quality: pass functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 36
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 1 Oct 2026 · Probed https://secscan.us/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=secscan.us | CN=WE1,O=Google Trust Services,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 44ec60ca0d96525913d81edfb73e0195 |
| SANs: secscan.us, *.secscan.us | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of secscan.us. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| us. | present | 59017 | 8 | Verified |
| secscan.us. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="secscan", resource_metadata="https://secscan.us/.well-known/oauth-protected-resource/api/mcp"
Bearer realm="secscan", resource_metadata="https://secscan.us/.well-known/oauth-protected-resource/api/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Protected resource metadata
| Document | https://secscan.us/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://secscan.us/api/mcp |
| Authorisation server | https://secscan.us |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://secscan.us/api/mcp | Verified | 200 | |
| http (plaintext) | http://secscan.us/api/mcp | HTTPS enforced | 301 | https://secscan.us/api/mcp |
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 →
add_monitor Monitor a site ~88
Put a site the user owns under continuous monitoring: hourly uptime checks, CVE matching, certificate alerts and regular rescans. Runs a full baseline scan straight away, which uses one of the user's scans exactly as in the app (free for plan holders). Returns the baseline scan_id for get_scan_status.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The site to monitor, e.g. https://example.com |
No output schema declared.
No examples provided.
check_domain_verification Check a domain verification ~62
Check whether the file or DNS record from start_domain_verification is live. On success the domain is verified and its next scan includes active tests. DNS changes can take a few minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain passed to start_domain_verification |
No output schema declared.
No examples provided.
dismiss_finding Dismiss a false positive ~99
Mark a finding as a false positive for this site, so future scans of it stop reporting it — the same as Dismiss in the app, and undoable there. ONLY use this after the user has confirmed the finding is wrong; never dismiss a real problem to improve a grade.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_name | string | yes | The finding's name exactly as get_report shows it |
| scan_id | string | yes | The scan whose report contains the finding |
No output schema declared.
No examples provided.
get_account Scans left and plan ~36
How many scans the user can still run — free scans, plan scans and credits — and their plan. Check this before starting several scans.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_report Read a scan report ~170
The finished report for a scan: grade, what the scan tested and what it skipped (a clean grade says nothing about skipped areas, so say so), prioritised findings with fixes and evidence, and a fix prompt written for the user's AI editor. Findings come 25 per page, most severe first — pass offset for the next page, or min_severity (e.g. "high") to focus on what matters most.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Findings per page (default 25, max 50) |
| min_severity | string | – | Only findings at this severity or worse, e.g. "high" |
| offset | integer | – | Skip this many findings, for the next page |
| scan_id | string | yes | The scan_id returned by scan_url or list_recent_scans |
No output schema declared.
No examples provided.
get_scan_status Check a scan ~83
Status of a scan (queued, scanning, analyzing, complete, failed). With wait_seconds (max 60) it waits for the scan to finish and returns the full report as soon as it does.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | string | yes | The scan_id returned by scan_url |
| wait_seconds | integer | – | Wait up to this long for the scan to finish |
No output schema declared.
No examples provided.
list_monitors List monitored sites ~48
Sites under continuous monitoring: latest grade, last and next scan, uptime check, CVE alerts, new problems in the last scan and certificate expiry. Use the monitor id with monitor_scan_now.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_recent_scans List recent scans ~29
The user's most recent scans with their status, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_verified_domains List verified domains ~51
Domains the user has proved they own. Only these receive active testing (injection, XSS, SSRF, access control); others get passive checks. Verify more at https://secscan.us/domains.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
monitor_scan_now Rescan a monitored site now ~78
Run a full scan of a monitored site now instead of waiting for its schedule — e.g. to confirm a fix. Free for plan holders; otherwise uses one of the user's scans, as in the app. Takes the monitor id from list_monitors.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor_id | string | yes | The monitor id from list_monitors or add_monitor |
No output schema declared.
No examples provided.
scan_url Scan a website ~173
Start a SecScan security scan of a web application the user owns or is authorised to test. Returns a scan_id; most scans finish in under a minute — then call get_scan_status with wait_seconds, or get_report. Active tests (injection, XSS, SSRF…) run only on domains the user has verified; others get passive checks. Optionally also reads a public GitHub repository for committed secrets (github_repo); that only contacts GitHub, never the site. Each scan uses one of the user's free scans, plan scans or credits.
| Name | Type | Req | Description |
|---|---|---|---|
| github_repo | string | – | Optional public GitHub repository to check for committed secrets, e.g. https://github.com/owner/repo. Public repositories only. |
| url | string | yes | The URL to scan, e.g. https://example.com |
No output schema declared.
No examples provided.
start_domain_verification Start verifying a domain ~113
Begin proving the user owns a domain, which unlocks active tests (injection, XSS, SSRF, access control) on its scans. Returns a file to publish on the site, or a DNS TXT record — an editor can usually add the file to the codebase and deploy it. Then call check_domain_verification. Calling it again returns the same token, so a record already published stays valid.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain, e.g. example.com or https://example.com |
No output schema declared.
No examples provided.
What is the SecScan MCP server?
SecScan is an MCP server listed in the public MCP registry as us.secscan/secscan. Scan, monitor and fix a live web app from your editor: graded security reports with fix prompts. This page covers its hosted endpoint (https://secscan.us/api/mcp).
Is the SecScan MCP server safe to use?
SecScan scores 83 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 SecScan MCP server expose?
SecScan exposes 12 tools: scan_url, get_scan_status, get_report, list_recent_scans, list_verified_domains, and 7 more. Their descriptions and schemas cost roughly 1,030 tokens of context every time the server is loaded.
Does the SecScan MCP server require authentication?
Yes. SecScan asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the SecScan MCP server still maintained?
SecScan is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.