FillTrust security questionnaire corpus
REMOTE · WWW.FILLTRUST.COM · SCANNED OCT 2
Guidance for answering vendor security questionnaires. Every result carries the page it came from.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 490 tokens (~98/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the FillTrust security questionnaire corpus MCP server?
FillTrust security questionnaire corpus is a hosted endpoint at https://www.filltrust.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.filltrust.com
claude mcp add --transport http com-filltrust-questions 'https://www.filltrust.com/api/mcp'
{
"mcpServers": {
"com-filltrust-questions": {
"url": "https://www.filltrust.com/api/mcp"
}
}
} {
"servers": {
"com-filltrust-questions": {
"type": "http",
"url": "https://www.filltrust.com/api/mcp"
}
}
} [mcp_servers.com-filltrust-questions] url = "https://www.filltrust.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-filltrust-questions": {
"type": "remote",
"url": "https://www.filltrust.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-filltrust-questions --url 'https://www.filltrust.com/api/mcp' --transport streamable-http
mcp_servers:
com-filltrust-questions:
url: "https://www.filltrust.com/api/mcp" {
"McpServers": {
"com-filltrust-questions": {
"Transport": "http",
"Url": "https://www.filltrust.com/api/mcp"
}
}
} assistant mcp add com-filltrust-questions -t streamable-http -u 'https://www.filltrust.com/api/mcp'
{
"mcpServers": {
"com-filltrust-questions": {
"type": "http",
"url": "https://www.filltrust.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Oct 26 +1
- Stability: 0.97 → pass security
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 2 Oct 2026 · Probed https://www.filltrust.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=filltrust.com | CN=WE1,O=Google Trust Services,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 6b6b56021ff4f1390e02b2017d9cb0b5 |
| SANs: filltrust.com, *.filltrust.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.filltrust.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| filltrust.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=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://www.googletagmanager.com https://*.google-analytics.com; font-src 'self' data:; connect-src 'self' https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com; frame-ancestors 'none'; form-action 'self'; base-uri 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.filltrust.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.filltrust.com/api/mcp | HTTPS enforced | 301 | https://www.filltrust.com/api/mcp |
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 →
get_filltrust_posture Read FillTrust's own security posture ~40
FillTrust's own answers to the questions it exists to answer, for anyone assessing it as a vendor. Includes the answers that are "no".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_question Read one question's guidance in full ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The slug from a search_questions result, for example "encryption-at-rest". |
No output schema declared.
No examples provided.
get_questionnaire_statistics What security questionnaires actually ask, measured ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| questionnaire | string | – | Optional. A named questionnaire to profile, for example "HECVAT" or "CAIQ". Omit for the corpus-wide topic counts. |
No output schema declared.
No examples provided.
list_standards List the standards the corpus covers ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_questions Search the questionnaire corpus ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many results to return. Defaults to 8. |
| query | string | yes | The questionnaire question, or words from it. Pasting the row from the spreadsheet works. |
No output schema declared.
No examples provided.
What is the FillTrust security questionnaire corpus MCP server?
FillTrust security questionnaire corpus is an MCP server listed in the public MCP registry as com.filltrust/questions. Guidance for answering vendor security questionnaires. Every result carries the page it came from. This page covers its hosted endpoint (https://www.filltrust.com/api/mcp).
Is the FillTrust security questionnaire corpus MCP server safe to use?
FillTrust security questionnaire corpus scores 80 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 FillTrust security questionnaire corpus MCP server expose?
FillTrust security questionnaire corpus exposes 5 tools: search_questions, get_question, list_standards, get_filltrust_posture, get_questionnaire_statistics. Their descriptions and schemas cost roughly 401 tokens of context every time the server is loaded.
Does the FillTrust security questionnaire corpus MCP server require authentication?
No. We connected to FillTrust security questionnaire corpus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FillTrust security questionnaire corpus MCP server still maintained?
FillTrust security questionnaire corpus is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.