Skip to content

Qumge: Agent Capabilities & Skills MCP server

com.qumge/skillsqumge.comstreamable-httpv1.2.0Scanned

Find, call and pay per call: the capability layer for agents, plus skills. One key or OAuth.

23 tools: 2 do something that can't be undone, 8 change things and 13 only read.

Tools: 0 delete, 2 irreversible, 8 write, 13 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 2
  • 4 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Qumge: Agent Capabilities & Skills MCP server can do

The Qumge: Agent Capabilities & Skills MCP server is published by qumge.com, a domain the MCP Registry verified. It has 23 tools. It can do things that cannot be undone, such as sending, paying or publishing (publish_cap and request_payout) and create or change data (8 tools: migrate_cap_contract, call_cap, become_developer, verify_domain and 4 more), but cannot delete data. 13 tools only read.

2 tools read private data (search_skills and get_skill); 1 tool brings in text other people can write (cap_status); 2 tools can send data out of your system (verify_domain and publish_cap). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 4 findings (credentials-mention and long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 1.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

23 tools

Can't be undone 2Claude Code: ask
  • publish_capCreate or update a DRAFT Cap on the developer's behalf (requires the developer's Qumge key).Can send data out4 findings

    Why it is in this group

    • The name "publish_cap" says "publish": a word for a change that another call does not undo.

    What it can reach

    • outboundThe name "publish_cap" says "publish": it sends or publishes something to other people.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...onfig or connection_id to share private credentials across Caps. Read https://qumge.com/en/..."

      What this check looks for
    • Info

      The input schema at properties.connection_config.description mentions "credentials".

      Matched text

      inputSchema.properties.connection_config.description: "...epeating the same developer/name reuses credentials when endpoint and authentication agree."

      What this check looks for
    • Info

      The input schema at properties.upstream_token.description mentions "credentials".

      Matched text

      inputSchema.properties.upstream_token.description: "...key. Reusable connections retain their credentials. Stored encrypted; sent as Authorizatio..."

      What this check looks for
    • Info

      The description is 2,864 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...t check can suspend it). (Older clients may still call this tool as publish_app.)"

      What this check looks for
    Description, as the server wrote it
    Create or update a DRAFT Cap on the developer's behalf (requires the developer's Qumge key). Start with the complete buyer outcome, then inspect existing MCP, API and business functions. Reuse a single entry point only when it delivers the full result; otherwise compose partial steps on the provider server and mix MCP, API and internal functions when useful. The buyer agent must not orchestrate provider internals. If both interfaces exist, choose the least-change reliable path; the presence of MCP is not a reason to ignore API. Prefer manifest v2: pass manifest_url for the project's public qumge.json, and slug to select a Cap when needed. The file supplies the name, connection, operations and suggested prices; do not repeat name or override file fields. If the Cap is already published, publishing applies the file's changes directly — descriptions, operations and price cuts now, price rises after the notice period — and says so when the file matches what is live. Without manifest_url, give name and either connection_config, connection_id, base_url or mcp_url, plus the priced operations. Every billed operation must deliver one complete result for one clear input (e.g. product URL in → finished video out); helper steps such as job status are free, and a result that needs several calls is wrapped into one endpoint — never sell partial steps. Managed execution reserves a fixed price and charges only after valid complete delivery; queued acceptance is not delivery, and failed or expired orders cost nothing. Reuse existing tasks and durable request_id deduplication; providers need no Qumge-specific buyer, order, ledger or usage-reporting tables. Prefer execution.identity: order with self-contained inputs. Use trusted request_id to isolate tasks and private results. For buyer-owned state, explicitly choose identity: buyer and authorize the trusted buyer_key; a shared service account alone does not isolate buyers. Use connection_config or connection_id to share private credentials across Caps. Read https://qumge.com/en/docs/caps/managed.md for the complete contract. Legacy per-response and advanced usage-based fields remain supported for existing integrations; the signing/usage guide applies to those modes, not managed execution. A new signing secret is returned once when applicable. Legacy non-managed integrations may also return a usage key; managed execution does not use it. Nothing is charged while it is a draft. Reuse the developer's already approved prices and publication authorization. Do not ask again; confirm only initial pricing, price changes or unclear scope. A manifest price alone is not approval. There is no human review: after test_cap passes, submit_cap takes the Cap live immediately, and qumge spot-checks it afterwards (a spot check can suspend it). (Older clients may still call this tool as publish_app.)
  • request_payoutAsk for a payout of the developer's payable balance (Cap income only — topped-up money cannot be withdrawn).No findings

    Why it is in this group

    • The name "request_payout" says "request": a word for a change.
    • The name "request_payout" also says "payout": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Ask for a payout of the developer's payable balance (Cap income only — topped-up money cannot be withdrawn). Call it once without `confirmed` to get the estimate (amount, channel fee, withholding tax, what actually lands), show that to the user, and only then call again with confirmed: true. Needs the developer's Qumge key.
