io.github.m-akcan/zektor

10 of 19 tools are described as changing something (creating, editing, deleting, sending or running).

• whoamion 178 other serversreads or searches

  “Reports which Zektor account the current token belongs to, the API it is talking to, and whether the token came from the environment or the config file.”

  Publisher declares: read-only yes · open-world yes

  Takes no inputs.

• list_instanceson 12 other serversreads or searches

  “Every database and cache on the account, with id, name, status, engine and plan.”

  Publisher declares: read-only yes · open-world yes

  Takes no inputs.

• get_instanceon 5 other serversreads or searches

  “Full detail for a single instance, including storage and autoscaling where it applies.”

  Publisher declares: read-only yes · open-world yes

  1 input, 1 required

  • idintegerrequired“Instance id, as returned by list_instances”
• get_actionon 4 other serversreads or searches

  “How the background work started by create_instance, scale_instance or resize_storage is going, by the actionId they return.”

  Publisher declares: read-only yes · open-world yes

  1 input, 1 required

  • action_idintegerrequired“actionId from create_instance, scale_instance or resize_storage”
• list_planson 40 other serversreads or searches

  “The plans an instance can be created on or scaled to, with price, engine, memory, storage and the engine versions each one can run.”

  Publisher declares: read-only yes · open-world yes

  1 input

  • groupstring“Restrict to databases or caches.”
• list_regionson 31 other serversreads or searches

  “Regions an instance can be created in.”

  Publisher declares: read-only yes · open-world yes

  Takes no inputs.

• get_connectionon 6 other serversreads or searches

  “RETURNS A LIVE CREDENTIAL for caches: the connection string includes the password.”

  Publisher declares: read-only yes · open-world yes

  1 input, 1 required

  • idintegerrequired“Instance id, as returned by list_instances”
• create_instanceon 12 other serverscreates or changes datadescribed as changing data

  “Provisions a database or cache.”

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

  5 inputs, 4 required

  • groupstringrequired“database for PostgreSQL, cache for Valkey/Redis”
  • namestringrequired“Instance name”
  • tierstringrequired“Plan name from list_plans, e.g.”
  • regionstringrequired“Region name (e.g.”
  • enginestring“Engine version, e.g.”
• scale_instancecreates or changes datadescribed as changing data

  “Changes the plan an instance runs on, which changes what it costs.”

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

  3 inputs, 3 required

  • idintegerrequired“Instance id, as returned by list_instances”
  • tierstringrequired“Target plan name from list_plans”
  • confirm_namestringrequired“The exact instance name, as a guard against acting on the wrong one.”
• list_brancheson 7 other serversreads or searches

  “The instance's cluster: the default database and every branch forked from it.”

  Publisher declares: read-only yes · open-world yes

  1 input, 1 required

  • idintegerrequired“Instance id, as returned by list_instances”
• create_branchon 4 other serverscreates or changes datadescribed as changing data

  “Creates a copy-on-write clone of a PostgreSQL instance: it has the source's data from the moment of branching, and the two diverge independently afterwards.”

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

  4 inputs, 2 required

  • idintegerrequired“Instance id, as returned by list_instances”
  • namestringrequired“Name for the branch”
  • tierstring“Plan for the branch, from list_plans.”
  • expires_in_daysinteger“Days before the branch is deleted automatically.”
• set_branch_expirycreates or changes datadescribed as changing data

  “Branches delete themselves after a while, so a forgotten one does not keep costing money.”

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

  3 inputs, 3 required

  • idintegerrequired“Instance id, as returned by list_instances”
  • branch_idintegerrequired“The branch to change”
  • expires_in_daysinteger or nullrequired“Days from now, or null to keep the branch indefinitely”

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-10-23.

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.