Skip to content

SecScan MCP server

us.secscan/secscansecscan.usstreamable-httpv1.1.0Scanned

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

12 tools: 1 can delete or cancel things, 5 change things and 6 only read.

Tools: 1 delete, 0 irreversible, 5 write, 6 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the SecScan MCP server can do

The SecScan MCP server is published by secscan.us, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (1 tool: dismiss_finding) and create or change data (5 tools: scan_url, start_domain_verification, check_domain_verification, add_monitor and 1 more). 6 tools only read.

4 tools bring in text other people can write (scan_url, check_domain_verification, add_monitor and 1 more); 2 tools can send data out of your system (scan_url and add_monitor).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Deletes or cancels 1Claude Code: deny
  • dismiss_findingMark 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.No findings

    Why it is in this group

    • The name "dismiss_finding" says "dismiss": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
Changes things 5Claude Code: ask
  • add_monitorPut a site the user owns under continuous monitoring: hourly uptime checks, CVE matching, certificate alerts and regular rescans.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "add_monitor" says "add": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • openWorldHint: true
  • check_domain_verificationCheck whether the file or DNS record from start_domain_verification is live.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • idempotentHint: true
    • openWorldHint: true
  • monitor_scan_nowRun a full scan of a monitored site now instead of waiting for its schedule — e.g.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • openWorldHint: true
  • scan_urlStart a SecScan security scan of a web application the user owns or is authorised to test.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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 GitHub repository's source (github_repo): any public one, or a private one the user connected at secscan.us. That only contacts GitHub, never the site. Each scan uses one of the user's free scans, plan scans or credits.

    Annotations the server declares

    • openWorldHint: true
  • start_domain_verificationBegin proving the user owns a domain, which unlocks active tests (injection, XSS, SSRF, access control) on its scans.No findings

    Why it is in this group

    • The name "start_domain_verification" says "start": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • idempotentHint: false
Only reads 6Show 6 read-only tools
  • get_accountHow many scans the user can still run — free scans, plan scans and credits — and their plan.No findings

    Why it is in this group

    • The name "get_account" says "get": a word for reading.
    Description, as the server wrote it
    How many scans the user can still run — free scans, plan scans and credits — and their plan. Check this before starting several scans.

    Annotations the server declares

    • readOnlyHint: true
  • get_reportThe 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 evi…No findings

    Why it is in this group

    • The name "get_report" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • get_scan_statusStatus of a scan (queued, scanning, analyzing, complete, failed).No findings

    Why it is in this group

    • The name "get_scan_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • list_monitorsSites under continuous monitoring: latest grade, last and next scan, uptime check, CVE alerts, new problems in the last scan and certificate expiry.No findings

    Why it is in this group

    • The name "list_monitors" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • list_recent_scansThe user's most recent scans with their status, newest first.No findings

    Why it is in this group

    • The name "list_recent_scans" says "list": a word for reading.
    Description, as the server wrote it
    The user's most recent scans with their status, newest first.

    Annotations the server declares

    • readOnlyHint: true
  • list_verified_domainsDomains the user has proved they own.No findings

    Why it is in this group

    • The name "list_verified_domains" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:20 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://secscan.us/.well-known/oauth-protected-resource/api/mcp
Authorization servers
https://secscan.us
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 destructive, 5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://secscan.us/api/mcp: tools/list returned 12 tools to an anonymous client, including dismiss_finding (destructive), scan_url (write), start_domain_verification (write), check_domain_verification (write), add_monitor (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http secscan https://secscan.us/api/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http secscan https://secscan.us/api/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__secscan__get_scan_status",
      "mcp__secscan__get_report",
      "mcp__secscan__list_recent_scans",
      "mcp__secscan__list_verified_domains",
      "mcp__secscan__get_account",
      "mcp__secscan__list_monitors"
    ],
    "ask": [
      "mcp__secscan__scan_url",
      "mcp__secscan__start_domain_verification",
      "mcp__secscan__check_domain_verification",
      "mcp__secscan__add_monitor",
      "mcp__secscan__monitor_scan_now"
    ],
    "deny": [
      "mcp__secscan__dismiss_finding"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as secscan. Review it before you use it.

Capability tags behind 4 rules
  • mcp__secscan__scan_url untrusted-input, outbound
  • mcp__secscan__check_domain_verification untrusted-input
  • mcp__secscan__add_monitor untrusted-input, outbound
  • mcp__secscan__monitor_scan_now untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/us.secscan/secscan/verify?hash=0e394976ddc6ef7e2132e82edaaf5e8836fd6a9e1533e43c02991e437a9ad568" | jq -e '.changed == false'

Pinned hash 0e394976ddc6, from Nov 19, 2026, 11:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/us.secscan/secscan/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for us.secscan/secscan
[![Anlyon Radar](https://radar.anlyon.com/badge/us.secscan/secscan.svg)](https://radar.anlyon.com/servers/us.secscan/secscan)

Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.

SecScan MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the SecScan MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the SecScan MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: dismiss_finding.

Can the SecScan MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the SecScan MCP server have?

12 tools: 1 destructive, 5 write, 6 read. dismiss_finding, scan_url, start_domain_verification, check_domain_verification, add_monitor, monitor_scan_now, get_scan_status, get_report and 4 more.

Does the SecScan MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SecScan MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): scan_url and add_monitor.

Has the SecScan MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.