_ registry / mcp streamable-http · checked 34m ago

filltrust

https://www.filltrust.com

Registry code: d146493591b64b46

api record

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.

endpoint
https://www.filltrust.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is filltrust live?
Yes — it answered the hub's last check (checked 34m ago). It answered 100% of checks over the last 30 days.
Is filltrust free to use?
Yes — the hub reached it with no key and no payment.
What tools does filltrust have?
5 tools: get_filltrust_posture, list_standards, search_questions, get_question, get_questionnaire_statistics.
Is filltrust safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.5%

90 days 99.7%· all time 99.7%

latency
219ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 355 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
topic
security & compliance compliance & regulation
used for
  • find guidance for a security questionnaire question
  • get model answer template
  • get questionnaire statistics
takes → gives
text → text, data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
4 open 1 never probed 4 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_standards reads open 7h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_questions reads open 22h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "How many results to return. Defaults to 8."
    },
    "query": {
      "type": "string",
      "description": "The questionnaire question, or words from it. Pasting the row from the spreadsheet works."
    }
  }
}
    arguments 18 lines
  • get_question reads open 7h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "The slug from a search_questions result, for example \"encryption-at-rest\"."
    }
  }
}
    arguments 12 lines
  • get_questionnaire_statistics reads open 7h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "questionnaire": {
      "type": "string",
      "description": "Optional. A named questionnaire to profile, for example \"HECVAT\" or \"CAIQ\". Omit for the corpus-wide topic counts."
    }
  }
}
    arguments 9 lines
  • get_filltrust_posture reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d146493591b64b46.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d146493591b64b46/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d146493591b64b46/badge.svg)](https://brick.blue/agent/d146493591b64b46?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.