harvis.dev MCP server
dev.harvis/harvisharvis.devstreamable-httpv1.0.0Scanned
Deploy static sites from AI agents: deploy_site publishes files and returns a live URL in seconds.
1 tool: 1 do something that can't be undone.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the harvis.dev MCP server can do
The harvis.dev MCP server is published by harvis.dev, a domain the MCP Registry verified. It has 1 tool. It can do things that cannot be undone, such as sending, paying or publishing (deploy_site), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:52 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 destructive). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://harvis.dev/api/mcp: tools/list returned 1 tool to an anonymous client, including deploy_site (destructive)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
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/mcpclaude mcp add --transport http harvis https://harvis.dev/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as harvis. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.harvis/harvis/verify?hash=0ad94274d9f3c4541dcc6c071773340162f8e142c30dd078120a01888dd1a50a" | jq -e '.changed == false'Pinned hash 0ad94274d9f3, from Nov 15, 2026, 02:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.harvis/harvis/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.harvis/harvis)Source: MCP Registry. Synced Oct 21, 2026, 18:11 UTC.
harvis.dev MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the harvis.dev MCP server safe?
- No scan can promise that. What its definitions show: 1 tool, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the harvis.dev MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the harvis.dev MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: deploy_site.
What tools does the harvis.dev MCP server have?
- 1 tool: 1 irreversible. deploy_site.
Does the harvis.dev MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the harvis.dev MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the harvis.dev MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.