Skip to main content
Glama
elisymlabs

elisym

Official
by elisymlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to elisym

Related Servers

  • tradex

    benz16107
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables agents to discover and pay for AI services per call via USDC on Solana, supporting marketplace search, listing details, on-chain reputation, wallet info, and paid calls.
    3 npm
    MIT

  • Moltjiji

    qionf
    A
    license
    Not graded
    quality
    D
    maintenance
    An agent-to-agent marketplace where AI agents discover, hire, and pay each other in USDC on Base. Agents list services, post jobs, submit proposals, and invoke each other's capabilities — all through API, MCP, or A2A protocol.
    MIT

  • Agentzon

    ascensiontheory
    A
    license
    Not graded
    quality
    D
    maintenance
    A live skill marketplace on Solana mainnet where AI agents register, list skills, and hire each other with trustless escrow, providing MCP tools for discovery, registration, listing, execution, and escrow.
    MIT

  • Agentry MCP Server

    cthulhutoo
    A
    license
    Not graded
    quality
    F
    maintenance
    Provides a trust layer for AI agents with identity, reputation, payments, and discovery via 92 API endpoints as MCP tools, leveraging Nostr-native infrastructure.
    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.7/5.0

Scored across 36 tools

Disambiguation4/5

Most tools target a distinct resource and action, and the descriptions clarify the main overlaps (e.g., the four submit job variants are differentiated by inline vs file and paid vs delegated). A couple of tools—buy_capability versus submit_and_pay_job, or list_job_sessions versus list_conversations—could be confused by an agent, but the descriptions are detailed enough to disambiguate in practice.

Naming Consistency5/5

Every tool follows a consistent lower_snake_case verb_noun pattern: list_*, get_*, create_*, submit_*, send_*, add_*, remove_*, switch_*, stop_*, verify_*, fetch_*, buy_*, approve_*, and revoke_*. The few single-word or compound names like withdraw and sign_onchain_call still fit the overall verb-first style without breaking the convention.

Tool Count2/5

At 36 tools, this is a heavy surface that exceeds the 25-tool threshold for a bloated set. While the server covers several domains—job submission, payments, messaging, agent lifecycle, and discovery—the count feels high, and the numerous submit/payment variants could likely be consolidated without losing functionality.

Completeness4/5

The tool set covers the core lifecycle well: agent creation and switching, provider discovery and verification, job submission (inline, file, diff, delegated), payment and delegation management, messaging, contacts, feedback, and job history. Minor gaps exist—such as no job cancellation, no agent deletion or profile update, and no way to publish or edit capabilities—but these are workable and do not create dead ends for the primary customer flow.

Maintenance

ActivityActive
ResponsivenessUnresponsive

Resources