MCP server

Qumge: Agent Capabilities & Skills Official

com.qumge/skills

Checked 26 Oct 2026, 08:29 UTC · Connected to it and listed its tools

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

At a glance

Type

MCP server

Publisher

qumge.com (verified by the MCP Registry)

Status

Working at last check

Tools

21

Token cost

About 9,735 tokens per request

Sets up in

Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok

Last checked

26 Oct 2026, 08:29 UTC

Connect it to your agent

Add to CursorAdd to VS CodeVS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

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

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

[mcp_servers.skills]
url = "https://qumge.com/mcp"

Gemini CLI

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

Cursor

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

VS Code

{"servers":{"skills":{"type":"http","url":"https://qumge.com/mcp"}}}

Antigravity

agy mcp add skills https://qumge.com/mcp

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"skills","server_url":"https://qumge.com/mcp","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"skills","server_url":"https://qumge.com/mcp"}

Tools

• become_developer ~369 tokens
  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
• call_cap ~712 tokens
  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`:
• cap_status ~164 tokens
  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.)
• delist_cap ~227 tokens
  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
• get_balance ~170 tokens
  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'
• get_cap ~254 tokens
  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
• get_cap_job ~272 tokens
  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
• get_earnings ~180 tokens
  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 a
• get_skill ~219 tokens
  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 t
• list_caps ~155 tokens
  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_categories ~65 tokens
  List the skill categories and how many skills are in each. Useful when the user is browsing rather than looking for something specific.
• list_models ~145 tokens
  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_wanted ~148 tokens
  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
• publish_cap Sends messages · ~4456 tokens
  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
• relist_cap ~188 tokens
  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
• request_payout Moves money · ~234 tokens
  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 t
• search_caps ~437 tokens
  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
• search_skills ~380 tokens
  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 act
• submit_cap ~288 tokens
  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 publishes the Cap immediately and agents can call it — and be charged — from then on. Run te
• test_cap ~360 tokens
  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 withou
• verify_domain ~312 tokens
  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 doma

Browse

• Claude tools
• SEO
• Website monitoring
• Converting to Markdown
• Social media

Related MCP servers

• Taifoon coordination layer
  Start here: a free key in one call, then a demand in words that is hired, graded and settled
• Agent Reality Layer
  Buy timestamped web, company, commerce, social, document and decision data via x402.
• MUJ428 Trust Layer — VERIFY BEFORE ACT
  MUJ428 verifies intent and evidence before consequential AI-agent actions.
• Circuit
  Find and try paid AI agent skills for security, on-chain data, code, markets, research and news.
• CrawlCheck
  Verification layer for the agentic web: a signed answer about any site before an agent acts.
• Agora
  Find governed AI capabilities and verify signed receipts. Read-only, no account.
• Fetcher
  The web capability layer for AI agents: render, extract, DNS, SSL, WHOIS & more via x402.
• PodMule
  Search, draft and manage your podcast workspace from your agent.

Badge for your README

[![AptLynx](https://aptlynx.net/badge/com.qumge/skills.svg)](https://aptlynx.net/servers/com.qumge/skills)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents