Skip to content

harvis.dev

by harvis.dev · remote · no sign-in to list tools · v1.0.0 · published by dev.harvis

Deploy static sites from AI agents: deploy_site publishes files and returns a live URL in seconds.

Final · 1
CompareRegistry entry

1 tool: 1 do something that can't be undone.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http harvis https://harvis.dev/api/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

1 tool

Can't be undone 1Claude Code: ask
  • deploy_sitePublish a static website to harvis.dev and get a live public URL back instantly.No findings

    Why it is in this group

    • The name "deploy_site" says "deploy": a word for a change.
    • The description's first verb is "publish": a word for a change that another call does not undo.
    • The description says "cannot be recovered".
    Description, as the server wrote it
    Publish a static website to harvis.dev and get a live public URL back instantly. No account or authentication is needed. Pass every file of the site (HTML, CSS, JS, images...) with its path relative to the site root; include an index.html. Returns the live site 'url' plus a private 'claimUrl' — always show the user BOTH links and tell them to open claimUrl and sign in (free) to attach the site to their account so they can edit or delete it later. Warn them claimUrl is private and cannot be recovered if lost, and that an unclaimed site is permanently deleted 24 hours after its last deploy and cannot be restored. The result also includes a private deployToken: pass it back on a later call to UPDATE that site in place (works before and after claiming) instead of creating a new one. The token identifies the site by itself; passing the subdomain too is optional and guards against updating the wrong site.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http harvis https://harvis.dev/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__harvis__deploy_site"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as harvis. Review it before you use it.