Skip to main content
Glama
OpenCodeWEB

opencodeweb

Official
by OpenCodeWEB
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to opencodeweb

No user-submitted related servers found.

    Related Servers

    • Yolfi MCP Server

      watson8071
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents and MCP hosts to register a workspace, create stablecoin checkout and payment links, configure webhooks, verify crypto payment status, and add webhook-based access logic to applications.
      -

    • @agentlair/mcp

      piiiico
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to register, send/receive email, store encrypted credentials, emit audit events, and query behavioral trust scores via MCP tools.
      3 npm
      5
      MIT
    • openpeoplerouter by DINQ-labs

      openpeoplerouterofficial

      DINQ-labs
      A
      license
      A
      quality
      C
      maintenance
      Enables people and company discovery, enrichment, identity resolution, and contact finding through unified MCP tools, with optional provider endpoint catalog access using your own API keys.
      12
      Apache 2.0

    • Snowdrop MCP

      Stonewater-Digital
      F
      license
      Not graded
      quality
      F
      maintenance
      Provides 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
      -

    • MIKO MCP Server

      Miko-Protocol
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      6
      4 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources