Skip to main content
Glama
Sign In
GlyphDNA Ecosystem

GlyphDNA Ecosystem

by TheRealDalaiLama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to GlyphDNA Ecosystem

No user-submitted related servers found.

    Related Servers

    • EVIDIQ Signet MCP

      EVIDIQ Signet MCPofficial

      evidiq
      F
      license
      Not graded
      quality
      B
      maintenance
      Deterministically generates brand and design artefacts (logo SVG, colour palette, type system, design tokens) with signed, 0G-anchored provenance receipts, plus paid tools for social kits, revisions, and verification.
      1
      -

    • DotI

      idotmy
      F
      license
      Not graded
      quality
      B
      maintenance
      Cross-chain decentralized Web3 identity protocol. Canonical naming resolvable across all EVM networks via Chainlink CCIP and EIP-3668.
      -

    • ClawDaddy MCP Server

      gregm711
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to check domain availability, purchase domains via Stripe, and perform full DNS and nameserver management. It facilitates automated domain lifecycle tasks like record updates and transfer locks without requiring CAPTCHAs.
      MIT

    • DomScan MCP Server

      estevecastells
      A
      license
      A
      quality
      D
      maintenance
      Domain intelligence for DNS, WHOIS/RDAP, SSL/TLS, subdomain discovery, availability, valuation, email security, and typosquatting and brand protection.
      1
      2
      MIT

    • mcp-server-domain-tools

      tudadada
      A
      license
      B
      quality
      C
      maintenance
      Enables domain investors, webmasters, and autonomous agents to perform comprehensive domain audits including brand scoring, TLD tier analysis, and DNS connectivity checks, and to generate strategic brand suffixes and industry compound variations for portfolio expansion.
      2
      6 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

    A3.9/5.0

    Scored across 11 tools

    Disambiguation5/5

    Every tool targets a distinct action: forking vs. reading lineage, onboarding vs. verifying, MQTT publish/subscribe vs. signed meeting messages, and presence vs. meeting lifecycle. Even the two MQTT-related paths are clearly separated by their arguments and purpose.

    Naming Consistency4/5

    All tools share the glyphdna_ prefix and use snake_case, with clear action-style names like glyphdna_fork, glyphdna_mqtt_pub, and glyphdna_meet_close. Minor inconsistency comes from noun-only names such as network_status, presence, and lineage, which break the verb-led pattern.

    Tool Count5/5

    Eleven tools is well-scoped for an ecosystem server covering identity, network status, MQTT messaging, presence, verifiable meetings, and script provenance. Each tool represents a distinct capability with no obvious redundancy.

    Completeness3/5

    Core workflows exist for joining, verifying, forking, lineage, and meeting lifecycle, but there are notable gaps: forked scripts are created visible=False with no enable/publish tool, there is no script read/search/delete operation, and no leave/revoke identity or meeting transcript retrieval. These gaps create avoidable dead ends for agents.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources