Developer · Remote MCP server
SecScan
Scan, monitor and fix a live web app from your editor: graded security reports with fix prompts.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
us.secscan/secscan- Version
- 1.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-23
- Updated
- 2026-09-23
- Publisher
- us.secscan
- Namespace
- Namespace verified by the MCP Registry via the domain secscan.us · how
- Website
- secscan.info/ai-editors
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://secscan.us/api/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- secscan 1.1.0 · protocol 2025-06-18
- Tools discovered
- 12:
scan_url,get_scan_status,get_report,list_recent_scans,list_verified_domains,get_account,start_domain_verification,check_domain_verification,list_monitors,add_monitor,monitor_scan_now,dismiss_finding - Checked on
- 2026-10-05
How to connect SecScan
SecScan is a remote MCP server: there is nothing to install. Its endpoint is https://secscan.us/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| SecHelixEvidence-first security review of authorized repositories. Read-only, root-confined, no shell. | Local · stdio |
| Secretguard MCPScans code for hardcoded secrets (AWS, Stripe, GitHub, JWTs) before an AI agent commits it. | Local · stdio |
| Secrets Audit MCPDetects leaked secrets & API keys: 32+ provider rules (AWS, GitHub, Stripe, OpenAI…), zero deps. | Local · stdio |
| Secrets Leak AuditScan text and git diffs for committed credentials using real vendor key formats plus entropy. | Remote · HTTPLive check: sign-in required |
| SectoraThreat intel + your scans/findings/Shield posture. CVE, EPSS, KEV, package vuln lookup, DAST. | Remote · HTTPLive check: ✓ handshake |
| Secure FlowsMCP server for secureFlows (secure-flows.com). Alias of io.github.michal-lefler/secureflows-mcp. | Remote · HTTPLive check: ✓ handshake |
| Secure Schema MCPRead-only MCP server for exposing database schema metadata without row data. | Local · stdio |
| SecurecodeSecrets vault for Claude Code with audit logs, access rules, and AES-256 encryption. | Local · stdio |