Home / MCP registry index / de.run-zero/mcp

run.zero

de.run-zero/mcp in the official MCP registry. Endpoint https://api.run-zero.de/mcp. Source: github.com/getitdone-gmbh/run-zero-mcp.

The registry describes it as: Deploy apps, APIs and Postgres from your AI agent. EU PaaS hosted in Germany, OAuth sign-in.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http run-zero https://api.run-zero.de/mcp

{
  "mcpServers": {
    "run-zero": {
      "url": "https://api.run-zero.de/mcp"
    }
  }
}

code --add-mcp '{"name":"run-zero","type":"http","url":"https://api.run-zero.de/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

runzero_get_help runzero_list_apps runzero_get_app runzero_create_app runzero_list_templates runzero_adopt_template runzero_list_services runzero_get_logs runzero_get_metrics runzero_screenshot runzero_rebuild_service runzero_delete_app runzero_deploy runzero_deploy_preview runzero_add_service runzero_delete_service runzero_scale_service runzero_set_secrets runzero_list_secrets runzero_delete_secret runzero_list_builds runzero_list_versions runzero_preview_version runzero_work_url runzero_list_releases runzero_publish runzero_restore_release runzero_set_publish_mode runzero_activate_version runzero_wait_for_build runzero_get_build_logs runzero_push_files runzero_list_files runzero_read_file runzero_upload_assets runzero_list_users runzero_create_user runzero_delete_user runzero_reset_user_password runzero_set_user_enabled runzero_list_identity_providers runzero_create_identity_provider runzero_generate_image runzero_db_query runzero_describe_addon runzero_get_legal_profile runzero_set_legal_profile

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-04): 4e7195a4c71ade68. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/de-run-zero-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/de-run-zero-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Postgres MCP servers