Compliance Assessment Tool: PCI DSS SAQ + AoC

com.complianceassessmenttoolPublished by complianceassessmenttool.comOfficial publisherv1.2.1Updated Nov 1, 2026

PCI DSS self-assessment for merchants: picks the SAQ, guides the answers, returns SAQ + AoC PDFs.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that helps merchants complete PCI DSS self-assessment questionnaires and produce SAQ and AoC PDFs.

What you can do
  • Select the appropriate PCI DSS SAQ type for a merchant's situation.
  • Guide the user through answering the self-assessment questions.
  • Generate the completed SAQ and Attestation of Compliance (AoC) as PDF documents.
When to use it
Useful when a merchant needs to work through a PCI DSS self-assessment questionnaire and obtain SAQ and AoC documents, with the assistant handling questionnaire selection and answer guidance.
Requirements
Remote streamable HTTP endpoint at api.complianceassessmenttool.com; no local install. Authentication is required: OAuth, or an X-API-Key header holding a CAT partner API key (live or sandbox). A free sandbox key is available by signing up on the provider's site.
Before you install
The server requires a partner API key sent in the X-API-Key header, so treat it as a secret. Assessment answers and compliance details are submitted to a third-party service, and the generated SAQ and AoC documents are formal compliance records, so review them before relying on or submitting them.

Installation

In SourceWeft

  1. Open Compliance Assessment Tool: PCI DSS SAQ + AoC in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.complianceassessmenttool%2Fpci-compliance/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "compliance-assessment-tool-pci-dss-saq-a": {
      "type": "http",
      "url": "https://api.complianceassessmenttool.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.2.1LatestNov 1, 2026
  2. v1.2.0Nov 1, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.