Is the Secscan MCP server down?

mcp-registry/us.secscan/secscan · v1.1.0

As of 2026-10-22 15:19 UTC, the Secscan MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

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

claude mcp add --transport http secscan-mcp-server https://secscan.us/api/mcp

{
  "mcpServers": {
    "secscan-mcp-server": {
      "type": "http",
      "url": "https://secscan.us/api/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (86/100)

What to fix (4)

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fus.secscan%2Fsecscan/fixes

{
  "name": "add_monitor",
  "description": "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.",
  "inputSchema": {
    "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
  },
  "annotations": {
    "openWorldHint": true,
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Monitor a site"
}

{
  "name": "check_domain_verification",
  "description": "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.",
  "inputSchema": {
    "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
  },
  "annotations": {
    "openWorldHint": true,
    "idempotentHint": true,
    "readOnlyHint": true
  },
  "title": "Check a domain verification"
}

{
  "name": "start_domain_verification",
  "description": "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.",
  "inputSchema": {
    "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
  },
  "annotations": {
    "idempotentHint": false,
    "readOnlyHint": false,
    "destructiveHint": false
  },
  "title": "Start verifying a domain"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/us.secscan/secscan"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/us.secscan/secscan"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~1,901 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.97% uptime over 30 days.

Largest tool definitions

• get_report ~285 tokens
• scan_url ~282 tokens
• start_domain_verification ~193 tokens
• dismiss_finding ~190 tokens
• add_monitor ~169 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fus.secscan%2Fsecscan.svg)](https://glimind.com/server/mcp-registry%2Fus.secscan%2Fsecscan?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fus.secscan%2Fsecscan?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fus.secscan%2Fsecscan.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fus.secscan%2Fsecscan.svg
   :target: https://glimind.com/server/mcp-registry%2Fus.secscan%2Fsecscan?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8e727be73f6d4185…, first seen 2026-10-17, included at leaf 2347 of 46,667. Version history · verify what your client received.

Tools (12)

• add_monitor
• check_domain_verification
• dismiss_finding
• get_account
• get_report
• get_scan_status
• list_monitors
• list_recent_scans
• list_verified_domains
• monitor_scan_now
• scan_url
• start_domain_verification

Compare: most reliable security servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Secscan MCP server down right now?

As of 2026-10-22 15:19 UTC, the Secscan MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

How many tools does Secscan MCP server provide?

Secscan MCP server advertises 12 tools, including add_monitor, check_domain_verification, dismiss_finding, get_account, get_report.

How do I install Secscan MCP server?

Point your MCP client at this streamable-http endpoint: https://secscan.us/api/mcp

Is the Secscan MCP server safe to connect to an AI agent?

Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Secscan MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.