SendFlo bronze
mcp.sendflo.app
“Moves files between people and agents: send a file and get a share link, or ask a person to upload one.
https://mcp.sendflo.app/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Google Trust Services
domain-validated
Valid until 9 Jan 2027 as of our check on 11 Nov 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.Control of the hostname was checked; nothing about who operates it.Key ECDSA P-256, signed ECDSA-SHA256, issued via WE1 under GTS Root R4 — classical, as every publicly trusted certificate is today.
Names on this certificate (2)
sendflo.app,*.sendflo.app. - Connection
- TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 11 Nov 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- First seen
- 28 Oct 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
-
? Unknown
·
Cloudflare, Inc.
(AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
- Last checked
- 4d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of mcp.sendflo.app controls every word below.
Send a file
Upload the attached file(s) — bytes or https URLs — and get a share link back.
- Share this report
- Make a download link for this video
Request a file from a person
Create a secure link a person (no account needed) uploads a file to; the task completes when it's stored and scanned clean, with what arrived (type, size, scan). The file itself goes to the people of the SendFlo workspace, never to the calling agent. Optional message metadata: requested_by, hand_to (emails of teammates), expires_in_minutes.
- Ask the client for their signed contract
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- SendFlo — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 1.0.0
- Auth schemes
- sendflo_key
- Card completeness
- complete all eight fields required by a2a.proto v1.0
View all card details
- Capabilities
- pushNotifications streaming
- Agent card
- https://mcp.sendflo.app/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.