Skip to main content
Glama
nymrel

@nymrel/mcp-hub

Official
by nymrel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to @nymrel/mcp-hub

No user-submitted related servers found.

    Related Servers

    • wham-engine by Whambammy

      wham-engineofficial

      Whambammy
      A
      license
      C
      quality
      C
      maintenance
      Provides AI agents with 200 deterministic micro-services covering code auditing, 3D/robotics, media processing, cryptography, blockchain settlement, AI safety, networking, and math, with automatic x402 USDC micropayments.
      200
      MIT

    • @coragentic/mcp

      coragentic
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables agents and clients to manage wallet-owned identity, private per-agent context, swarm coordination, jobs and offerings, policy-gated tool execution, and audit proofs, with Robinhood Chain execution and payment verification support.
      -

    • @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.
      0
      5
      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 14 tools

    Disambiguation4/5

    Each tool targets a distinct functional area—commerce, proof verification, crawling, sandboxing, swarm coordination, etc.—and the descriptions make those boundaries clear. A few pairs (proof_ledger/proof_verify, swarm_claim/swarm_bus) are semantically adjacent but not interchangeable, so the risk of selecting the wrong tool is low.

    Naming Consistency3/5

    All tool names follow a consistent lowercase snake_case style with the nymrel_ prefix, which aids readability and grouping. However, the second element mixes actions ('audit', 'ping', 'render') with nouns ('ledger', 'mesh', 'bus', 'sandstorm'), so there isn't one strict verb_noun or noun_verb pattern.

    Tool Count5/5

    At 14 tools, the server is well-scoped for a multi-purpose MCP hub that covers commerce, security, swarm coordination, proof attestation, crawling, and rendering. Each tool addresses a distinct capability without redundancy or unnecessary bloat.

    Completeness4/5

    The tool surface covers complete workflows within its major clusters: attestation has generation and verification, swarm has claiming, communication, and health pings, and UCP has auditing as well as execution. Minor gaps exist, such as no explicit tool for deleting or managing previously generated artifacts, but these do not create dead ends for the intended agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources