Server providing Argo CD integration for MCP clients.
Nothing to run from here
BIND 9 AIops is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
97/100
trust score
7
downloads a day
local
runs on your machine
30
downloads in 30d
What it does
Governed BIND 9 DNS operations — 23 MCP tools with audit.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user bind-9-aiops-mcp '--' uvx --from bind9-aiops bind9-aiops-mcp
# 2 — ask your agent for something these tools do
# bind_fetch_limits, bind_security_roots, bind_tcp_timeouts and 20 more
BIND 9 AIops costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ATAll 30 servers
AIops-tools30 servers
7 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts BIND 9 AIops as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user bind-9-aiops-mcp '--' uvx --from bind9-aiops bind9-aiops-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
23 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
[READ] Show servers and domains currently limited by recursive fetch caps.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | no | — |
[READ] Show trust anchors through rndc's response channel, without a dump file.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | no | — |
[READ] Show current DNS TCP timeouts without changing them.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | no | — |
[READ] List a zone's ongoing and completed DNSSEC signing state.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| target | string | no | — |
[READ] Show DNSSEC signing status for one zone.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| target | string | no | — |
[READ] Show BIND managed DNSSEC trust-key status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | no | — |
[READ] Show whether stale DNS answers are currently served.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | no | — |
[READ] Show a running dynamic zone's configuration when enabled.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| target | string | no | — |
[READ] Query a specified DNS server for a supported record type.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| server | string | yes | — |
| rrtype | string | no | — |
| target | string | no | — |
[WRITE] Check config and queue a zone reload; completion remains unknown.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| dry_run | boolean | no | — |
| target | string | no | — |
[WRITE] Ask a secondary zone to refresh; transfer completion remains unknown.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| dry_run | boolean | no | — |
| target | string | no | — |
[WRITE] Flush one DNS name from cache; cache state cannot be restored.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| dry_run | boolean | no | — |
| target | string | no | — |
[WRITE] Request a secondary zone retransfer; completion remains unknown.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| dry_run | boolean | no | — |
| target | string | no | — |
[WRITE] Resend NOTIFY for one zone; downstream refresh remains unknown.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| dry_run | boolean | no | — |
| target | string | no | — |
[READ] Get named service status from rndc.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | no | — |
[READ] Validate BIND config and loaded zone files with named-checkconf -z.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | no | — |
[READ] Get BIND's live zonestatus for one zone.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| target | string | no | — |
[READ] Check current DNSSEC validation setting using rndc.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | no | — |
[READ] Query the configured DNS server and expose its actual response code.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| rrtype | string | no | — |
| target | string | no | — |
[READ] Compare primary and secondary SOA serials; unknown stays null.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| secondary | string | yes | — |
| target | string | no | — |
[READ] Correlate named, config, zone, SOA and DNSSEC probes; report failures.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| target | string | no | — |
[READ] List recorded, not-yet-applied undo tokens (most recent first).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max rows to return (default 50, capped at 500). |
| target | string | no | Unused (undo state is host-local); accepted for CLI uniformity. |
[WRITE][risk=medium] Apply a recorded undo by dispatching its inverse tool.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| undo_id | string | yes | The undoId from undo_list (or an `_undo_id` in a write result). |
| dry_run | boolean | no | If True, preview the inverse tool + params without running it. |
| target | string | no | Passed through to the inverse tool when it accepts a target. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install BIND 9 AIops or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 97 / 100
Release 0.2.0 · scanned 6 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score97
Findings2 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digest8f9fcfe6bab5701fccc12d166b26f58c6cd83cc88b778c7f116d8071677efe78
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (23 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| bind_fetch_limits | untrusted-input | untrusted-input: keyword "fetch" |
| bind_security_roots | sensitive-source | sensitive-source: keyword "dump" |
| bind_tcp_timeouts | no tags | |
| bind_signing_status | no tags | |
| bind_dnssec_zone_status | no tags | |
| bind_managed_keys_status | no tags | |
| bind_serve_stale_status | no tags | |
| bind_show_zone | no tags | |
| bind_query_server | no tags | |
| bind_reload_zone | no tags | |
| bind_refresh_zone | no tags | |
| bind_flush_name | no tags | |
| bind_retransfer_zone | no tags | |
| bind_notify_zone | no tags | |
| bind_status | no tags | |
| bind_config_check | no tags | |
| bind_zone_status | no tags | |
| bind_dnssec_validation | no tags | |
| bind_query | no tags | |
| bind_compare_soa | no tags | |
| bind_diagnose_zone | no tags | |
| undo_list | no tags | |
| undo_apply | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest8f9fcfe6bab5701f
Scanned2026-11-06
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.0. Pin a release below and the command asks for exactly that one.
0.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish BIND 9 AIops can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.