Validate Formhaus form definitions and simulate multi-step paths against the real engine.
Nothing to run from here
Dropthis is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
97/100
trust score
6
downloads a day
local
runs on your machine
236
downloads in 30d
What it does
Official MCP server for dropthis — publish content and get a permanent URL from any MCP-compatible agent.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'DROPTHIS_API_KEY=${DROPTHIS_API_KEY}' --transport stdio dropthis-mcp '--' npx -y @dropthis/mcp
# 2 — ask your agent for something these tools do
# dropthis_get, dropthis_list, dropthis_delete and 26 more
It needs DROPTHIS_API_KEY: this reads it from your environment, so export it first.
Dropthis costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DDAll 1 server
dropthis-dev1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Dropthis as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads DROPTHIS_API_KEY (Your dropthis API key (sk_...). Required) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx DROPTHIS_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'DROPTHIS_API_KEY=${DROPTHIS_API_KEY}' --transport stdio dropthis-mcp '--' npx -y @dropthis/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: DROPTHIS_API_KEY — Your dropthis API key (sk_...). Required.. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
29 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read back an EXISTING drop
No parameter schema on file.
List the account
No parameter schema on file.
Permanently delete a drop and its public URL by
No parameter schema on file.
List a drop
No parameter schema on file.
Approximate view analytics for one drop, by its
No parameter schema on file.
Read back the content an EXISTING drop is serving \u2014 the content read half of the edit loop: in a read-modify-write / read-before-patch cycle, read with this tool, modify, then ship the new version with dropthis_update_content. Requires
No parameter schema on file.
Turn a drop
No parameter schema on file.
Return the authenticated account profile (id, email, display name, plan, status) WITH the active plan
No parameter schema on file.
Change an EXISTING drop
No parameter schema on file.
Check a custom domain
No parameter schema on file.
Repoint a DEDICATED custom domain to a different drop (
No parameter schema on file.
Disconnect a custom domain: the hostname stops serving drops and its routes are removed (the drops themselves are NOT deleted). Destructive; requires
No parameter schema on file.
List the workspaces (teams) this connection can act in, with the currently active one flagged (
No parameter schema on file.
Switch the active team/workspace for this connection. Subsequent publishes land in it; the choice persists server-side across reconnects. Use dropthis_workspaces to list available workspaces first.
No parameter schema on file.
Create a new team workspace (you become its owner). Requires a team-scoped credential (ADR-0068: workspaces:write) \u2014 a publish-only key cannot create teams. Returns the new workspace
No parameter schema on file.
Rename a team workspace or change its slug, by its workspace id. Requires a team-scoped credential (ADR-0068: workspaces:write; owner/admin). Pass
No parameter schema on file.
Permanently delete a team workspace by its id. Destructive and irreversible (its drops and members go with it); requires
No parameter schema on file.
List a team workspace
No parameter schema on file.
Invite an email to a team workspace as admin or member (owner is transferred, never invited). Requires a team-scoped credential (ADR-0068: members:write; owner/admin).
No parameter schema on file.
Change a workspace member
No parameter schema on file.
Remove a member from a team workspace by the workspace id and the member
No parameter schema on file.
Accept a team-workspace invitation and join \u2014 this is the teammate
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Dropthis or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 97 / 100
Release 0.37.0 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score97
Findings0 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digest804f3ad5ce22d374504c0fed7c2b17bef83db9c79e16b3d3fbdb57dc4132ef25
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (29 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
29 of the 29 recovered tools are registered only when tool.requiresWrite && !auth.canWrite is false (dist/bin.cjs:1913) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
No tool is registered unconditionally · 29 only when tool.requiresWrite && !auth.canWrite is false (dist/bin.cjs:1913) — typically when a key or option is configured. All 29 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| dropthis_publish conditional | no tags | |
| dropthis_update_content conditional | no tags | |
| dropthis_update_settings conditional | no tags | |
| dropthis_get conditional | no tags | |
| dropthis_list conditional | no tags | |
| dropthis_delete conditional | state-write | state-write: declares destructiveHint: true |
| dropthis_list_deployments conditional | no tags | |
| dropthis_restore_deployment conditional | no tags | |
| dropthis_analytics conditional | no tags | |
| dropthis_get_content conditional | no tags | |
| dropthis_resolve conditional | no tags | |
| dropthis_account conditional | no tags | |
| dropthis_domains_connect conditional | no tags | |
| dropthis_domains_verify conditional | no tags | |
| dropthis_domains_list conditional | no tags | |
| dropthis_domains_get conditional | no tags | |
| dropthis_domains_update conditional | no tags | |
| dropthis_domains_delete conditional | state-write | state-write: declares destructiveHint: true |
| dropthis_workspaces conditional | no tags | |
| dropthis_use_workspace conditional | no tags | |
| dropthis_create_workspace conditional | no tags | |
| dropthis_rename_workspace conditional | no tags | |
| dropthis_delete_workspace conditional | state-write | state-write: declares destructiveHint: true |
| dropthis_members conditional | no tags | |
| dropthis_invite_member conditional | no tags | |
| dropthis_update_member_role conditional | no tags | |
| dropthis_remove_member conditional | state-write | state-write: declares destructiveHint: true |
| dropthis_invitations conditional | no tags | |
| dropthis_accept_invitation conditional | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest804f3ad5ce22d374
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.37.0. Pin a release below and the command asks for exactly that one.
0.37.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Dropthis can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.