Veilfile

io.github.veilfile由 GitHub 账号 veilfile 发布v1.0.0更新于 Oct 30, 2026

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

已验证Streamable HTTP可网页运行云端与基础设施文件与存储

概览

AI 生成的概览

Veilfile 是一个托管的 MCP 服务器，用于私密、会过期的产物托管：助手可上传截图、日志或 HAR 文件，并获得一个无法猜测、到期自动失效的链接。

可以做什么
  • 上传产物并取回无法猜测、带有效期的链接
  • 为不直接发送的文件创建预签名上传地址
  • 列出工作区中已有的产物
  • 撤销产物，使其链接立即失效
  • 上传内容会被扫描敏感信息形态并标记，调用方要求时可直接拒绝
适用场景
适合 CI 或云端会话中的编码代理产出截图、日志包或 HAR 文件需要私密链接供审阅，而不想放进公开仓库的场景。也适合把短期文件交给人工查看，又不想让它们长期留在网上。
运行要求
通过 streamable HTTP 连接 veilfile.com 的远程端点，无需本地安装。需要完成邮箱验证的账号，并在控制台创建 API 密钥，以 Authorization 请求头携带，或使用 OAuth 令牌。有免费方案，更大额度需付费。
安装前请注意
API 密钥只显示一次，可对工作区执行上传、列出和撤销操作，需妥善保存。只有调用方明确要求拒绝时，含敏感信息形态的上传才会被拦截，否则仅被标记但仍会存储。持有链接的任何人都能读取文件，因为令牌本身就是凭证。付费方案通过 Stripe 计费。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Veilfile，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.veilfile%2Fveilfile/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

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

README

Veilfile — private, ephemeral artifact hosting for AI agents

When a coding agent in CI or a cloud session produces a screenshot, log bundle, or HAR file for review, it needs a private URL to put it at — not a public repo. Veilfile is the sanctioned place: upload via API key (or MCP), get back an unguessable, expiring URL. Uploads are scanned for secret shapes and flagged (blocked only when the caller passes on_secret=reject; file contents are never logged).

  • API: POST /api/v1/artifacts (multipart, Authorization: Bearer vlf_…) → {id, url, expires_at, size_bytes, secret_flags[]}. GET /a/<token> serves the file (the 256-bit token is the auth). List (bare JSON array) and revoke endpoints included.
  • MCP: hosted server at POST /mcp (JSON-RPC over HTTP; tools upload_artifact, create_upload_url, list_artifacts, revoke_artifact), authenticated with a vlf_ key or an OAuth token.
  • CLIs: veilfile on PyPI (cli/) and npm (npm/): login (device flow), logout, status, push, pull.
  • Dashboard: signed-in pages at /app/, Django views on the same shell as the rest of the site: Overview (usage vs plan caps), Files (secret-flag notes
    • revoke), Keys (a new key is shown once), Connected apps and Billing (plan switching and the Stripe billing portal).
  • Landing page: / (public). Agent docs: /llms.txt, docs/API.md, /docs/.
  • Agents working on this repo: read AGENTS.md.

See SPEC.md for the product spec.

Plans

PlanPriceUploads/moMax TTLStorageAPI keys
Free$01007 days1 GB1
Team$4/mo2,00090 days25 GB5
Team Plus$6/mo4,00090 days40 GB10
Scale$12/mo10,000365 days100 GBunlimited
Team (yearly)$40/yr2,00090 days25 GB5
Team Plus (yearly)$60/yr4,00090 days40 GB10
Scale (yearly)$120/yr10,000365 days100 GBunlimited

Yearly billing costs ten months' price, so two months are free. A yearly plan has the same limits as the monthly one.

The source of truth is backend/drop_core/plans.py (PLANS, and ANNUAL_PRICE_USD for the yearly prices; Stripe prices live in Stripe and the STRIPE_PRICE_* variables). backend/drop_core/tests_fix_docs.py fails when a doc or template states a different price or cap.

Quickstart (local dev)

