Koskamo

SecScan MCP

A remote MCP server for the SecScan hosted web application security scanner. It allows AI editors like Claude Code and Cursor to initiate black-box security scans, monitor scan status, retrieve graded reports with AI-generated fix prompts, and manage continuous monitoring for verified domains.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

SecScan MCP logo, by SecScanVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by SecScan
MCP endpoint (Streamable HTTP)
https://secscan.us/api/mcp
Vendor documentation

What its tools do

12 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (6)

Can change data (1)

Not annotated (5)

12 of 12 have a description · 7 of 12 declare behavior hints · 8 of 9 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to secscan.us ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Scan a web application URL for security vulnerabilities
  • Retrieve graded security reports with AI fix prompts
  • Monitor scan status and list recent scans
  • Manage continuous monitoring for verified domains

Source and maintenance

Vendor evidenceRegistry 1.1.0
mcp-registry: us.secscan/secscan@1.1.0Project website

Protocol and capabilities

Server
secscan 1.1.0
MCP protocol negotiated in check
2025-11-25
Tools
12 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

SecScan scans a live web application from the outside and reports its security problems. Only scan applications the user owns or is authorised to test. Typical flow: scan_url -> get_scan_status with wait_seconds 60 (most scans finish in under a minute, and the call returns the report as soon as it does) -> for a large report, get_report with offset for more pages, or min_severity "high" to focus. Work through critical and high findings first, and use the fix prompt in the report — it is written for the user's editor. Active tests (injection, XSS, SSRF, access control) run only on domains listed by list_verified_domains; say so if a scan was passive-only. Each scan spends one of the user's free scans, plan scans or credits, so do not start a scan the user did not ask for. The same applies to add_monitor and monitor_scan_now; get_account says how many scans are left. To unlock active tests, use start_domain_verification, publish the file or DNS record it returns, then check_domain_verification. Only call dismiss_finding when the user has confirmed a finding is a false positive — never to improve a grade.

Tools

12 advertised

scan_url — Scan a website
Advertised by the server during the last successful anonymous check.
Open-world

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.

scan_url input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 2048,
      "minLength": 1,
      "description": "The URL to scan, e.g. https://example.com"
    },
    "github_repo": {
      "type": "string",
      "maxLength": 300,
      "description": "Optional GitHub repository to read, e.g. https://github.com/owner/repo. Public, or private if the user connected it under Connect GitHub on secscan.us."
    }
  },
  "additionalProperties": false
}
scan_url annotations
{
  "openWorldHint": true
}
get_scan_status — Check a scan
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

get_scan_status input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "scan_id"
  ],
  "properties": {
    "scan_id": {
      "type": "string",
      "description": "The scan_id returned by scan_url"
    },
    "wait_seconds": {
      "type": "integer",
      "maximum": 60,
      "minimum": 0,
      "description": "Wait up to this long for the scan to finish"
    }
  },
  "additionalProperties": false
}
get_scan_status annotations
{
  "readOnlyHint": true
}
get_report — Read a scan report
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

get_report input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "scan_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Findings per page (default 25, max 50)"
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Skip this many findings, for the next page"
    },
    "scan_id": {
      "type": "string",
      "description": "The scan_id returned by scan_url or list_recent_scans"
    },
    "min_severity": {
      "enum": [
        "critical",
        "high",
        "medium",
        "low",
        "info"
      ],
      "type": "string",
      "description": "Only findings at this severity or worse, e.g. \"high\""
    }
  },
  "additionalProperties": false
}
get_report annotations
{
  "readOnlyHint": true
}
list_recent_scans — List recent scans
Advertised by the server during the last successful anonymous check.
Advertised read-only

The user's most recent scans with their status, newest first.

list_recent_scans input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1
    }
  },
  "additionalProperties": false
}
list_recent_scans annotations
{
  "readOnlyHint": true
}
list_verified_domains — List verified domains
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

list_verified_domains input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
list_verified_domains annotations
{
  "readOnlyHint": true
}
get_account — Scans left and plan
Advertised by the server during the last successful anonymous check.
Advertised read-only

How many scans the user can still run — free scans, plan scans and credits — and their plan. Check this before starting several scans.

get_account input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
get_account annotations
{
  "readOnlyHint": true
}
start_domain_verification — Start verifying a domain
Advertised by the server during the last successful anonymous check.

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.

start_domain_verification input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "maxLength": 253,
      "minLength": 1,
      "description": "The domain, e.g. example.com or https://example.com"
    }
  },
  "additionalProperties": false
}
start_domain_verification annotations
{
  "idempotentHint": false
}
check_domain_verification — Check a domain verification
Advertised by the server during the last successful anonymous check.
Open-world

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.

check_domain_verification input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "maxLength": 253,
      "minLength": 1,
      "description": "The domain passed to start_domain_verification"
    }
  },
  "additionalProperties": false
}
check_domain_verification annotations
{
  "openWorldHint": true,
  "idempotentHint": true
}
list_monitors — List monitored sites
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

list_monitors input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
list_monitors annotations
{
  "readOnlyHint": true
}
add_monitor — Monitor a site
Advertised by the server during the last successful anonymous check.
Open-world

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.

add_monitor input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 2048,
      "minLength": 1,
      "description": "The site to monitor, e.g. https://example.com"
    }
  },
  "additionalProperties": false
}
add_monitor annotations
{
  "openWorldHint": true
}
monitor_scan_now — Rescan a monitored site now
Advertised by the server during the last successful anonymous check.
Open-world

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.

monitor_scan_now input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "monitor_id"
  ],
  "properties": {
    "monitor_id": {
      "type": "string",
      "description": "The monitor id from list_monitors or add_monitor"
    }
  },
  "additionalProperties": false
}
monitor_scan_now annotations
{
  "openWorldHint": true
}
dismiss_finding — Dismiss a false positive
Advertised by the server during the last successful anonymous check.
Advertised destructive

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.

dismiss_finding input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "scan_id",
    "finding_name"
  ],
  "properties": {
    "scan_id": {
      "type": "string",
      "description": "The scan whose report contains the finding"
    },
    "finding_name": {
      "type": "string",
      "maxLength": 300,
      "minLength": 1,
      "description": "The finding's name exactly as get_report shows it"
    }
  },
  "additionalProperties": false
}
dismiss_finding annotations
{
  "destructiveHint": true
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
394 ms
95th percentile latency
394 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 394 ms · metadata changed · 12 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http secscan-mcp https://secscan.us/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add secscan-mcp --url https://secscan.us/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable secscan-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "secscan-mcp": {
      "url": "https://secscan.us/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "secscan-mcp": {
      "type": "streamableHttp",
      "url": "https://secscan.us/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start secscan-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "secscan-mcp": {
      "type": "http",
      "url": "https://secscan.us/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http secscan-mcp https://secscan.us/api/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://secscan.us/api/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "secscan-mcp": {
      "serverUrl": "https://secscan.us/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like SecScan MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 8,787

Do you run SecScan MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing