Veilfile MCP Server

by yourimaginationwillbefired Your server? Claim it

answering

Veilfile is answering right now. Last checked 12 min ago.

Private, expiring artifact hosting for AI agents. Upload via API or MCP; links die on their own.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 28 days of history · worst day 99%

28 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

306 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

What the code does

We have not read this server's code yet, 24 d ago · rules ccca72095570

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Builds a file path from a variable backend/drop_core/services.py:364

        path = os.path.join(alert_dir, f"{stamp}-safety-critical.md")

Builds a database query by concatenation backend/templates/registration/verify_email.html:61

        <button type="submit">{% if record %}Update and resend link{% else %}Send verification link{% endif %}</button>

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add veilfile --transport http https://veilfile.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://veilfile.com/mcp

~/.codex/config.toml

[mcp_servers.veilfile]
url = "https://veilfile.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "veilfile": {
      "url": "https://veilfile.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "veilfile": {
      "type": "http",
      "url": "https://veilfile.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://veilfile.com/mcp	streamable-http	sign-in	268 ms	12 min ago

Alternatives to Veilfile

same job, measured the same way

Veilfile

by veilfile

Private, expiring artifact hosting for AI agents. Upload via API or MCP; links die on their own.

answering

drop.media

by drop

Host files and AI-generated images on drop.media and get public or expiring private links.

answering

File Relay

by yjq001

Temporary file relay for AI agents: upload a generated file, get an expiring download link.

5 tools answering

Hushdrop

by maxtechera

Open-source artifact sharing for AI agents: private, branded, zero-knowledge links.

67 installs/wk local only

Yourimageshare

by yourimageshare

MCP server exposing the YourImageShare upload API (upload/list/delete) as tools for AI agents.

85 installs/wk 5 tools answering

Yourimageshare

by mediashareorg

MCP server exposing the YourImageShare upload API (upload/list/delete) as tools for AI agents.

local only

Artifacta

by artifacta

Artifact store for AI agents. Hosted OAuth at mcp.artifacta.io/mcp; local stdio via npm/PyPI.

104 installs/wk answering

UniPost

by unipost

Hosted MCP server for AI agents to post to LinkedIn profiles and X and upload to YouTube.

answering

Veilfile — questions

Answers built from our own checks of this server.

Why is there no tool list for Veilfile?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Veilfile working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 306 ms. The bar chart above shows every period we have measured.

Is Veilfile still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Veilfile?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Veilfile?

No API key is involved. Veilfile answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Veilfile?

It answers our handshake in 306 ms on average, which is faster than 47% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.