Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SimplyScan

REMOTE · API.SIMPLYSCAN.IO · SCANNED SEP 30

Security, SEO and AI-visibility scanner for web apps · free scans and focused checks via MCP.

+7 this week 84 Trust /100
Trust breakdown (7 categories)

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 Security69
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 466 tokens (~66/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
Install

How do I install the SimplyScan MCP server?

SimplyScan is a hosted endpoint at https://api.simplyscan.io/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 · api.simplyscan.io

# add to Claude Code
claude mcp add --transport http io-simplyscan-simplyscan 'https://api.simplyscan.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-simplyscan-simplyscan": {
      "url": "https://api.simplyscan.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-simplyscan-simplyscan": {
      "type": "http",
      "url": "https://api.simplyscan.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-simplyscan-simplyscan]
url = "https://api.simplyscan.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-simplyscan-simplyscan": {
      "type": "remote",
      "url": "https://api.simplyscan.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-simplyscan-simplyscan --url 'https://api.simplyscan.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-simplyscan-simplyscan:
    url: "https://api.simplyscan.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-simplyscan-simplyscan": {
      "Transport": "http",
      "Url": "https://api.simplyscan.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-simplyscan-simplyscan -t streamable-http -u 'https://api.simplyscan.io/mcp'
// mcp.json
{
  "mcpServers": {
    "io-simplyscan-simplyscan": {
      "type": "http",
      "url": "https://api.simplyscan.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 28 Sept 26 +7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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
  • 26 Aug 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 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
  • 31 Jul 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
  • 30 Jul 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
  • 27 Jul 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
Diagnostics

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 30 Sept 2026 · Probed https://api.simplyscan.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=simplyscan.io CN=WE1,O=Google Trust Services,C=US 4 Sept 2026 3 Dec 2026 ECDSA 256 ECDSA-SHA256 fe63f82197ea524a13ad09627958d0fe
SANs: simplyscan.io, api.simplyscan.io, *.api.simplyscan.io
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 api.simplyscan.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
simplyscan.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.simplyscan.io/mcp Verified 200
http (plaintext) http://api.simplyscan.io/mcp Inconclusive 406
MCP tools · 7 exposed · ~416 tokens

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 →

Tool Tokens
check_ai_visibility ~64

AEO check: whether AI answer engines (ChatGPT/GPTBot, Claude, Perplexity, Google-Extended, etc.) can crawl and cite the site, plus llms.txt and structured-data signals.

NameTypeReqDescription
urlstringyesFull https URL to check

No output schema declared.

No examples provided.

check_email_security ~48

Check a domain's email authentication: SPF, DKIM (common selectors), and DMARC policy. Flags spoofable domains.

NameTypeReqDescription
domainstringyesDomain, e.g. example.com

No output schema declared.

No examples provided.

check_exposed_files ~51

Probe a site for accidentally exposed high-risk files (.env, .git/config, backups, etc.). Reports HTTP status only, never file contents.

NameTypeReqDescription
urlstringyesFull https URL to check

No output schema declared.

No examples provided.

check_security_headers ~59

Grade a URL's HTTP security headers (CSP, HSTS, X-Frame-Options, Referrer-Policy, Permissions-Policy, COOP, COEP) A-F.

NameTypeReqDescription
urlstringyesFull https URL to check

No output schema declared.

No examples provided.

check_seo ~60

On-page SEO audit of a URL: title, meta description, H1, canonical, indexability, Open Graph, structured data, image alt coverage, sitemap. Returns an A-F grade.

NameTypeReqDescription
urlstringyesFull https URL to check

No output schema declared.

No examples provided.

check_ssl ~51

Inspect a domain's SSL/TLS certificate: issuer, expiry, protocol, and flags for expiring/self-signed/mismatched certs.

NameTypeReqDescription
domainstringyesDomain, e.g. example.com

No output schema declared.

No examples provided.

scan_website ~83

Run a free SimplyScan security & speed scan of a deployed web app URL. Returns a 0-100 score and findings (exposed secrets, missing Supabase RLS, frontend leaks, speed issues). Best for apps built with Lovable, Bolt, v0, Cursor, Replit, etc.

NameTypeReqDescription
urlstringyesFull https URL to check

No output schema declared.

No examples provided.

Common questions

What is the SimplyScan MCP server?

SimplyScan is an MCP server listed in the public MCP registry as io.simplyscan/simplyscan. Security, SEO and AI-visibility scanner for web apps · free scans and focused checks via MCP. This page covers its hosted endpoint (https://api.simplyscan.io/mcp).

Is the SimplyScan MCP server safe to use?

SimplyScan scores 84 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 SimplyScan MCP server expose?

SimplyScan exposes 7 tools: scan_website, check_security_headers, check_ai_visibility, check_seo, check_ssl, and 2 more. Their descriptions and schemas cost roughly 416 tokens of context every time the server is loaded.

Does the SimplyScan MCP server require authentication?

No. We connected to SimplyScan without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SimplyScan MCP server still maintained?

SimplyScan is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.