opencodeweb
Official# MCP — OpenCodeWEB Model Context Protocol Server
> **Universal AI-tool bridge** for the sovereign ecosystem — `GDBx` (data mesh) + `DSGx` (support) + `GDMx` (payments). Any MCP client (Claude Desktop, Cursor, opencode) can call the live mesh. **Free, MIT, zero hosting cost.**
**Repo:** `github.com/OpenCodeWEB/MCP` · **Live mesh:** `https://gdbx.xup.workers.dev`
## 8 Tools
| Tool | Description |
|---|---|
| `gdbx_did_resolve` | Resolve `did:gdbx` identity for an address |
| `gdbx_sync_get` | Read merged CRDT deltas (`?prefix=` filter) |
| `gdbx_name_resolve` | Resolve verified `.gdbx` name (e.g. `absup`) |
| `gdbx_names_list` | List global `.gdbx` registry |
| `gdbx_apikey_verify` | Verify `GDBx****AB` API key |
| `gdmx_providers` | List 7 fiat on-ramps + configured status |
| `gdmx_create_checkout` | Card→USDC checkout (fastest provider wins) |
| `dsgx_profile` | Developer support profile (`ABsUP`) |
## Usage
```bash
npm i
npm test # 8 tools + live mesh tests
npm start # stdio (Claude Desktop)
npm run http # :8787 — GET /tools, POST /call
```
**Claude Desktop** (`claude_desktop_config.json`):
```json
{ "mcpServers": { "opencodeweb": { "command": "npx", "args": ["-y", "@opencodeweb/mcp"] } } }
```
**HTTP:**
```bash
curl localhost:8787/tools
curl -X POST localhost:8787/call -H 'content-type: application/json' \
-d '{"name":"gdbx_name_resolve","arguments":{"name":"absup"}}'
```
## Principles
- **Non-custodial** — reads are open, writes stay signed client-side
- **0% fee** — only gas, no gateway cut
- **MIT** — fork, self-host, no vendor lock
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.