# FillTrust security questionnaire corpus (remote · www.filltrust.com)

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

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-02

## Components

- remote · `www.filltrust.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-filltrust-questions/api-mcp.md), [page](https://verifymcp.io/servers/com-filltrust-questions/api-mcp)

## Channel facts

- Endpoint: `https://www.filltrust.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-02.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 490 tokens (~98/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "com-filltrust-questions": {
      "url": "https://www.filltrust.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-filltrust-questions": {
      "type": "http",
      "url": "https://www.filltrust.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-filltrust-questions]
url = "https://www.filltrust.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-filltrust-questions": {
      "type": "remote",
      "url": "https://www.filltrust.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-filltrust-questions --url 'https://www.filltrust.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-filltrust-questions:
    url: "https://www.filltrust.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-filltrust-questions": {
      "Transport": "http",
      "Url": "https://www.filltrust.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-filltrust-questions -t streamable-http -u 'https://www.filltrust.com/api/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-02 (score 80, +1)

- [security] Stability: 0.97 → pass

### 2026-09-30 (score 79, +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.

### 2026-09-28 (score 78, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 77, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 76, +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.

### 2026-09-21 (score 75, +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.

### 2026-09-19 (score 74, +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.

### 2026-09-17 (score 73, +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.

## MCP tools (5)

### `search_questions` (~96 tokens)

Search the questionnaire corpus

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.

Input parameters:

- `limit` (integer): How many results to return. Defaults to 8.
- `query` (string, required): The questionnaire question, or words from it. Pasting the row from the spreadsheet works.

### `get_question` (~85 tokens)

Read one question's guidance in full

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.

Input parameters:

- `slug` (string, required): The slug from a search_questions result, for example "encryption-at-rest".

### `list_standards` (~46 tokens)

List the standards the corpus covers

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.

### `get_filltrust_posture` (~40 tokens)

Read FillTrust's own security posture

FillTrust's own answers to the questions it exists to answer, for anyone assessing it as a vendor. Includes the answers that are "no".

### `get_questionnaire_statistics` (~134 tokens)

What security questionnaires actually ask, measured

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.

Input parameters:

- `questionnaire` (string): Optional. A named questionnaire to profile, for example "HECVAT" or "CAIQ". Omit for the corpus-wide topic counts.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-filltrust-questions/api-mcp#diagnostics

## Score history

- 2026-10-02: 80
- 2026-10-01: 79
- 2026-09-30: 79
- 2026-09-29: 78
- 2026-09-28: 78
- 2026-09-27: 77
- 2026-09-26: 77
- 2026-09-25: 77
- 2026-09-24: 76
- 2026-09-23: 76
- 2026-09-22: 75
- 2026-09-21: 75
- 2026-09-20: 74
- 2026-09-19: 74
- 2026-09-18: 73
- 2026-09-17: 73
- 2026-09-16: 72
- 2026-09-15: 72
- 2026-09-14: 71
- 2026-09-13: 71
- 2026-09-12: 70
- 2026-09-11: 70
- 2026-09-10: 70
- 2026-09-09: 69
- 2026-09-08: 69
- 2026-09-07: 68
- 2026-09-06: 68
- 2026-09-05: 67
- 2026-09-04: 67
- 2026-09-03: 66

## Common questions

### 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.

## Links

- Remote endpoint: https://www.filltrust.com/api/mcp
- Website: https://www.filltrust.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-filltrust-questions/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-filltrust-questions/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-filltrust-questions/api-mcp