Changes things 8Claude Code: ask
  • become_developerOpen a developer account for the user (needs their qumge key).No findings

    Why it is in this group

    • The description's first verb is "open": a word for a change.
    Description, as the server wrote it
    Open a developer account for the user (needs their qumge key). There is no review and no waiting: it takes effect immediately, and publish_cap works right after. Give a display name and an ISO country code; the country decides tax and payout rails later. Payout details and legal name are only needed when the user actually withdraws money.
  • call_capCall a Cap on the user's behalf and return its response.No findings

    Why it is in this group

    • The name "call_cap" says "call": a word for a change.
    Description, as the server wrote it
    Call a Cap on the user's behalf and return its response. Use this when you cannot make the HTTP call yourself: qumge charges the user's qumge balance and forwards the call at the same price as calling it over HTTP through Qumge. Operations and prices come from get_cap. Prefer `operation` + `input`: when the operation declares an input_schema, `input` is validated against it before anything is charged or forwarded. For metered Caps, call quote_cap first and pass its quote_id together with a stable idempotency_key; the order is reserved at the quoted amount. Asynchronous calls return a platform job_id and get_cap_job reads cached progress and the final receipt for free. Needs the user's qumge key in the Authorization header. A 5xx from the Cap is free; a 402 means the user's balance or this Cap's monthly limit stopped it. (Older clients may still call this tool as call_app — it still works.)
  • delist_capTake one of the developer's own Caps down.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Take one of the developer's own Caps down. It stops working the moment this returns: calls get a 404 (cap_delisted) and it disappears from the store. Nothing is deleted — price versions, reviews and earnings stay, and the public page stays up marked as delisted so existing links don't break. Confirm with the user before calling: anyone using it loses access immediately. relist_cap puts it back with no new review. Needs the developer's Qumge key.
  • migrate_cap_contractControlled same-price contract replacement for an owned live Cap.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Controlled same-price contract replacement for an owned live Cap. Prepare an explicit old-to-new mapping bound to the current and pending candidate versions/digest, test that candidate, then activate only its verified snapshot. Does not recharge, purchase, or perform real delivery. Changed deliverables require buyer confirmation for new orders; old orders keep their snapshots.
  • relist_capPut one of the developer's delisted Caps back online.No findings

    Why it is in this group

    • The description's first verb is "put": a word for a change.
    Description, as the server wrote it
    Put one of the developer's delisted Caps back online. There is no review: if the connection hasn't changed since it was delisted it goes live immediately. If the service address did change, it is retested first and the call fails with the test result until the new address passes. Needs the developer's Qumge key.
  • submit_capTake one of the developer's Caps live.No findings

    Why it is in this group

    • The name "submit_cap" says "submit": a word for a change.
    Description, as the server wrote it
    Take one of the developer's Caps live. Nothing is reviewed before launch and nobody approves it: when the applicable connection/operation checks and price book pass, with complete billed-operation docs, this lists a new Cap immediately. Existing Cap updates retain their effective version and notice period; submit_cap does not advance a pending contract. Run test_cap first (legacy checklist keys remain signature and end_to_end; the price book is recorded when it saves). Passing native connection checks or isolated fixtures does not verify real delivery. Qumge spot-checks docs and support afterwards and can suspend the Cap. Needs the developer's Qumge key. (Older clients may still call this tool as submit_app_review.)
  • test_capRun the applicable publication checks after publish_cap, before submit_cap.No findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    Description, as the server wrote it
    Run the applicable publication checks after publish_cap, before submit_cap. Managed qumge wrapper operations use authenticated isolated fixture hooks and validate the complete fixture result. Native managed API/MCP operations check HTTP OPTIONS or MCP tools/list for connection/schema evidence without invoking generation. The verification array distinguishes connection, fixture and real_delivery scopes; real delivery is not tested. Legacy integrations may call one free and one billable route, or each published MCP tool, directly with probe inputs; Qumge does not charge for these probes, but the developer may incur provider costs. Signed wrapper/legacy APIs also test /qumge/ping with valid, forged and stale signatures; legacy usage-reporting routes must report probe usage. Missing billed-operation docs block publishing. Needs the developer's Qumge key. (Older clients may still call this tool as test_app.)
  • verify_domainProve the developer owns the domain of their MCP server or API.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Prove the developer owns the domain of their MCP server or API. Going live does not need it: an unverified Cap is live and charges callers, but the developer's earnings from it stay frozen until this passes — verifying releases them. Call with the service's https url: if the domain (or a parent domain) is already verified it says so; otherwise it returns a one-line file to serve at /.well-known/qumge-verify.txt on that host (or a DNS TXT record with the same line). Put the file into the project so it ships with the next deploy, then call again with check: true. Needs the developer's Qumge key.
