opencodeweb
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gdbx_did_resolveB | Resolve a did:gdbx identity document for a .GDBx address. |
| gdbx_sync_getB | Read merged CRDT state (deltas) for an address, optionally filtered by key prefix. |
| gdbx_name_resolveA | Resolve a verified .gdbx short name (e.g. absup → https://absup.org). Server-side PoW+sig verified. |
| gdbx_names_listA | List all claimed .gdbx names (global registry, newest first). |
| gdbx_apikey_verifyA | Verify a GDBx****AB API key. Returns owner prefix + address. |
| gdmx_providersA | List fiat on-ramp providers (MoonPay, Transak, Ramp, Banxa, Wert, Stripe) with configured status. |
| gdmx_create_checkoutA | Create a card→USDC checkout (parallel race, fastest provider wins, direct to merchant wallet). |
| dsgx_profileB | Get a developer support profile (dsgx.pages.dev/) with wallet + verified status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools target distinct resources (identity resolution, sync state, names, API keys, fiat providers, checkout, profiles). gdbx_did_resolve and gdbx_name_resolve both resolve identifiers to identity-related data, which could cause minor confusion, but their descriptions clarify the different input types.
Tool names follow a consistent prefix pattern (gdbx_, gdmx_, dsgx_) with verb_noun structure (did_resolve, sync_get, name_resolve, names_list, apikey_verify, providers, create_checkout, profile). However, the prefixes are inconsistent (gdbx vs gdmx vs dsgx) and some names omit verbs (gdmx_providers, dsgx_profile), breaking the pattern.
8 tools is a reasonable count for a domain spanning identity, names, sync, payments, and support profiles. It is slightly broad but not excessive; each tool appears to serve a distinct function.
The set covers resolution, listing, verification, and checkout creation, but lacks obvious lifecycle operations like name claiming/renewal, API key creation/revocation, or checkout status/confirmation. The domain is broad enough that gaps are noticeable, though core read/verify operations are present.