Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Private, expiring artifact hosting for AI agents. Upload via API or MCP; links die on their own.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http veilfile https://veilfile.com/mcp/ --header 'Authorization: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"veilfile": {
"url": "https://veilfile.com/mcp/",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"veilfile": {
"type": "http",
"url": "https://veilfile.com/mcp/",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account veilfile, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 11 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, TF Rooms
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Live room availability, rates and stay quotes for 12 New Leaf motels in Twin Falls, Idaho.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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).
POST /api/v1/artifacts (multipart, Authorization: Bearer vlf_…) → {id, url, expires_at, size_bytes, secret_flags[]}. GET /a/ serves the file (the 256-bit token *is* the auth). List (bare JSON array) and revoke endpoints included.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.veilfile on PyPI (cli/) and npm (npm/): login (device flow), logout, status, push, pull./app/, Django views on the same shell as the rest of the site: Overview (usage vs plan caps), Files (secret-flag notes/ (public). Agent docs: /llms.txt, docs/API.md, /docs/.See SPEC.md for the product spec.
| Plan | Price | Uploads/mo | Max TTL | Storage | API keys |
|---|---|---|---|---|---|
| Free | $0 | 100 | 7 days | 1 GB | 1 |
| Team | $4/mo | 2,000 | 90 days | 25 GB | 5 |
| Team Plus | $6/mo | 4,000 | 90 days | 40 GB | 10 |
| Scale | $12/mo | 10,000 | 365 days | 100 GB | unlimited |
| Team (yearly) | $40/yr | 2,000 | 90 days | 25 GB | 5 |
| Team Plus (yearly) | $60/yr | 4,000 | 90 days | 40 GB | 10 |
| Scale (yearly) | $120/yr | 10,000 | 365 days | 100 GB | unlimited |
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.
# Backend
python3 -m venv venv && ./venv/bin/pip install -r backend/requirements.txt export 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:
curl -H "Authorization: Bearer vlf_..." \
-F "file=@screenshot.png" \ http://localhost:8000/api/v1/artifacts/
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.
| Variable | Required | Default | Notes |
|---|---|---|---|
DJANGO_SECRET_KEY | prod | — | Required when DJANGO_DEBUG is false |
DJANGO_DEBUG | no | False | Set True for local dev and for tests |
DJANGO_ALLOWED_HOSTS | prod | — | Comma-separated, e.g. veilfile.com |
DJANGO_CSRF_TRUSTED_ORIGINS | no | derived from DJANGO_ALLOWED_HOSTS | Comma-separated origins |
DATABASE_URL | prod | sqlite (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_SQLITE | no | — | True lets production mode run on SQLite on purpose (local docker run, image build) |
DJANGO_CONN_MAX_AGE | no | 60 | Persistent DB connection lifetime (seconds) |
DROP_BASE_URL | prod | http://localhost:8000 | Public URL; artifact links are built from it |
DROP_STORAGE | no | local | local (dev) or s3 (prod) |
DROP_LOCAL_DIR | no | backend/media/artifacts | Local storage root |
AWS_S3_ENDPOINT_URL | prod (s3) | — | R2 endpoint, e.g. https:// .r2.cloudflarestorage.com |
AWS_S3_BUCKET | prod (s3) | — | R2 bucket name |
AWS_ACCESS_KEY_ID | prod (s3) | — | R2 API token (access key) |
AWS_SECRET_ACCESS_KEY | prod (s3) | — | R2 API token (secret) |
STRIPE_SECRET_KEY | billing | — | Live secret key (sk_live_…) in production |
STRIPE_WEBHOOK_SECRET | billing | — | Signing secret (whsec_…) from the same Stripe account and mode as the secret key |
STRIPE_PRICE_TEAM | billing | — | Price ID for the $4/mo Team plan (tax-inclusive) |
STRIPE_PRICE_TEAMPLUS | billing | — | Price ID for the $6/mo Team Plus plan (tax-inclusive). The name has no underscore between TEAM and PLUS |
STRIPE_PRICE_SCALE | billing | — | Price ID for the $12/mo Scale plan (tax-inclusive) |
STRIPE_PRICE_TEAM_ANNUAL | billing | — | Price ID for yearly Team billing, $40/yr (tax-inclusive) |
STRIPE_PRICE_TEAMPLUS_ANNUAL | billing | — | 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_ANNUAL | billing | — | Price ID for yearly Scale billing, $120/yr (tax-inclusive) |
EMAIL_BACKEND | prod | console | Set 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_PASSWORD | prod | — | SMTP settings (the live service uses Gmail SMTP) |
DEFAULT_FROM_EMAIL | prod | — | From address, e.g. support@veilfile.com |
EMAIL_TIMEOUT | no | 10 | SMTP timeout (seconds) |
VEILFILE_SAFETY_MODE | no | off | off, log or enforce: SHA-256 blocklist screening of uploads. Unset is reported as veilfile.W002 |
VEILFILE_CLIENT_IP_HEADER | no | CF-Connecting-IP | Header 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_HOPS | no | 2 | Trusted 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_SECONDS | no | 31536000 | HSTS max-age on HTTPS responses |
DJANGO_SECURE_HSTS_INCLUDE_SUBDOMAINS, DJANGO_SECURE_HSTS_PRELOAD | no | False | Turn on only after every subdomain serves HTTPS |
PORT | no | 8000 | Set by the host (Render); the entrypoint falls back to 8000 |
WEB_CONCURRENCY | no | 1 | gunicorn workers (gthread) |
GUNICORN_THREADS | no | 4 | Threads per worker. Each in-flight upload is held in memory; lower this on small instances |
GUNICORN_TIMEOUT, GUNICORN_GRACEFUL_TIMEOUT | no | 120, 30 | gunicorn timeouts (seconds) |
SKIP_MIGRATE | no | unset | 1 skips migrate at boot (use with a Render pre-deploy command) |
VEILFILE_FUNNEL_RETENTION_DAYS | no | 365 | How long prune_funnel_events keeps funnel rows |
VEILFILE_ALERT_DIR | no | unset | Directory where CRITICAL safety alerts are also written as files, for an external alert bus; they always go to the log |
DJANGO_TEST_ALLOW_REMOTE_DB | no | — | 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 need DJANGO_DEBUG=True (the test runner refuses False) and a local database; it also forces local storage and strips STRIPE_*/AWS_*.
# 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
cd npm && node --test cd 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").
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.GET /healthz returns 200 {"status":"ok"} after a SELECT 1, or 503. Set it as the Render Health Check Path.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.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.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.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.manage.py check --deploy reports veilfile.W001-W006 misconfigurations (also logged at ERROR by every worker at boot).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.docs/REGISTRIES.md.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,
Only the beginning is shown; read the rest in the repo