Only reads 13Show 13 read-only tools
  • cap_statusCheck one of the developer's own capabilities: its status (draft / review / live / suspended) and how far the publishing checklist has got.Reads text others writeNo findings

    Why it is in this group

    • The name "cap_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
    Description, as the server wrote it
    Check one of the developer's own capabilities: its status (draft / review / live / suspended) and how far the publishing checklist has got. Needs the developer's Qumge key. (Older clients may still call this tool as app_status.)
  • get_balanceThe user's Qumge balance, plus what each Cap has spent this month against its monthly limit.No findings

    Why it is in this group

    • The name "get_balance" says "get": a word for reading.
    Description, as the server wrote it
    The user's Qumge balance, plus what each Cap has spent this month against its monthly limit. Call this before a paid call when the user asks whether they can afford it, and after a 402 that says the balance or a limit stopped the call — it returns the top-up link to hand to the user. Needs the user's qumge key.
  • get_capFetch one Cap's operations, prices and how to call it, by the slug returned from search_caps.No findings

    Why it is in this group

    • The name "get_cap" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one Cap's operations, prices and how to call it, by the slug returned from search_caps. Call this before using a Cap: it lists each operation (by name), its input and output schema when the developer provided one, which routes are billable, the per-call maximum, when the call settles, and the error codes the caller may see. If the request carries the user's Qumge key, it also reports that user's monthly limit for this Cap. (Older clients may still call this tool as get_app — it still works.)
  • get_cap_jobRead your managed Cap job's cached progress, complete result and receipt for free.No findings

    Why it is in this group

    • The name "get_cap_job" says "get": a word for reading.
    Description, as the server wrote it
    Read your managed Cap job's cached progress, complete result and receipt for free. Use the platform job_id returned by call_cap. Ordinary reads do not invoke the provider. Set refresh_result: true to explicitly request free renewal of declared result URLs after success; the optional private provider command does not generate new work or change the receipt. Existing orders remain readable after Cap revocation.
  • get_earningsWhat a developer has earned and what is payable: the amount still inside the 30-day holdback, the amount sitting in their wallet (income from Caps — the only part that can be withd…No findings

    Why it is in this group

    • The name "get_earnings" says "get": a word for reading.
    Description, as the server wrote it
    What a developer has earned and what is payable: the amount still inside the 30-day holdback, the amount sitting in their wallet (income from Caps — the only part that can be withdrawn), and what has already been paid out, with the most recent entries. Matured purchase amounts move into the wallet automatically. Needs the developer's Qumge key.
  • get_skillFetch the full SKILL.md content of one skill, by the slug returned from search_skills.Reads private dataNo findings

    Why it is in this group

    • The name "get_skill" says "get": a word for reading.

    What it can reach

    • private-dataThe input names a file (input.include_files), and the tool reads: it reads files.
    Description, as the server wrote it
    Fetch the full SKILL.md content of one skill, by the slug returned from search_skills. Write the returned markdown to .claude/skills/<name>/SKILL.md (or the equivalent for the user's agent). If the reply says the skill ships more files (REFERENCE.md, scripts/…), call again with include_files: true to get them and write each next to SKILL.md.
  • list_capsList the developer's own Caps with their status (draft / live / suspended) and slug.No findings

    Why it is in this group

    • The name "list_caps" says "list": a word for reading.
    Description, as the server wrote it
    List the developer's own Caps with their status (draft / live / suspended) and slug. Use it before publishing to see what already exists, and after to check what went live. Needs the developer's qumge key. (Older clients may still call this tool as list_apps.)
  • list_categoriesList the skill categories and how many skills are in each.No findings

    Why it is in this group

    • The name "list_categories" says "list": a word for reading.
    Description, as the server wrote it
    List the skill categories and how many skills are in each. Useful when the user is browsing rather than looking for something specific.
  • list_modelsList the models this gateway can route to, best first.No findings

    Why it is in this group

    • The name "list_models" says "list": a word for reading.
    Description, as the server wrote it
    List the models this gateway can route to, best first. Every one is reachable with the same Qumge key — no per-vendor signup. Only tool-calling models are listed: an agent cannot use the others.
  • list_wantedWhat agents searched for on Qumge and found nothing: the demand side of the store, in the searchers' own words, with how often each was searched in the last 7 and 30 days.No findings

    Why it is in this group

    • The name "list_wanted" says "list": a word for reading.
    Description, as the server wrote it
    What agents searched for on Qumge and found nothing: the demand side of the store, in the searchers' own words, with how often each was searched in the last 7 and 30 days. Useful before building or publishing a Cap — it tells you what people already want. Only the search text is stored; no user and no IP.
  • quote_capGet a free, binding price quote for a metered Cap before calling it.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get a free, binding price quote for a metered Cap before calling it. This does not start provider work, reserve funds, spend a free call, or charge anything. Pass the complete `input` exactly as you will call it — the quote is bound to that input, the Cap, and your identity for 10 minutes. For capped_actual Caps also pass `limits` (per-line maximum quantities); add `max_charge_micro_usd` to hold spending under your own budget. Then pass the returned quote_id to call_cap with a stable idempotency_key. One quote can create one order; a new key cannot reprice an old order. Needs the user's qumge key.
  • search_capsSearch Qumge's Caps — paid services an agent can call, billed per call from the user's Qumge balance.No findings

    Why it is in this group

    • The name "search_caps" says "search": a word for reading.
    Description, as the server wrote it
    Search Qumge's Caps — paid services an agent can call, billed per call from the user's Qumge balance. A Cap (short for capability) is one finished job: somebody's API or MCP server with a price list; to you it is a set of operations. Use this when the user wants something done rather than a skill to install: 'make a promo video', 'transcribe this call'. Returns the best few with pricing, measured success rate and latency, and the slug to pass to get_cap. Results label declared direct or uncertain matches; partial_results are separate and never a complete-result replacement. Budget applies to the matched operation reservation ceiling. Publication checks are not proof of real delivery. (Older clients may still call this tool as search_apps — it still works.)
  • search_skillsSearch Qumge's curated catalog of agent skills (SKILL.md files) by what the user wants to accomplish.Reads private dataNo findings

    Why it is in this group

    • The name "search_skills" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "file": it reads files.
    Description, as the server wrote it
    Search Qumge's curated catalog of agent skills (SKILL.md files) by what the user wants to accomplish. Use this whenever the user asks for a skill, tool, or Cap — e.g. 'find me a skill for social media automation', 'is there a skill for SEO audits'. Returns the best few, ranked by how useful they actually are (an LLM read each one), with a one-line summary and the exact slug to pass to get_skill.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__skills__cap_status"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:45 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
12
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://qumge.com/.well-known/oauth-protected-resource
Authorization servers
https://qumge.com/
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 12 tools that change things (10 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://qumge.com/mcp: tools/list returned 23 tools to an anonymous client, including migrate_cap_contract (destructive), call_cap (destructive), become_developer (destructive), verify_domain (destructive), publish_cap (destructive) and 7 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 10 to 12
  2. Nov 6, 2026
    • Tools that change things, listed without credentials: 9 to 10
  3. Oct 29, 2026
    • Tools that change things, listed without credentials: 7 to 9

Findings

Matches of fixed checks, with the text they matched.

4 info
  • The description mentions "credentials".

    Matched text

    description: "...onfig or connection_id to share private credentials across Caps. Read https://qumge.com/en/..."

    What this check looks for
  • The input schema at properties.connection_config.description mentions "credentials".

    Matched text

    inputSchema.properties.connection_config.description: "...epeating the same developer/name reuses credentials when endpoint and authentication agree."

    What this check looks for
  • The input schema at properties.upstream_token.description mentions "credentials".

    Matched text

    inputSchema.properties.upstream_token.description: "...key. Reusable connections retain their credentials. Stored encrypted; sent as Authorizatio..."

    What this check looks for
  • The description is 2,864 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...t check can suspend it). (Older clients may still call this tool as publish_app.)"

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 10 -> 12.View diff
    • Tools that change things, listed without credentials: 10 to 12
  2. Tools1 added, 2 changed.+1 added~2 changedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 9 -> 10.View diff
    • Tools that change things, listed without credentials: 9 to 10
  4. Tools3 added, 5 changed.+3 added~5 changedView diff
  5. PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 9.View diff
    • Tools that change things, listed without credentials: 7 to 9

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http skills https://qumge.com/mcp
claude mcp add --transport http skills https://qumge.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__skills__search_skills",
      "mcp__skills__get_skill",
      "mcp__skills__list_categories",
      "mcp__skills__list_models",
      "mcp__skills__search_caps",
      "mcp__skills__get_cap",
      "mcp__skills__get_cap_job",
      "mcp__skills__quote_cap",
      "mcp__skills__get_balance",
      "mcp__skills__list_caps",
      "mcp__skills__cap_status",
      "mcp__skills__get_earnings",
      "mcp__skills__list_wanted"
    ],
    "ask": [
      "mcp__skills__migrate_cap_contract",
      "mcp__skills__call_cap",
      "mcp__skills__become_developer",
      "mcp__skills__verify_domain",
      "mcp__skills__publish_cap",
      "mcp__skills__test_cap",
      "mcp__skills__submit_cap",
      "mcp__skills__delist_cap",
      "mcp__skills__relist_cap",
      "mcp__skills__request_payout"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as skills. Review it before you use it.

Capability tags behind 5 rules
  • mcp__skills__search_skills private-data
  • mcp__skills__get_skill private-data
  • mcp__skills__verify_domain outbound
  • mcp__skills__publish_cap outbound
  • mcp__skills__cap_status untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.qumge/skills/verify?hash=1525833ce0593cfa58a2d09d414dd56ec00a3ae7fc037a7b6d2d4ba4d12ea70d" | jq -e '.changed == false'

Pinned hash 1525833ce059, from Nov 14, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.qumge/skills/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.qumge/skills
[![Anlyon Radar](https://radar.anlyon.com/badge/com.qumge/skills.svg)](https://radar.anlyon.com/servers/com.qumge/skills)

Source: MCP Registry. Synced Oct 21, 2026, 18:01 UTC.

Qumge: Agent Capabilities & Skills MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Qumge: Agent Capabilities & Skills MCP server safe?

No scan can promise that. What its definitions show: 23 tools, 10 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Qumge: Agent Capabilities & Skills MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Qumge: Agent Capabilities & Skills MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: publish_cap and request_payout.

What tools does the Qumge: Agent Capabilities & Skills MCP server have?

23 tools: 2 irreversible, 8 write, 13 read. publish_cap, request_payout, migrate_cap_contract, call_cap, become_developer, verify_domain, test_cap, submit_cap and 15 more.

Does the Qumge: Agent Capabilities & Skills MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Qumge: Agent Capabilities & Skills MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): verify_domain and publish_cap.

Has the Qumge: Agent Capabilities & Skills MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.