PCI DSS self-assessment questionnaire finder: free MCP tool
Call the PCI DSS self-assessment questionnaire finder from your AI as a free MCP tool, no account: the inputs, a worked request and response, and how to add the server.
pci_dss_saq_type is one of the 20 free GRC tools from ISMS Copilot that any AI client can call over MCP: no account, no model, one call.
Reads which PCI DSS v4.0.1 self-assessment questionnaire (SAQ A, A-EP, B, B-IP, C-VT, C, P2PE or D) a merchant's payment setup most likely maps to, or whether a service-provider route or no PCI DSS applies, with the reasons. Answer every question (the input schema lists them with their options); with any question unanswered the tool returns the open questions instead of a verdict. The verdict is a reading from fixed rules, not a legal conclusion. Returns general information from a fixed rule set; confirm against the official text.
This page is about calling the tool from an AI client: the request, the response and the setup. For the same tool on the web, with the background on the rules it applies, open the PCI DSS self-assessment questionnaire finder page.
Inputs
The tool's input schema, as tools/list returns it, field by field.
| Field | What it is | Allowed values |
|---|---|---|
answers | One answer per question, keyed by question id. Every question needs an answer before a verdict is computed. | object (fields below) |
answers.role | Which best describes your organisation's relationship to card payments? A merchant accepts payment cards for its own goods or services. A service provider stores, processes, or transmits cardholder data on behalf of other organisations (for example a payment gateway, a hosting provider inside the cardholder data environment, or a managed-service provider), or can otherwise affect the security of a payment. Pick the closest fit for the part of your business you are assessing; if your organisation does both, run this check once per role. | merchant (We are a merchant: we accept payment cards for our own goods or services.), service-provider (We are a service provider: we store, process, or transmit cardholder data on behalf of other organisations, or can affect the security of their card payments.), no-card-data (Neither: we never store, process, or transmit cardholder data and cannot affect the security of a card payment.), unsure (It is not yet clear which of these describes us.) |
answers.storesCardData | Does your organisation electronically store cardholder data (the full card number) after a payment is authorised, anywhere in your own systems? Cardholder data means the primary account number, alone or with the cardholder name, expiry date, or service code. Storage counts wherever it lands: a database, a spreadsheet, a CRM record, application logs, call recordings, or email. It does not count if a validated third party holds the data and you only ever handle a token or a truncated number. Electronic storage of cardholder data removes eligibility for every reduced questionnaire, so this question is decisive; if you are not certain, say so rather than guessing. | yes (Yes, cardholder data is stored electronically somewhere in our systems.), no (No, we do not electronically store cardholder data.), unsure (We are not sure whether cardholder data is stored anywhere in our systems.) |
answers.setup | How are card payments handled in the part of your business you are assessing? Pick the single option that best fits how cards are actually accepted. Each setup maps to a different questionnaire because it changes which of your systems can touch cardholder data. If you accept cards in more than one way (for example a website and a shop counter), assess the channel with the widest exposure, or run this check once per channel. Answer for the merchant role; a service provider's result does not depend on this question. | ecom-fully-outsourced (Online, fully outsourced and your site cannot affect the payment page: the customer is redirected to a validated third party's page, or the provider's payment page is embedded (for example in an iframe), and your website never receives card data and does not serve, generate, or control any element or script on the payment page.), ecom-controls-redirect (Online, and your website can affect the security of the payment page: a validated third party processes the payment, but your site serves or generates part of the payment form, uses a direct-post integration, or runs scripts that shape the payment page. Your systems do not store card data.), moto-outsourced (Mail order or telephone order (card-not-present): all card handling is outsourced to a validated third party and no card data is kept on your systems.), virtual-terminal (Virtual terminal: staff key one transaction at a time into a validated third party's web-based virtual terminal on an isolated computer; no card data is stored.), p2pe (In person, P2PE only: payments are taken through a solution listed as a validated PCI point-to-point encryption (P2PE) solution, and no card data is stored electronically.), terminal-dialout (In person, standalone dial-out terminals or imprint machines only: the terminals connect over a phone line (not the internet) and no card data is stored electronically.), terminal-ip (In person, standalone IP terminals only: standalone approved terminals with an internet (IP) connection to the processor, and no card data is stored electronically.), integrated-pos (Payment applications or an integrated point-of-sale system connected to the internet, with no electronic storage of card data.), other-or-stores (None of these fits, or our own systems store or process card data more directly than the options above.), unsure (It is not yet clear which of these describes our setup.) |
answers.level | What is your card-payment validation tier? The card brands sort merchants into validation levels by yearly transaction volume, and the top tier typically validates through an onsite assessment that produces a Report on Compliance rather than a self-assessment. Thresholds and the exact validation method are set by each brand and your acquirer, but the largest merchants (Visa, for example, treats more than roughly six million transactions a year for a brand as its top level), any merchant a brand has designated to that tier, and any merchant that has suffered a card-data breach are typically in it. This question never changes which SAQ describes your environment; it flags whether you may use the questionnaire at all. | top-tier (Top tier: we are among the largest-volume merchants, a card brand has designated us to its highest validation level, or we have had a card-data breach.), self-assess (Below the top tier: our transaction volume is in a range the card brands generally let us self-assess.), unsure (We do not know our validation level.) |
If an answer is missing
The tool never guesses an answer. A call with any field left out returns status: "needs_answers" and the open questions, each with its id, its text and its allowed values, and no result. Your AI can ask you those questions and call again.
Worked example
This request and response come from the tool itself: the catalog runs the tool's handler on this example input, and this page is generated from that catalog.
Request
A tools/call request, as your client sends it:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "pci_dss_saq_type",
"arguments": {
"answers": {
"role": "merchant",
"storesCardData": "no",
"setup": "ecom-fully-outsourced",
"level": "self-assess"
}
}
}
}Response
The structuredContent of the result. The result's text content says the same in plain words, with the disclaimer.
{
"status": "result",
"verdict": {
"id": "saq-a",
"reading": "Reading from fixed rules, not a legal conclusion: Your setup maps to SAQ A",
"page_title": "Your setup maps to SAQ A",
"summary": "On your answers you are a card-not-present merchant (e-commerce or mail/telephone order) who has outsourced all handling of cardholder data to validated third parties, keeps no cardholder data on your own systems, and cannot affect the security of the payment page. That is the smallest questionnaire, SAQ A. One v4.0.1 detail to watch: the newer script-protection eligibility criteria for SAQ A apply to e-commerce merchants who embed the third party's payment page or form in their own page (for example an iframe), not to a plain redirect or a payment link, so confirm which pattern you use. The obligations block below summarises what completing PCI DSS validation involves.",
"tone": "in"
},
"reasons": [
{
"code": "saq-a-fully-outsourced",
"text": "You indicated you accept cards only online with the payment handled entirely by a validated third party (a redirect to, or an embedded page from, the provider), your site never receives card data, and your site cannot affect the security of the payment page. That fully-outsourced e-commerce pattern is the basis for SAQ A, the smallest questionnaire. Where you embed the provider's page (for example in an iframe), the v4.0.1 SAQ A eligibility criteria add a script-protection expectation for that embedded page; a plain redirect or payment link is outside that specific criterion."
},
{
"code": "reduced-saq-no-storage",
"text": "This reduced questionnaire is available only because you indicated no cardholder data is stored electronically. If that changes, or if any other system in the environment starts to touch card data, re-run this check: storage or wider exposure moves you to SAQ D."
},
{
"code": "validation-set-by-acquirer",
"text": "The SAQ your environment maps to describes the control scope, but whether you may self-assess with that questionnaire, and your merchant level, are set by the card brands and your acquiring bank. Confirm both with your acquirer; they differ by brand and region."
},
{
"code": "merchant-scope-note",
"text": "This result is for the merchant role you are assessing. Scope it to the specific payment channel: if you accept cards in more than one way, the widest-exposure channel drives the questionnaire, or you can assess each channel separately."
}
],
"obligations": [
"Complete the applicable Self-Assessment Questionnaire each year, or a Report on Compliance where your validation level requires an assessment by a Qualified Security Assessor, and sign the Attestation of Compliance.",
"Where any in-scope system is reachable from the internet, have an Approved Scanning Vendor run passing external vulnerability scans at least every quarter, as required for the questionnaires that call for them.",
"Meet the PCI DSS v4.0.1 control areas that your questionnaire covers: protect stored account data and encrypt cardholder data in transit, build and maintain secure networks and systems, restrict access on a need-to-know basis and authenticate every user, log and monitor access, test security regularly, and maintain a security policy and awareness programme.",
"Reduce scope wherever you can: not storing cardholder data, tokenisation, validated point-to-point encryption, and outsourcing card handling to validated third parties all shrink the cardholder data environment and can move you to a shorter questionnaire.",
"Keep a current list of the third-party service providers that store, process, or transmit cardholder data on your behalf or could affect its security, and monitor their PCI DSS status; you remain responsible for the data you hand them.",
"Confirm your merchant level and validation type with your acquiring bank and the card brands, and re-check them when your transaction volume changes or after any suspected card-data incident."
],
"answered": 4,
"total": 4,
"basis": [
"PCI DSS v4.0.1 Self-Assessment Questionnaires and their eligibility criteria"
],
"sources_checked_on": [
{
"source": "PCI Security Standards Council, Document Library (PCI DSS v4.0.1, the Self-Assessment Questionnaires, and the SAQ Instructions and Guidelines)",
"checked_on": "2026-07-11"
},
{
"source": "PCI Security Standards Council Bulletin: SAQs for PCI DSS v4.0.1 Now Available",
"checked_on": "2026-07-11"
},
{
"source": "PCI Security Standards Council blog: FAQ Clarifies New SAQ A Eligibility Criteria for E-Commerce Merchants",
"checked_on": "2026-07-11"
},
{
"source": "Visa, Account Information Security (AIS) Program and PCI (merchant validation levels are set by the card brands)",
"checked_on": "2026-07-11"
}
],
"disclaimer": "General information from a fixed rule set, not legal advice. Check the result against the official text and with a qualified professional before you act on it.",
"more": {
"url": "https://www.ismscopilot.com/mcp?ref=mcp-tool-pci-dss-saq-checker",
"label": "Review your own documents against this framework with ISMS Copilot"
},
"tool_page": "https://www.ismscopilot.com/resources/pci-dss-saq-checker"
}What the result rests on
Every result names its basis, as identifiers only (never standard text):
- PCI DSS v4.0.1 Self-Assessment Questionnaires and their eligibility criteria
Sources the rules were checked against, with the date each was last checked:
- PCI Security Standards Council, Document Library (PCI DSS v4.0.1, the Self-Assessment Questionnaires, and the SAQ Instructions and Guidelines), checked 2026-07-11
- PCI Security Standards Council Bulletin: SAQs for PCI DSS v4.0.1 Now Available, checked 2026-07-11
- PCI Security Standards Council blog: FAQ Clarifies New SAQ A Eligibility Criteria for E-Commerce Merchants, checked 2026-07-11
- Visa, Account Information Security (AIS) Program and PCI (merchant validation levels are set by the card brands), checked 2026-07-11
Add the server
claude mcp add --scope user --transport http ismscopilot-free-tools 'https://www.ismscopilot.com/api/public/tools/mcp'That is Claude Code. For claude.ai, Claude Desktop, ChatGPT, Cursor, Codex and any other client, see Add the server to your client. No sign-in, no token.
Limits
General information from a fixed rule set, not legal advice. Check the result against the official text and with a qualified professional before you act on it.
Your inputs are never logged or stored by our code. We count calls per tool (the tool name, whether it produced a result and when, nothing else). Our host keeps standard request logs (time, path, status, client address) for a short period. Do not send personal data: no tool needs any.
A fixed rule cannot read your own policies, registers or contracts. For a review of your own documents, connect ISMS Copilot, the GRC expert your AI calls.