Security & Testing

filltrust.com

Provides guidance and evidence for answering security compliance questionnaire questions, including standards and control references.

1 endpoint4 known toolsFirst detected September 3, 2026Last detected September 3, 2026

ENDPOINT 1

https://www.filltrust.com/api/mcp

No auth detected

MCP server metadata

Name: filltrust
Version: 1.0.0

Capabilities

tools

Server instructions

Guidance on answering vendor security questionnaires (CAIQ, SIG Lite, ISO 27001 Annex A), published by FillTrust. Search for the question you have been asked, then read the full guidance for it. Every result carries the URL of the page it came from; cite it. Model answers are templates with the specifics deliberately blank, to be filled from the company's own documentation. Do not assert a control that no document supports.

Known tools 4

search_questions

Find guidance on how to answer a security questionnaire question.

Inferred read-only

get_question

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.

Inferred read-only

list_standards

Which questionnaire standards this corpus answers questions from, how many questions each has, and which controls are cited.

Inferred read-only

get_filltrust_posture

FillTrust's own answers to the questions it exists to answer, for anyone assessing it as a vendor.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.filltrust]
url = "https://www.filltrust.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "filltrust": {
      "type": "http",
      "url": "https://www.filltrust.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: filltrust
Remote MCP URL: https://www.filltrust.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "filltrust": {
      "url": "https://www.filltrust.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "filltrust",
  "transport": "streamable-http",
  "url": "https://www.filltrust.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.