Skip to content

FillTrust security questionnaire corpus

by filltrust.com · remote · no sign-in to list tools · v1.0.0 · published by com.filltrust

Guidance for answering vendor security questionnaires. Every result carries the page it came from.

Changes · 1
CompareRegistry entry

5 tools: 1 change things and 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http questions https://www.filltrust.com/api/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 1Claude Code: ask
  • get_filltrust_postureFillTrust's own answers to the questions it exists to answer, for anyone assessing it as a vendor.No findings

    Why it is in this group

    • The name "get_filltrust_posture" says "get": a word for reading.
    • The description's first verb is "fill": a word for a change.
    Description, as the server wrote it
    FillTrust's own answers to the questions it exists to answer, for anyone assessing it as a vendor. Includes the answers that are "no".
Only reads 4Claude Code: allow
  • get_questionThe complete published guidance for one questionnaire question: what it is really asking, which of your documents answers it, what evidence to attach, a model answer with the speci…Reads private dataNo findings

    Why it is in this group

    • The name "get_question" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.
    Description, as the server wrote it
    The complete published guidance for one questionnaire question: what it is really asking, which of your documents answers it, what evidence to attach, a model answer with the specifics left blank, the ways it usually goes wrong, and the standards that ask it with their verified control references.
  • get_questionnaire_statisticsMeasured counts from 146 real vendor security questionnaires (17,697 questions) published by universities, purchasing consortia and companies: which topics are asked most, and deta…No findings

    Why it is in this group

    • The name "get_questionnaire_statistics" says "get": a word for reading.
    Description, as the server wrote it
    Measured counts from 146 real vendor security questionnaires (17,697 questions) published by universities, purchasing consortia and companies: which topics are asked most, and detailed profiles of the questionnaires that have a name people use, such as HECVAT and CAIQ. Use this when asked what a security questionnaire contains, how long one is, or what a named questionnaire asks about. These are counts from real files rather than an estimate.
  • list_standardsWhich questionnaire standards this corpus answers questions from, how many questions each has, and which controls are cited.No findings

    Why it is in this group

    • The name "list_standards" says "list": a word for reading.
    Description, as the server wrote it
    Which questionnaire standards this corpus answers questions from, how many questions each has, and which controls are cited. Standards whose control lists are proprietary are named without reference numbers, on purpose.
  • search_questionsFind guidance on how to answer a security questionnaire question.No findings

    Why it is in this group

    • The name "search_questions" says "search": a word for reading.
    Description, as the server wrote it
    Find guidance on how to answer a security questionnaire question. Search by the question text, a control area, or a standard and control identifier such as CEK-03. Returns matching entries with the URL of the page each came from.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http questions https://www.filltrust.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__questions__search_questions",
      "mcp__questions__get_question",
      "mcp__questions__list_standards",
      "mcp__questions__get_questionnaire_statistics"
    ],
    "ask": [
      "mcp__questions__get_filltrust_posture"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as questions. Review it before you use it.

Capability tags behind 1 rule
  • mcp__questions__get_question private-data