SimplyScan
REMOTE · API.SIMPLYSCAN.IO
Security, SEO and AI-visibility scanner for web apps · free scans and focused checks via MCP.
Available components
Last scanned (14 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
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 Security54
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 612 tokens (~76/item across 8 items; 8 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 Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "scan_local_code" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “scan_website” rewrote its description, which is the text the model reads security
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 7 Nov 26 +1
- Stability: 0.97 → pass security
- 6 Nov 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
- Stability: 0.97 → pass security
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 21 Nov 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 | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 6934f393abf16c4f0eabd9f0c167cd75 |
| 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 secure
Validation of api.simplyscan.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| simplyscan.io. | DS published | 2371 | 13 | Verified |
| api.simplyscan.io. | Verified address RRset verified with the apex keys |
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 | 405 |
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 →
check_ai_visibility Check AI visibility (AEO) ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full https URL to check |
No output schema declared.
No examples provided.
check_email_security Check email security (SPF/DKIM/DMARC) ~48
Check a domain's email authentication: SPF, DKIM (common selectors), and DMARC policy. Flags spoofable domains.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain, e.g. example.com |
No output schema declared.
No examples provided.
check_exposed_files Check for exposed files ~51
Probe a site for accidentally exposed high-risk files (.env, .git/config, backups, etc.). Reports HTTP status only, never file contents.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full https URL to check |
No output schema declared.
No examples provided.
check_security_headers Check security headers ~59
Grade a URL's HTTP security headers (CSP, HSTS, X-Frame-Options, Referrer-Policy, Permissions-Policy, COOP, COEP) A-F.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full https URL to check |
No output schema declared.
No examples provided.
check_seo Check on-page 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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full https URL to check |
No output schema declared.
No examples provided.
check_ssl Check SSL/TLS certificate ~51
Inspect a domain's SSL/TLS certificate: issuer, expiry, protocol, and flags for expiring/self-signed/mismatched certs.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain, e.g. example.com |
No output schema declared.
No examples provided.
scan_local_code Scan local code ~100
Send selected editor file contents to the SimplyScan Security Engine's deterministic repository rules. Requires a Pro API key. Source leaves the editor, is processed in memory, and is not retained; masked findings are saved in the private scan record. No AI provider receives these files. Code rules analyse JavaScript and TypeScript; other files are checked for secrets only. When no file can be analysed, the result has no score.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | – |
No output schema declared.
No examples provided.
scan_website Scan website ~98
Run a SimplyScan Security Engine security & speed scan (account required; Pro with an entitled API key, otherwise free) 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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full https URL to check |
No output schema declared.
No examples provided.
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
claude mcp add --transport http io-simplyscan-simplyscan 'https://api.simplyscan.io/mcp'
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 76 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 8 tools: scan_website, scan_local_code, check_security_headers, check_ai_visibility, check_seo, and 3 more. Their descriptions and schemas cost roughly 531 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the SimplyScan MCP server?
VerifyMCP ran 11 checks on SimplyScan, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about SimplyScan: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.