Home / MCP registry index / com.denkops/denkops

DenkOps

com.denkops/denkops in the official MCP registry. Endpoint https://denkops.com/mcp. Source: github.com/DenkOpsAI/denkops-mcp.

The registry describes it as: Deploy APIs, MCP servers and scheduled jobs on managed EU hosting. Sign in with Google or GitHub.

Connect it

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

claude mcp add --transport http denkops https://denkops.com/mcp

{
  "mcpServers": {
    "denkops": {
      "url": "https://denkops.com/mcp"
    }
  }
}

code --add-mcp '{"name":"denkops","type":"http","url":"https://denkops.com/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 lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

list_members invite_member set_member_role remove_member cancel_invite get_project_access set_project_access get_member_access get_connector_access set_connector_access list_connector_accounts add_connector_account reset_connector_account_password remove_connector_account update_connection_scopes regenerate_connection get_connection_activity list_alert_rules create_alert_rule update_alert_rule delete_alert_rule list_alert_events get_audit_log list_deployments set_cron_enabled list_workspaces create_workspace get_workspace_overview list_projects get_status get_container_logs rollback stop_project start_project delete_project list_env set_env unset_env redeploy get_public_paths set_public_paths get_egress_policy set_egress_policy add_domain list_domains verify_domain remove_domain list_traces get_trace get_metrics list_connections create_connection revoke_connection list_crons run_cron get_denkops_guide get_plan get_billing_link get_connector_branding set_connector_branding and 2 more

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-09): 19849dcde1fe4a10. 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/com-denkops-denkops/badge.svg)](https://lazaretto.dev/mcp-registry/com-denkops-denkops)

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

GitHub MCP servers