FillTrust security questionnaire corpus
Measured conclusion: Deep-tested. L2 outcome: tools_ok.
Guidance for answering vendor security questionnaires. Every result carries the page it came from.
| Author | com.filltrust |
|---|---|
| Access | remote |
| Publisher key required | No |
| Measured state | Deep-tested |
| L1 liveness | alive |
| L1 latency | 2660 ms |
| Last measured | 2026-10-26 |
Add to your agent
Copy this into your MCP client config:
{
"mcpServers": {
"FillTrust security questionnaire corpus": {
"url": "https://www.filltrust.com/api/mcp",
"transport": "streamable-http"
}
}
}
Measured tools (5)
search_questionsFind 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.
Parameters:
query(required) — string — The questionnaire question, or words from it. Pasting the row from the spreadsheet works.limit— integer — How many results to return. Defaults to 8.
Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared
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 specifics left blank, the ways it usually goes wrong, and the standards that ask it with their verified control references.
Parameters:
slug(required) — string — The slug from a search_questions result, for example "encryption-at-rest".
Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared
list_standardsWhich 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.
Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared
get_filltrust_postureFillTrust's own answers to the questions it exists to answer, for anyone assessing it as a vendor. Includes the answers that are "no".
Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared
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 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.
Parameters:
questionnaire— string — Optional. A named questionnaire to profile, for example "HECVAT" or "CAIQ". Omit for the corpus-wide topic counts.
Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared
Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.