bash
# Backendpython3 -m venv venv && ./venv/bin/pip install -r backend/requirements.txtexport DJANGO_DEBUG=True DJANGO_SECRET_KEY=dev-only-key./venv/bin/python backend/manage.py migrate./venv/bin/python backend/manage.py createsuperuser   # dashboard login./venv/bin/python backend/manage.py runserver          # :8000

Sign up at http://localhost:8000/accounts/signup/ (or log in), open /app/, create an API key, then:

bash
curl -H "Authorization: Bearer vlf_..." \     -F "[email protected]" \     http://localhost:8000/api/v1/artifacts/

Environment variables

No secrets are committed to this repo. Copy the names below into a local .env (gitignored) or your host's env config. Billing is live in production (sk_live_..., live price IDs, Stripe Managed Payments); use a Stripe sandbox/test key only on a local or staging copy.

VariableRequiredDefaultNotes
DJANGO_SECRET_KEYprod—Required when DJANGO_DEBUG is false
DJANGO_DEBUGnoFalseSet True for local dev and for tests
DJANGO_ALLOWED_HOSTSprod—Comma-separated, e.g. veilfile.com
DJANGO_CSRF_TRUSTED_ORIGINSnoderived from DJANGO_ALLOWED_HOSTSComma-separated origins
DATABASE_URLprodsqlite (dev only)Postgres URL. Production refuses to start without it, or with a sqlite:// URL, unless DJANGO_ALLOW_SQLITE=True. User, password and name are percent-decoded; ?sslmode=... is passed to the driver
DJANGO_ALLOW_SQLITEno—True lets production mode run on SQLite on purpose (local docker run, image build)
DJANGO_CONN_MAX_AGEno60Persistent DB connection lifetime (seconds)
DROP_BASE_URLprodhttp://localhost:8000Public URL; artifact links are built from it
DROP_STORAGEnolocallocal (dev) or s3 (prod)
DROP_LOCAL_DIRnobackend/media/artifactsLocal storage root
AWS_S3_ENDPOINT_URLprod (s3)—R2 endpoint, e.g. https://<acct>.r2.cloudflarestorage.com
AWS_S3_BUCKETprod (s3)—R2 bucket name
AWS_ACCESS_KEY_IDprod (s3)—R2 API token (access key)
AWS_SECRET_ACCESS_KEYprod (s3)—R2 API token (secret)
STRIPE_SECRET_KEYbilling—Live secret key (sk_live_…) in production
STRIPE_WEBHOOK_SECRETbilling—Signing secret (whsec_…) from the same Stripe account and mode as the secret key
STRIPE_PRICE_TEAMbilling—Price ID for the $4/mo Team plan (tax-inclusive)
STRIPE_PRICE_TEAMPLUSbilling—Price ID for the $6/mo Team Plus plan (tax-inclusive). The name has no underscore between TEAM and PLUS
STRIPE_PRICE_SCALEbilling—Price ID for the $12/mo Scale plan (tax-inclusive)
STRIPE_PRICE_TEAM_ANNUALbilling—Price ID for yearly Team billing, $40/yr (tax-inclusive)
STRIPE_PRICE_TEAMPLUS_ANNUALbilling—Price ID for yearly Team Plus billing, $60/yr (tax-inclusive). No underscore between TEAM and PLUS, as in STRIPE_PRICE_TEAMPLUS
STRIPE_PRICE_SCALE_ANNUALbilling—Price ID for yearly Scale billing, $120/yr (tax-inclusive)
EMAIL_BACKENDprodconsoleSet django.core.mail.backends.smtp.EmailBackend; without SMTP no new user can verify their email, mint keys or approve CLI logins (veilfile.W001)
EMAIL_HOST, EMAIL_PORT, EMAIL_USE_TLS, EMAIL_HOST_USER, EMAIL_HOST_PASSWORDprod—SMTP settings (the live service uses Gmail SMTP)
DEFAULT_FROM_EMAILprod—From address, e.g. [email protected]
EMAIL_TIMEOUTno10SMTP timeout (seconds)
VEILFILE_SAFETY_MODEnooffoff, log or enforce: SHA-256 blocklist screening of uploads. Unset is reported as veilfile.W002
VEILFILE_CLIENT_IP_HEADERnoCF-Connecting-IPHeader carrying the visitor IP, set (and overwritten) by Cloudflare. Used for rate limits when it holds a valid IP and the request came from a Cloudflare edge address; otherwise the X-Forwarded-For hop logic below applies. Empty disables it
VEILFILE_TRUSTED_PROXY_HOPSno2Trusted public proxy hops in front of the app. The client IP used for rate limits is the X-Forwarded-For entry that many positions from the right, after trailing private-network hops are skipped, when the last of them is a Cloudflare edge address. A request without one did not come through Cloudflare, and the last entry (the one the platform's proxy appended) is used. Confirm against real traffic before changing
DJANGO_SECURE_HSTS_SECONDSno31536000HSTS max-age on HTTPS responses
DJANGO_SECURE_HSTS_INCLUDE_SUBDOMAINS, DJANGO_SECURE_HSTS_PRELOADnoFalseTurn on only after every subdomain serves HTTPS
PORTno8000Set by the host (Render); the entrypoint falls back to 8000
WEB_CONCURRENCYno1gunicorn workers (gthread)
GUNICORN_THREADSno4Threads per worker. Each in-flight upload is held in memory; lower this on small instances
GUNICORN_TIMEOUT, GUNICORN_GRACEFUL_TIMEOUTno120, 30gunicorn timeouts (seconds)
SKIP_MIGRATEnounset1 skips migrate at boot (use with a Render pre-deploy command)
VEILFILE_FUNNEL_RETENTION_DAYSno365How long prune_funnel_events keeps funnel rows
VEILFILE_ALERT_DIRnounsetDirectory where CRITICAL safety alerts are also written as files, for an external alert bus; they always go to the log
DJANGO_TEST_ALLOW_REMOTE_DBno—Lets manage.py test run against a non-local database server (CI with a service container)

Without Stripe vars, checkout/switch/portal return 503 billing_not_configured and the dashboard shows a friendly note; everything else works.

Tests

Tests need DJANGO_DEBUG=True (the test runner refuses False) and a local database; it also forces local storage and strips STRIPE_*/AWS_*.

bash
# Backend (the count changes; run it rather than trusting a number here)cd backend && DJANGO_DEBUG=True DJANGO_SECRET_KEY=dev-only-key \  ../venv/bin/python manage.py test../venv/bin/python manage.py makemigrations --check --dry-run   # must report no changes
# CLIscd npm && node --testcd cli && ../venv/bin/python -m unittest discover -s tests -t .

CI (.github/workflows/ci.yml) runs all of the above plus manage.py check --deploy, a production-settings collectstatic, and the browser checks in site-tests/ (jobs site, site-cloth, site-ink, site-reading, site-phone, site-forms, site-catalog and site-dashboard; see AGENTS.md, "Site checks") on every pull request to main (the browser checks skip a pull request that changes no page), and the backend and CLI checks on every push to it. It runs on GitHub-hosted runners, one machine for each job, with the jobs side by side (AGENTS.md, "Where CI runs").

Ops

  • Deploy: Render Docker web service (serves veilfile.com), auto-deploys every commit to main after its CI checks pass, with a paid Postgres. render.yaml mirrors it. The container runs as a non-root user. Boot sequence (backend/entrypoint.sh): migrate --noinput (skipped when SKIP_MIGRATE=1), createcachetable, a background daily housekeeping loop, then gunicorn.
  • Health check: GET /healthz returns 200 {"status":"ok"} after a SELECT 1, or 503. Set it as the Render Health Check Path.
  • Daily housekeeping: the entrypoint loop runs sweep_expired, clearsessions, cleartokens, prune_funnel_events, prune_email_ips (clears send-log IPs after 90 days) and purge_expired_cache once a day. No separate cron job is needed. Uploads also trigger a small lazy sweep.
  • TTL sweeper: python backend/manage.py sweep_expired deletes expired artifacts (files + rows). Idempotent. Prints swept=N bytes=N failed=N and exits non-zero when any storage delete failed (those rows are kept for the next run); --limit N / --time-budget SECONDS bound a run.
  • Orphaned files: python backend/manage.py reconcile_storage lists stored objects with no artifact row; --delete removes them. Run it by hand, dry run first: --delete refuses when the database looks wrong (empty artifact table, more than 20% orphans, or R2 storage without PostgreSQL) unless you pass --force after checking the db= / storage= it prints.
  • Billing resync: python backend/manage.py sync_stripe_billing (dry run; --apply to write) rebuilds workspace plans from Stripe. The Stripe setup steps are in the private ops repository.
  • Deploy checks: manage.py check --deploy reports veilfile.W001-W006 misconfigurations (also logged at ERROR by every worker at boot).
  • Local container: docker run needs DATABASE_URL=sqlite:////tmp/db.sqlite3 together with DJANGO_ALLOW_SQLITE=True (production mode otherwise refuses SQLite); /app/backend is read-only to the non-root user.
  • Storage: Render's disk is ephemeral. Production must use DROP_STORAGE=s3 (Cloudflare R2).
  • MCP registries: launch checklist in docs/REGISTRIES.md.

Project layout

backend/  config/          Django settings/URLs (env-driven)  drop_core/       Workspace, APIKey (vlf_), Artifact, plans, storage,                   secret scan, agent API, key mgmt, device login, OAuth                   glue, sweeper  drop_billing/    Stripe checkout/switch/portal/status/webhook (live,                   tax-inclusive, Managed Payments)  drop_mcp/        MCP server (POST /mcp)  blog/, docs/     Markdown-rendered Journal posts (and their feed) and Docs pages  legal/           Terms, privacy policy, abuse reporting (Markdown)  pages/           public-page registry, sitemap, component catalog, content checks  static/          the new shell's CSS, JS, fonts and images  dashboard/       the signed-in dashboard at /app/ (views, URLs, tests)  templates/       shell.html, layouts/, chapters/ and components/, the Journal, Docs and legal pages, the form pages (sign in, device, OAuth), the dashboard and the error pagescli/, npm/         Python and Node `veilfile` command-line clientsplugin/            Claude Code plugin (share-artifact skill)docs/              API.md, llms.txt (served at /llms.txt), REGISTRIES.md,                   superpowers/ (design specs and build plans)site-tests/        browser checks for the new shell (CI jobs `site`, `site-cloth`, `site-ink`, `site-reading`, `site-phone`, `site-forms`, `site-catalog`, `site-dashboard`)tools/             one-off font and image generators, run by handDockerfile         one Python stage, WhiteNoise + gunicorn (the site has no build step)render.yaml        Render deploy blueprint (mirrors the live service)AGENTS.md          Rules and commands for agents working on this repo

License and contributions

The code is published so that anyone can read it and check what Veilfile does. All rights are reserved (LICENSE), except for the command-line clients in cli/ and npm/, which are under the MIT License. This repository does not accept pull requests from outside contributors. Issues are welcome, and a security problem should be reported privately with "Report a vulnerability" on the repository's Security tab.

Launch checklist

  1. Create Cloudflare R2 bucket + API token (S3-compatible).
  2. Create Stripe products/prices (Team $4, Team Plus $6, Scale $12, tax-inclusive) with product tax codes; note the price IDs.
  3. Deploy on Render (see render.yaml); set env vars incl. DROP_BASE_URL, DATABASE_URL and the EMAIL_* SMTP settings; set the Health Check Path to /healthz.
  4. Point the Stripe webhook at https://<host>/api/v1/billing/webhook; set STRIPE_WEBHOOK_SECRET.
  5. Decide VEILFILE_SAFETY_MODE (log or enforce).
  6. List the MCP server per docs/REGISTRIES.md.

Expired artifacts are swept daily by the entrypoint loop; no cron job is needed.

来源：README.md，提交 5a19640

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v1.0.0最新Oct 29, 2026

评分

已满足适用检查项的 75%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。