protogrid

Search / com.filltrust/questions

FillTrust security questionnaire corpus

R0· no sign-in

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

v1.0.0 · active · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality79good
Trust79of 100
Uptime, 30 days96%
Latency p50613 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "questions": {
      "type": "http",
      "url": "https://www.filltrust.com/api/mcp"
    }
  }
}
claude mcp add --transport http questions https://www.filltrust.com/api/mcp
[mcp_servers.questions]
url = "https://www.filltrust.com/api/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "questions": {
      "type": "remote",
      "url": "https://www.filltrust.com/api/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "questions": {
      "type": "http",
      "url": "https://www.filltrust.com/api/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=questions&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vd3d3LmZpbGx0cnVzdC5jb20vYXBpL21jcCJ9"
}
{
  "servers": {
    "questions": {
      "type": "http",
      "url": "https://www.filltrust.com/api/mcp"
    }
  }
}
{
  "mcpServers": {
    "questions": {
      "httpUrl": "https://www.filltrust.com/api/mcp"
    }
  }
}
extensions:
  "questions":
    enabled: true
    name: "questions"
    type: streamable_http
    uri: "https://www.filltrust.com/api/mcp"
    timeout: 300

Quality 79 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene71 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • fail
    tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_question (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_questions (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_filltrust_posture (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
  • pass
    tools.token_costabout 543 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
  • pass
    stability.changesno tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

5 tools, about 543 tokens to load them all · tool set 9e2bdfc42b76 · checked 2026-10-20 10:35 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 79 / 100

no-repository
provenance55
liveness98
freshness85
hygiene80

+dns-namespace +website +reachable +uptime-96% ~updated-48d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://www.filltrust.com/api/mcp streamable-httpnoneyes96%613 ms2025-06-182026-10-20

Tools (5)

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

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "com.filltrust/questions",
  "title": "FillTrust security questionnaire corpus",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://www.filltrust.com/api/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.0",
  "websiteUrl": "https://www.filltrust.com/mcp",
  "description": "Guidance for answering vendor security questionnaires. Every result carries the page it came from."
}