Skip to main content
Glama

Qumge: Agent Capabilities & Skills

by com.qumge
OverviewDiscussionsAdmin

verify_domain

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe service's https url, e.g. https://api.example.com/mcp
checkNotrue = look for the line now (after the user deployed it).
qumge_keyNoOptional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYes
put_atNo
dns_txtNo
verifiedYes
verification_lineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / qumge_key
      Added value: +{
+  "description": "Optional: your Qumge API key, for clients that cannot set an Authorization header. Takes precedence over the header. Never echoed back.",
+  "type": "string"
+}
  2. Added

TDQS

Score is being calculated.

All Qumge: Agent Capabilities & Skills toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources