Veilfile
Server Details
Private, expiring artifact hosting for AI agents. Upload via API or MCP; links die on their own.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- veilfile/veilfile
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
Each tool targets a distinct artifact operation: large-file URL creation, base64 upload, listing, and revocation. create_upload_url and upload_artifact share the upload domain but are clearly separated by file-size/base64 constraints and description.
All names follow a consistent snake_case verb_noun pattern: create_upload_url, list_artifacts, revoke_artifact, upload_artifact. The convention is predictable and readable.
Four tools are well-scoped for a simple artifact/file workspace: upload via base64, upload via URL, list, and revoke. No tool feels redundant or superfluous.
The surface covers upload, listing, and revocation, which are the core lifecycle operations. Minor gaps exist, such as no dedicated get_artifact metadata tool and no explicit expiry update, but list_artifacts provides enough metadata to work around these.
Available Tools
4 toolscreate_upload_urlCreate an upload URLAInspect
Create a one-time upload URL for a file too large to send as base64 through upload_artifact. The result has upload_url, expires_at, max_size_bytes (25 MiB), ttl_days and filename. The URL is valid for 15 minutes and needs no API key. A PUT of the file's raw bytes to it, for example with curl --upload-file, runs the same type check and secret scan as upload_artifact and answers 201 with the same fields that upload_artifact returns. The first successful PUT uses up the URL. A PUT that fails can be retried until the URL expires, except one blocked as content_not_allowed. The URL also stops working if the API key that created it is revoked or the connected app that created it is disconnected.
Inputs: filename (required), ttl_days, on_secret.
list_artifactsList filesARead-onlyIdempotentInspect
List the files in this workspace, newest first. Each entry has id, filename, mime_type, size_bytes, url, expires_at, secret_flags and created_at. Expired files that are not yet deleted are included. The tool changes nothing.
Inputs: limit.
revoke_artifactRevoke a fileADestructiveIdempotentInspect
Revoke a file by its id. Its link stops working at once and the file is deleted. The result is revoked: true, or revoked: false when this workspace has no file with that id. If storage could not be reached, the result adds storage_deleted: false and a later sweep finishes the deletion. Repeating the call is harmless.
Inputs: id (required).
upload_artifactUpload a fileAInspect
Upload a file from base64 content and return its id, its private share link as url, expires_at, size_bytes and secret_flags. The link stops working when the file expires. The decoded file can be up to 25 MiB; for larger files, create_upload_url takes the bytes by PUT instead. The secret scan reads the first 1 MiB of the file, and secret_flags names each kind of secret-shaped content it finds. With on_secret "flag", the default, a flagged file is stored and the result adds a warning and secret_flag_locations. With on_secret "reject", a flagged file is not stored and the call returns the secret_detected error.
Inputs: filename (required), content_base64 (required), ttl_days, mime_type, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Persistent file storage for AI agents. Save files over MCP, get a link a human can open.
Temporary file relay for AI agents: upload a generated file, get an expiring download link.
Artifact store for AI agents — read, write, and search files by path; share by rendered URL.
Artifact store for AI agents. Hosted OAuth at mcp.artifacta.io/mcp; local stdio via npm/PyPI.
Related MCP Servers
- AlicenseAqualityCmaintenanceThe artifact store for AI agents. Every output your agents produce — persisted, retrievable, shareable. Across runs, sessions, and tools. Session/agent metadata, content-hash dedup, and expiring share links; available on npm (@artifacta-mcp/mcp) and PyPI (artifacta-mcp).81MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to publish, retrieve, update, and delete hosted HTML, Markdown, Mermaid, and SVG artifacts and to create, list, or revoke shareable links through authenticated, scope-enforced tools. It exposes artifact hosting over Streamable HTTP so any MCP client can manage content on a self-hosted instance using a Bearer agent API key.2MIT
- FlicenseNot gradedqualityDmaintenanceEnables multi-agent systems to store large tool outputs and share only artifact IDs between agents, with access control, TTL, and audit logging.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to store, version, browse, search, and share artifacts in workspace drives and folders through MCP tools, with keys that gate which tools are offered. Uploads produce shareable public links and rendered previews, and the same bearer key works across the REST API and MCP transport.Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.