opencodeweb
OfficialRelated Servers
Alternatives to opencodeweb
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to register, send/receive email, store encrypted credentials, emit audit events, and query behavioral trust scores via MCP tools.2 npm4MIT
- FlicenseNot gradedqualityFmaintenanceProvides 667 specialized tools for financial and operational tasks, including fund accounting, compliance, DeFi, and tax management. It enables users to integrate extensive financial intelligence and automated workflows into any MCP-compatible client.1-
- AlicenseAqualityBmaintenanceEnables MCP clients to call MIKO's on-chain analytics tools including fact-checking, persona analysis, narrative tracking, and market insights via a REST API, with authentication tied to $MIKO token holdings.64 npmMIT

NEX MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables any MCP client to access 11 AI inference and data tools, including chat, code, vision, embeddings, crypto prices, weather, geolocation, currency exchange, and WHOIS, with a free tier and paid USDC-on-Base endpoints.Apache 2.0
Signaliz MCPofficial
FlicenseNot gradedqualityDmaintenanceProvides MCP clients with 60+ APIs for B2B data enrichment, lead generation, email verification, company intelligence, and agentic GTM workflows.-- AlicenseNot gradedqualityCmaintenanceEnables access to DePIN RF telemetry, spatial heuristics, and threat intelligence through metered MCP tools with per-record spend caps and on-chain settlement.1MIT
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.