Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

FileFleet

REMOTE · MCP.FILEFLEET.IO

What upload forms accept (passport, visa and exam photos), file checks, and links that fix files.

Available components

+3 this week 77 Trust /100

Last scanned (17 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Documents and Files

Trust breakdown (7 categories)

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability74
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 791 tokens (~197/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 70% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 73

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://mcp.filefleet.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.filefleet.io CN=YE1,O=Let's Encrypt,C=US 11 Nov 2026 9 Feb 2027 ECDSA 256 ECDSA-SHA384 559df18f2d809213b7045113a009ba03b9b
SANs: mcp.filefleet.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.filefleet.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
filefleet.io. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.filefleet.io/mcp Verified 200
http (plaintext) http://mcp.filefleet.io/mcp HTTPS enforced 301 https://mcp.filefleet.io:443/mcp
MCP tools · 3 exposed · ~635 tokens

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 →

Tool Tokens
check_file ~147

Check whether a form will accept a file, from the file's facts: its real type (from its contents, not its name), size in bytes, and pixel size or PDF page count. Give either rules or a requirement id from find_upload_requirements (with the upload name for multi-upload forms, such as "ibps/signature"). The file itself is never sent. Returns each rule as passed or failed, and where to fix it.

NameTypeReqDescription
fileobjectyes–
requirementstring–A requirement id, such as "us-visa" or "ibps/signature".
rulesobject–The form's rules, when there is no requirement id.

No output schema declared.

No examples provided.

find_upload_requirements ~151

Look up what size, format or dimensions a photo or upload must be for a specific form: US passport photo size, US visa or DS-160 photo requirements, Green Card (DV) lottery photo rules, Schengen visa photo size, UK online passport photo rules, or IBPS photo, signature, thumb impression and declaration sizes. Returns pixel sizes, file size limits, head and eye position rules, the official source and the date checked, plus a free FileFleet page that makes a photo that passes on the person's own device. Leave the query empty to list everything.

NameTypeReqDescription
querystring–What the person is applying for, such as "US visa photo" or "IBPS signature".

No output schema declared.

No examples provided.

make_requirement_link ~337

Make a FileFleet link that carries a form's upload rules, such as "PDF or JPG, up to 2 MB, named Lastname_ID". Anyone who opens it can add their files and download versions that meet the rules, converted and shrunk in their own browser, so files are never uploaded. Use it when someone has to upload files to a form, or collects files from other people. Shows the rules in the chat, where the person can check their files straight away.

NameTypeReqDescription
file_namestring–How files should be named, such as "Lastname_ID".
forstring–Who is asking for the files, such as "ABC Lettings".
heightinteger–Exact height in pixels (with width).
max_filesinteger–How many files the form takes.
max_heightinteger––
max_kbnumber–Largest allowed size per file, in KB (2 MB = 2000).
max_pagesinteger–Most pages allowed in a PDF.
max_widthinteger––
min_heightinteger––
min_kbnumber–Smallest allowed size per file, in KB.
min_widthinteger––
notestring–A short note for the person, such as "Both sides of your ID, please."
squareboolean––
typesarray–File types the form accepts.
whatstring–What the files are for, such as "Rental application".
widthinteger–Exact width in pixels (with height).

No output schema declared.

No examples provided.

Install

How do I install the FileFleet MCP server?

FileFleet is a hosted endpoint at https://mcp.filefleet.io/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 · mcp.filefleet.io

# add to Claude Code
claude mcp add --transport http io-filefleet-filefleet 'https://mcp.filefleet.io/mcp'
Common questions

What is the FileFleet MCP server?

FileFleet is an MCP server listed in the public MCP registry as io.filefleet/filefleet. What upload forms accept (passport, visa and exam photos), file checks, and links that fix files. This page covers its hosted endpoint (https://mcp.filefleet.io/mcp).

Is the FileFleet MCP server safe to use?

FileFleet scores 77 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 FileFleet MCP server expose?

FileFleet exposes 3 tools: find_upload_requirements, check_file, make_requirement_link. Their descriptions and schemas cost roughly 635 tokens of context every time the server is loaded.

Does the FileFleet MCP server require authentication?

No. We connected to FileFleet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the FileFleet MCP server still maintained?

FileFleet is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the FileFleet MCP server?

VerifyMCP ran 14 checks on FileFleet, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.