Skip to main content

Qumge: Agent Capabilities & Skills

com.qumge/skillsVersion 1.2.0

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

Status

Responds278 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 14:12 UTC
Latency
278 ms
Remotes responding
1 of 1
Sign-in
No sign-in
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://qumge.com/mcpResponds278 ms
No sign-in

Claude Code

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

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: skills
Remote MCP server URL: https://qumge.com/mcp

Cursor

{
  "mcpServers": {
    "skills": {
      "url": "https://qumge.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"skills","type":"http","url":"https://qumge.com/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

23 tools

Tools of Qumge: Agent Capabilities & Skills
Read-only
Idempotent
Open world
become_developerOpen 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.Not declaredNot declaredNot declaredNot declared
call_capCall 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.)Not declaredNot declaredNot declaredNot declared
cap_statusCheck 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.)Not declaredNot declaredNot declaredNot declared
delist_capTake 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.Not declaredNot declaredNot declaredNot declared
get_balanceThe 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.Not declaredNot declaredNot declaredNot declared
get_capFetch 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.)Not declaredNot declaredNot declaredNot declared
get_cap_jobRead 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.Not declaredNot declaredNot declaredNot declared
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 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.Not declaredNot declaredNot declaredNot declared
get_skillFetch 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.Not declaredNot declaredNot declaredNot declared
list_capsList 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.)Not declaredNot declaredNot declaredNot declared
list_categoriesList the skill categories and how many skills are in each. Useful when the user is browsing rather than looking for something specific.Not declaredNot declaredNot declaredNot declared
list_modelsList 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.Not declaredNot declaredNot declaredNot declared
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. 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.Not declaredNot declaredNot declaredNot declared
migrate_cap_contractControlled 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.Not declaredNot declaredNot declaredNot declared
publish_capCreate 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 credeNot declaredNot declaredNot declaredNot declared
quote_capGet 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.Not declaredNot declaredNot declaredNot declared
relist_capPut 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.Not declaredNot declaredNot declaredNot declared
request_payoutAsk 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.Not declaredNot declaredNot declaredNot declared
search_capsSearch 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.)Not declaredNot declaredNot declaredNot declared
search_skillsSearch 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.Not declaredNot declaredNot declaredNot declared
submit_capTake 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.)Not declaredNot declaredNot declaredNot declared
test_capRun 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.)Not declaredNot declaredNot declaredNot declared
verify_domainProve 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.Not declaredNot declaredNot declaredNot declared

Details

Registry status
Active
Published
Sep 28, 2026
Updated
Sep 28, 2026
Website
Not given
Repository
Not given
Categories (suggested)
Developer toolsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR
Not declared

Are you the operator? Claim this listing