QAmcp

Copied. Paste it into Claude Code, Cursor or Codex:Fetch and follow the instructions at https://qamcp.dev/setup.md to test my MCP server.

Your AI finds your server in your project, tests it with QAmcp, explains what's wrong in plain words, fixes it with your OK, and tests again. Read the instructions

NewYour score can change any day. QAmcp Monitor keeps testing your server and emails you when it breaks. Free for 1 server.See what Monitor does →

Directory / DenkOps

DenkOps

Q: Is DenkOps MCP server safe?

QAmcp's test on 9 Nov 2026: None of the hidden-instruction wordings we know were found in its 62 tool descriptions. Its error messages showed no secrets or internal details. 27 of its 60 tools are labeled read-only; the others may change or send things. Overall it scored 92/100 on 9 Nov 2026. A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

by denkops.com · https://denkops.com/mcp

Deploy APIs, MCP servers and scheduled jobs on managed EU hosting. Sign in with Google or GitHub.

62 tools✓ no account neededPricing: on their site

See pricing →Visit website

92 /100

PASS · WITH NOTES

Partial: 10 of 11 checks · 9 Nov 2026

Test it now for current results

At a glance

Runs where: On their server. What you send to it goes to them.
What you need: Nothing: it answered without a login
Tools: 62 tools
Its own safety labels: 28 read-only, 22 labeled as deleting or destroying, 12 labeled as changing things
Memory it takes: About 9,400 tokens of your AI's memory, just for its tool descriptions
Largest answer: About 17.1 KB in our test
Tools that look alike: 1 pair of tools with nearly the same description, so the AI may pick the wrong one
Speed: Average answer in our test: 158 ms

Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From our latest test, 9 Nov 2026.

Is DenkOps MCP server safe?

None of the hidden-instruction wordings we know were found in its 62 tool descriptions.
Its error messages showed no secrets or internal details.
27 of its 60 tools are labeled read-only; the others may change or send things.
Overall it scored 92/100 on 9 Nov 2026.

A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

What this test does not check

Its source code and packages.
What a tool quietly does behind the scenes, such as writing a file or calling another service.
Instructions hidden inside live tool answers. We only look for those in tool descriptions.
Hidden instructions worded in a way our list doesn't know yet.
Tools that could change something. Those are read, never run.

What QAmcp can and can't see · How to tell if an MCP server is safe · Hidden instructions · Prompt injection

Known security advisories

Not looked up yet. QAmcp tests how a server behaves. It does not scan source code.

What it can do

60 tools, in the server's own words.

list_membersread-only

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

invite_member

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

set_member_role

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

remove_member

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

cancel_invite

Cancel a pending workspace invite.

get_project_accessread-only

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

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.

get_member_accessread-only

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

get_connector_accessread-only

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

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 = a…

list_connector_accountsread-only

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

add_connector_account

Create an email/password account for a connector project.

reset_connector_account_password

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

remove_connector_account

Delete an email/password account from a connector project.

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 …

regenerate_connection

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

get_connection_activityread-only

Show recent actions performed with one connection token.

list_alert_rulesread-only

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

create_alert_rule

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.

update_alert_rule

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

delete_alert_rule

Delete an alert rule.

list_alert_eventsread-only

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

get_audit_logread-only

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

list_deploymentsread-only

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

and 36 more

Test results

Safe mode: only tools labeled read-only were run. How the test works

!
Every tool is described
24 warnings
- !invite_member: Inputs with no description: email, github_login, role
- !set_member_role: Inputs with no description: role
- !set_project_access: Inputs with no description: role
- !set_connector_access: Inputs with no description: public, allowed_emails, sign_in_providers, password_accounts
- !add_connector_account: Inputs with no description: email
- !reset_connector_account_password: Inputs with no description: email
- !remove_connector_account: Inputs with no description: email
- !update_connection_scopes: Inputs with no description: env, public_paths, egress, can_create, projects
- and 16 more
note
!
Follows MCP best practices (not scored yet)
1 tip (not scored)
- !The tool list is about 44 KB (roughly 11k tokens). AI apps send it with every message, so it takes that much of the AI's memory before any work starts.
note
✓
ConnectsConnected in 456 ms
pass
✓
Ready for the newest MCP versionUses the latest MCP version (2026-07-28)
pass
✓
Lists its toolsFound 62 tools
pass
✓
Tools are labeled safe or dangerousEvery tool has a safety label
pass
✓
No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.
pass
✓
Tools work with good inputs
All good
- –list_members: Needs you to sign in, so it was not tested (not counted against the server)
- –get_project_access: Needs you to sign in, so it was not tested (not counted against the server)
- –get_member_access: Needs you to sign in, so it was not tested (not counted against the server)
- –get_connector_access: Needs you to sign in, so it was not tested (not counted against the server)
- –list_connector_accounts: Needs you to sign in, so it was not tested (not counted against the server)
- –get_connection_activity: Needs you to sign in, so it was not tested (not counted against the server)
- –list_alert_rules: Needs you to sign in, so it was not tested (not counted against the server)
- –list_alert_events: Needs you to sign in, so it was not tested (not counted against the server)
- and 32 more
pass
✓
Fast enough
All good
- ✓Connecting took 456 ms
- ✓Listing tools took 414 ms
- ✓Average tool answer: 158 ms
- ✓get_denkops_guide: Slowest tool: get_denkops_guide (158 ms)
pass
✓
No secrets leakedChecked 92 error messages: no secrets or internal details
pass
–
Bad inputs give a clean error
Not tested
- –get_project_access: Needs you to sign in, so bad inputs were not tested
- –get_member_access: Needs you to sign in, so bad inputs were not tested
- –get_connector_access: Needs you to sign in, so bad inputs were not tested
- –list_connector_accounts: Needs you to sign in, so bad inputs were not tested
- –get_connection_activity: Needs you to sign in, so bad inputs were not tested
- –list_alert_events: Needs you to sign in, so bad inputs were not tested
- –list_deployments: Needs you to sign in, so bad inputs were not tested
- –get_status: Needs you to sign in, so bad inputs were not tested
- and 10 more
not tested
–
Tools work togetherNo tool's answer could be fed into another tool, so there were no chains to test (not counted either way)
not tested

Test it yourself

Free and open source. Same checks, same score.

npx qamcp-cli https://denkops.com/mcp

Show this score on GitHub

Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.

[![QAmcp score](https://qamcp.dev/s/com-denkops-denkops.svg)](https://qamcp.dev/s/com-denkops-denkops.html)

Score over time

9 Nov 202692

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use DenkOps, signed in with GitHub, one per person. Reviews never change the score.

Is this your server? Get an alert the moment it breaks.

QAmcp Monitor tests it every hour and emails you when it goes down, the score drops, a tool changes or a secret leaks. Free for 1 server, no card.

Have a concern, or want it removed? Ask us and we'll take it off the list. How the directory works