Skip to content

MCP servers › com.denkops › denkops

MCP server · registry snapshot 2026-11-09 · last tested 2026-11-09

denkops MCP server

Registry name com.denkops/denkops

by denkops.com · domain (the registry's namespace rule)repository owner on GitHub: DenkOpsAI (organization)Source ↗Website ↗

Deploy APIs, MCP servers and scheduled jobs on managed EU hosting. Sign in with Google or GitHub. — the publisher's description

3 of 5 record checks metRead-only · tools listed 2026-11-09version 1.0.0streamable HTTP62 tools

Summary

com.denkops/denkops is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain denkops.com. Its linked repository is github.com/DenkOpsAI/denkops-mcp; GitHub reports its owner as DenkOpsAI, an organization. On 2026-11-09 ProtocolProbe connected to it in read-only mode and read its inventory: 62 tools, 0 resources and 0 prompts.

Record checks

3 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • not met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
62
Last tested
2026-11-09

Tool list size

13,401 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (62 tools). Counted with Anthropic's token counter on 2026-11-09, from the tool list we read on 2026-11-09. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-09 (denkops.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 27 tools whose name or declaration suggests they change data (set_member_role, remove_member, cancel_invite, set_project_access, set_connector_access and 22 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-09.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-09
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-11-09 (registry, as of the 2026-11-09 snapshot)
First listed version
2026-11-09 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-09
Package and repository
checked 2026-11-09
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-08, listed on 2026-11-09 with version 1.0.0 (published 2026-11-09).

Source: the official MCP Registry list on 2026-11-08 and on 2026-11-09.

What it is

What does this server offer?

Observed inventory
62tools
0resources
0prompts

None of its 62 tools are described as changing anything. For 62 the reading was uncertain, so no mark is shown.

  • “List the workspace's members with their roles, and pending invites.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • invite_memberon 16 other servers

    “Invite someone to the workspace by email address (or GitHub username) with a role.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    3 inputs
    • emailstring
    • github_loginstring
    • rolestring
  • set_member_role

    “Change a workspace member's role (owner, member or viewer).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 2 required
    • user_idstringrequired“The user id”
    • rolestringrequired
  • remove_memberon 12 other servers

    “Remove a member from the workspace; their access (including chat connections) ends immediately.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • user_idstringrequired“The user id”
  • cancel_inviteon 1 other server

    “Cancel a pending workspace invite.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • invite_idstringrequired“The invite id”
  • get_project_accesson 1 other server

    “Show each member's workspace role and effective role on one project (none = the project is hidden from them).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • project_idstringrequired“The project id”
  • set_project_access

    “Set a member's role on one project: none (hidden), viewer, member or owner — or inherit to fall back to their workspace role.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    3 inputs, 3 required
    • project_idstringrequired“The project id”
    • user_idstringrequired“The user id”
    • rolestringrequired
  • get_member_access

    “List the per-project role overrides of one workspace member.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • user_idstringrequired“The user id”
  • get_connector_access

    “Show who may connect to a connector project (public, an email allowlist, or workspace members) and which sign-in methods are allowed.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • project_idstringrequired“The project id”
  • set_connector_access

    “Change who may connect to a connector project: public on/off, the email allowlist (replaces it), allowed sign-in providers (github, google, microsoft; null = all) and email/password accounts on/off.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    5 inputs, 1 required
    • project_idstringrequired“The project id”
    • publicboolean
    • allowed_emailsarray
    • sign_in_providersarray or null
    • password_accountsboolean
  • list_connector_accountson 4 other servers

    “List the email/password accounts that can sign in to a connector project.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • project_idstringrequired“The project id”
  • add_connector_account

    “Create an email/password account for a connector project.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    2 inputs, 2 required
    • project_idstringrequired“The project id”
    • emailstringrequired
Show 50 more tools
  • reset_connector_account_password

    “Generate a new password for a connector project's email/password account; the old one stops working.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs, 2 required
    • project_idstringrequired“The project id”
    • emailstringrequired
  • remove_connector_account

    “Delete an email/password account from a connector project.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 2 required
    • project_idstringrequired“The project id”
    • emailstringrequired
  • update_connection_scopes

    “Change what a connection token may do: env / public paths / egress access (none, read, write), whether it may create projects, and which projects it may touch (null = all).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    6 inputs, 1 required
    • connection_idstringrequired“The connection id”
    • envstring
    • public_pathsstring
    • egressstring
    • can_createboolean
    • projectsarray or null
  • regenerate_connection

    “Issue a new token for a connection and revoke the old one (e.g.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    1 input, 1 required
    • connection_idstringrequired“The connection id”
  • get_connection_activity

    “Show recent actions performed with one connection token.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • connection_idstringrequired“The connection id”
  • list_alert_ruleson 3 other servers

    “List the workspace's alert rules (crash, killed, rate_limit, deploy_failed) and where they notify.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • create_alert_ruleon 2 other servers

    “Create an alert rule for an event (crash, killed, rate_limit, deploy_failed) on one project or all, optionally posting to an https webhook (e.g.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    3 inputs, 1 required
    • event_typestringrequired
    • project_idstring“The project id”
    • webhook_urlstring
  • update_alert_rule

    “Turn an alert rule on/off or change its webhook (null removes it).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    3 inputs, 1 required
    • rule_idstringrequired“The rule id”
    • enabledboolean
    • webhook_urlstring or null
  • delete_alert_ruleon 2 other servers

    “Delete an alert rule.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • rule_idstringrequired“The rule id”
  • list_alert_eventson 1 other server

    “Show recent alert events (crashes, kills, rate limits, failed deploys).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • limitinteger
  • get_audit_logon 13 other servers

    “Show the workspace's recent audit log: who did what, when.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • list_deploymentson 11 other servers

    “List a project's deployed versions (newest first) with status and when; the active version is marked.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • project_idstringrequired“The project id”
  • set_cron_enabled

    “Pause (enabled=false) or resume (enabled=true) a project's scheduled job.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    3 inputs, 3 required
    • project_idstringrequired“The project id”
    • job_idstringrequired“The job id”
    • enabledbooleanrequired
  • list_workspaceson 49 other servers

    “List the workspaces of the signed-in account with roles, and which one this connection acts in.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • create_workspaceon 17 other servers

    “Create a new workspace owned by the signed-in person.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    1 input, 1 required
    • namestringrequired
  • get_workspace_overview

    “One overview of the workspace: slot usage and every project with status, active version and latest memory/CPU use.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • “List the DenkOps projects in the signed-in workspace with their status and URL.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • “Get a DenkOps project's status and active version by project_id.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • project_idstringrequired“The DenkOps project id”
  • get_container_logson 1 other server

    “Read recent container logs for a DenkOps project, e.g.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 1 required
    • project_idstringrequired“The DenkOps project id”
    • linesinteger
    • sincestring
    • levelstring
  • “Roll a DenkOps project back to a previous healthy version (omit version for the previous one).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs, 1 required
    • project_idstringrequired“The DenkOps project id”
    • versioninteger
  • stop_projecton 5 other servers

    “Stop a DenkOps deployment: its containers stop and it goes offline.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • project_idstringrequired“The DenkOps project id”
  • start_projecton 4 other servers

    “Start a stopped DenkOps deployment again (reactivates its active version).”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • project_idstringrequired“The DenkOps project id”
  • delete_projecton 43 other servers

    “PERMANENTLY delete a DenkOps deployment and ALL its data (containers, images, volume and records).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs, 1 required
    • project_idstringrequired“The DenkOps project id”
    • confirmstring“The project's exact slug, to confirm permanent deletion”
  • “List a DenkOps project's environment variable KEYS (values are write-only and never shown), and whether changes are pending a redeploy.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • project_idstringrequired“The DenkOps project id”
  • “Set or overwrite a DenkOps project's environment variable (for secrets such as API keys).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    3 inputs, 3 required
    • project_idstringrequired“The DenkOps project id”
    • keystringrequired
    • valuestringrequired
  • unset_env

    “Delete a DenkOps project's environment variable.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 2 required
    • project_idstringrequired“The DenkOps project id”
    • keystringrequired
  • “Re-run the current version of a DenkOps project to apply staged env or path changes or restart the app.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    1 input, 1 required
    • project_idstringrequired“The DenkOps project id”
  • get_public_paths

    “List a DenkOps project's public (unauthenticated) paths, plus the routes DenkOps has observed the app serve.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • project_idstringrequired“The DenkOps project id”
  • set_public_paths

    “Replace a DenkOps project's list of public (unauthenticated) paths.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 2 required
    • project_idstringrequired“The DenkOps project id”
    • pathsarrayrequired
  • get_egress_policy

    “Read a project's outbound-network (egress) allow-list policy: enabled, allowed hosts and recently blocked hosts.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • project_idstringrequired“The DenkOps project id”
  • set_egress_policy

    “Set a project's egress allow-list.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    3 inputs, 3 required
    • project_idstringrequired“The DenkOps project id”
    • enabledbooleanrequired
    • allowlistarrayrequired
  • “Attach a custom domain to a DenkOps project.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    2 inputs, 2 required
    • project_idstringrequired“The DenkOps project id”
    • domainstringrequired
  • “List a DenkOps project's custom domains and whether each is verified.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • project_idstringrequired“The DenkOps project id”
  • verify_domainon 20 other servers

    “Check a DenkOps custom domain's DNS TXT record and activate routing when it is present.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • project_idstringrequired“The DenkOps project id”
    • domain_idstringrequired“The domain id”
  • remove_domainon 8 other servers

    “Detach a custom domain from a DenkOps project.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 2 required
    • project_idstringrequired“The DenkOps project id”
    • domain_idstringrequired“The domain id”
  • “List recent request traces for a DenkOps project (name, status, duration, span count).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • project_idstringrequired“The DenkOps project id”
  • “Get the spans of a single DenkOps request trace by project_id and trace_id.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • project_idstringrequired“The DenkOps project id”
    • trace_idstringrequired“The trace id”
  • “Get a DenkOps project's request metrics (latency percentiles, error rate), latest resource sample and rejected-request count over the last 24h.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • project_idstringrequired“The DenkOps project id”
  • list_connectionson 28 other servers

    “List the workspace's DenkOps connection tokens (scoped, revocable agent/CLI credentials): label, agent type, scopes and status.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • create_connectionon 3 other servers

    “Mint a new scoped, revocable DenkOps connection token for a CLI, CI job or agent (e.g.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    5 inputs
    • labelstring
    • agent_typestring“e.g.”
    • env_scopestring“env var access scope (default none)”
    • expires_in_daysnumber or null“null = never expires (default 90)”
    • projectsarray“restrict to these project ids (default: all projects)”
  • revoke_connectionon 3 other servers

    “Immediately revoke a DenkOps connection token by its connection_id.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • connection_idstringrequired“The connection id”
  • “List a project's managed scheduled (cron) jobs with next and last run and status.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • project_idstringrequired“The DenkOps project id”
  • run_cron

    “Trigger a managed scheduled job immediately (recorded as a manual run).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    2 inputs, 2 required
    • project_idstringrequired“The DenkOps project id”
    • job_idstringrequired“The job id”
  • get_denkops_guide

    “Explains how to structure, configure (denkops.json) and deploy a DenkOps project: bun-Hono or python-FastAPI APIs and MCP servers built with defineMcp.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • “Show the workspace's plan: slots used and still free, subscription status and renewal date, and prices.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_billing_linkon 3 other servers

    “Get a one-click Stripe link for this workspace: subscribe (optionally with extra slots), add slots to an existing subscription, or fix a failed payment.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    1 input
    • extra_slotsinteger“Extra slots on top of the plan (default 0)”
  • get_connector_branding

    “Show the brand colours and icon used on a connector project's hosted sign-in and consent pages.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • project_idstringrequired“The DenkOps project id”
  • set_connector_branding

    “Brand a connector project's hosted sign-in and consent pages: accent colour (buttons/links), background colour (hex like #2563eb; null resets to the DenkOps default) and/or an icon (PNG, JPEG or WebP…”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    5 inputs, 1 required
    • project_idstringrequired“The DenkOps project id”
    • accent_colorstring or null
    • background_colorstring or null
    • icon_base64string“Icon image bytes, base64-encoded”
    • icon_mime_typestring
  • “Show which DenkOps account and workspace this connection acts as.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • “Deploy a project to DenkOps by sending its files, and get the live URL back.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • filesarrayrequired
    • project_idstring“Existing project to deploy a new version to”
    • namestring“Project name for a first deploy without denkops.json”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-09.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
60% of 101
Tools with a description
100% of 62
Typical description length
140 characters

The tool set

Counted from the listing

Tools
62
Size of the list
about 10,947 tokens for an agent to load (characters ÷ 4)
Naming
58 of 62 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 62 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-09 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://denkops.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "denkops": {
      "url": "https://denkops.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "denkops": {
      "type": "http",
      "url": "https://denkops.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"denkops","type":"http","url":"https://denkops.com/mcp"}'
Claude Code
claude mcp add --transport http denkops https://denkops.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "denkops": {
      "type": "streamableHttp",
      "url": "https://denkops.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "denkops": {
      "httpUrl": "https://denkops.com/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.denkops]
url = "https://denkops.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "denkops": {
      "url": "https://denkops.com/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://denkops.com/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint denkops.com/mcpSession openedmatchesour test · 2026-11-09
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-09
Repository github.com/DenkOpsAI/denkops-mcpOpens publiclymatchesapi.github.com · 2026-11-09

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
com.denkops
GitHub owner
an organization (DenkOpsAI)
Repository
github.com/DenkOpsAI/denkops-mcp
Stars
0
Repository age
91–180 days
Last push
91–180 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-09; security policy read from GitHub · 2026-11-09.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

3 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • Not metCode pushed to the repository in the 90 days before our checkLast push 91-180 days before our check.What changes this check: This check reads the date of the last push to the repository, as GitHub reports it, against the 90 days before our check. A project with no recent changes is a normal state.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-09 (security policy 2026-11-09). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about com.denkops/denkops

Answered from the data above

Who publishes com.denkops/denkops?

The registry ties the namespace com.denkops to the domain denkops.com; only its owner can publish under it. Its linked repository is github.com/DenkOpsAI/denkops-mcp; GitHub reports its owner as DenkOpsAI, an organization. These are facts from the registry and GitHub, not a rating.

Is com.denkops/denkops safe to install?

We do not rate servers as safe or unsafe. 3 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does com.denkops/denkops need an API key or sign-in?

It opened a session without any credential on 2026-11-09. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.denkops/denkops been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Does com.denkops/denkops publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of com.denkops/denkops?

In github.com/DenkOpsAI/denkops-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-09
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-09, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,513 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 62 tools, 0 resources, 0 prompts.
  4. 5,219 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-09; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
not stated
GitHub detects no source language in this repository (docs-only or empty)
Hosting type
registry · 2026-11-09
MCP capability
tools
our test · 2026-11-09
Transport
streamable HTTP
registry · 2026-11-09
Required credentials
none declared
registry · 2026-11-09 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-09
Lifecycle status
registry · 2026-11-09
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: an organization · repository age: 91–180 days · stars: 0–9
api.github.com · 2026-11-09
Maintenance
api.github.com · 2026-11-09
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-09

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.denkops/denkops: MCP server record.” Data checked 2026-11-09. https://protocolprobe.com/mcp/servers/com.denkops/denkops

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 3 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.denkops/denkops)](https://protocolprobe.com/mcp/servers/com.denkops/denkops)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology