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.

ServerScan

REMOTE · WWW.SERVERSCAN.COM

PCI ASV scan prices, SAQ check, free payment page check, PCI guides and scan-failure fixes.

+6 this week 82 Trust /100

Last scanned (11 hours ago)

Scores higher than 85% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Security

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 Security80
Transport & Reachability100
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1486 tokens (~45/item across 33 items; 6 tools + 27 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 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 current MCP spec version (2026-07-28).Pass
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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +3
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: fail → pass ▲ functional
    • The server now declares the “resources” capability functional
    • First check of Schema quality: 100 functional
    • Schema quality: excellent → good functional
    • New resource “asv-scan-errors-cloudflare” functional
    • New resource “common-pci-scan-failures” functional
    • New resource “gdpr-and-pci-dss-scanning” functional
    • New resource “how-automated-external-penetration-testing-works” functional
    • New resource “payment-page-change-detection” functional
    • New resource “payment-page-monitoring-faq” functional
    • New resource “pci-compliance-scanning-solutions-for-your-business” functional
    • New resource “pci-dss-requirement-1-firewalls” functional
    • New resource “pci-dss-requirement-10-tracking-data-access” functional
    • New resource “pci-dss-requirement-12-maintaining-secure-policies” functional
    • New resource “pci-dss-requirement-2-vendor-defaults” functional
    • New resource “pci-dss-requirement-3-protect-data” functional
    • New resource “pci-dss-requirement-4-data-encryption” functional
    • New resource “pci-dss-requirement-5-anti-virus-malware” functional
    • New resource “pci-dss-requirement-6-secure-systems” functional
    • New resource “pci-dss-requirement-7-restricting-data-access” functional
    • New resource “pci-dss-requirement-8-authenticating-access” functional
    • New resource “pci-dss-requirement-9-restrict-physical-access” functional
    • New resource “pci-scanning-vs-penetration-testing” functional
    • New resource “penetration-testing” functional
    • New resource “remediation-partners” functional
    • New resource “scan-which-ip-addresses” functional
    • New resource “script-integrity-payment-pages” functional
    • New resource “security-verified-site-seal” functional
    • New resource “third-party-scripts-checkout” functional
    • New resource “web-application-penetration-testing” functional
    • New resource “which-saq-form” functional
    • Server version: 1.1.0 → 1.2.0 functional
    • New tool “fix_failed_scan” functional
    • New tool “search_guides” functional
  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_pricing” rewrote its description, which is the text the model reads security
    • Tool “start_order” rewrote its description, which is the text the model reads security
    • Schema quality: good → excellent functional
    • “start_order” reworded the description of “product” cosmetic
  • 23 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
    • Server version: 1.0.0 → 1.1.0 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 5 Nov 2026 · Probed https://www.serverscan.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=serverscan.com CN=YE1,O=Let's Encrypt,C=US 17 Sept 2026 16 Dec 2026 ECDSA 256 ECDSA-SHA384 549a3c9924a3274841cd7c3a99b4cbea9be
SANs: *.serverscan.com, serverscan.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.serverscan.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
serverscan.com. 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
content-security-policy default-src 'self' https:; img-src 'self' data: https:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-inline' https:;
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.serverscan.com/api/mcp Verified 200
http (plaintext) http://www.serverscan.com/api/mcp HTTPS enforced 301 https://www.serverscan.com/api/mcp
MCP tools · 6 exposed · ~710 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_payment_page ~144

Runs ServerScan's free one-off check of a payment or checkout page: TLS, security headers, the HTTP to HTTPS redirect, which scripts load and from where, and whether third-party scripts carry an integrity hash (PCI DSS 6.4.3 and 11.6.1). Returns six yes/no/not-yet-known answers and what to fix first. It fetches the page once. Any one site can be checked only a few times a day, and a repeat within 15 minutes returns the stored answer.

NameTypeReqDescription
urlstringyesThe payment page address, for example https://shop.example.com/checkout. A bare domain is read as https.

No output schema declared.

No examples provided.

do_i_need_an_asv_scan ~95

Says whether a merchant's PCI DSS self-assessment questionnaire (SAQ) requires quarterly external scans by an Approved Scanning Vendor, under PCI DSS v4.0.1, and what to scan. Pass the SAQ type, or "unsure" to get every SAQ with who it is for.

NameTypeReqDescription
saq_typestringyesThe merchant's SAQ, or "unsure".

No output schema declared.

No examples provided.

fix_failed_scan ~128

Explains a failed PCI ASV scan finding and how to fix it, for the ten most common causes: certificates, old TLS, unpatched software, open ports, default credentials, version banners, missing headers, insecure remote access, DNS and mail, and injection flaws. Pass the finding text from the scan report, or an issue name, or neither to list all ten.

NameTypeReqDescription
findingstring–The finding as the scan report words it, for example "TLS Version 1.0 Protocol Detection".
issuestring–The category, when the caller already knows it.

No output schema declared.

No examples provided.

get_pricing ~53

Current prices for ServerScan PCI ASV scanning (per domain or IP address), payment page monitoring and penetration testing of networks and web applications, read live from the store, with what each plan includes and the refund terms.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_guides ~111

Searches ServerScan's published guides on PCI DSS requirements, ASV scanning, scan failures, payment page monitoring and penetration testing. Returns up to five matching guides with a short excerpt and a link each. Use it to answer a PCI question from our own pages, then cite the link.

NameTypeReqDescription
querystringyesWhat to look for, in a few words. For example "requirement 11.6.1", "TLS 1.0 scan failure" or "SAQ A-EP".

No output schema declared.

No examples provided.

start_order ~179

Returns a link to ServerScan's signup page with the plan picked and the domain filled in, for the person to open, check and pay. Creates nothing and charges nothing. For a penetration test, of a network or of web applications, it returns the page to request a quote from.

NameTypeReqDescription
domainstring–asv_scanning only: the domain or IPv4 address to scan, filled into the signup form. A URL is cut down to its host.
include_monitoringboolean–asv_scanning only: add payment page monitoring to the scan plan.
productstringyesWhat to buy. penetration_test tests a network by IP address; web_app_penetration_test tests web applications and their APIs while logged in.
termstring–Billing term. Defaults to one_year, the cheaper per quarter.

No output schema declared.

No examples provided.

Install

How do I install the ServerScan MCP server?

ServerScan is a hosted endpoint at https://www.serverscan.com/api/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 · www.serverscan.com

# add to Claude Code
claude mcp add --transport http com-serverscan-mcp 'https://www.serverscan.com/api/mcp'
Common questions

What is the ServerScan MCP server?

ServerScan is an MCP server listed in the public MCP registry as com.serverscan/mcp. PCI ASV scan prices, SAQ check, free payment page check, PCI guides and scan-failure fixes. This page covers its hosted endpoint (https://www.serverscan.com/api/mcp).

Is the ServerScan MCP server safe to use?

ServerScan scores 82 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 ServerScan MCP server expose?

ServerScan exposes 6 tools: get_pricing, do_i_need_an_asv_scan, check_payment_page, start_order, search_guides, fix_failed_scan. Their descriptions and schemas cost roughly 710 tokens of context every time the server is loaded.

Does the ServerScan MCP server require authentication?

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

Is the ServerScan MCP server still maintained?

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