Skip to main content
Glama
elisymlabs

elisym

Official
by elisymlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to elisym

Related Servers

  • @txn-dev/mcp-server

    polyxmedia
    A
    license
    A
    quality
    C
    maintenance
    Enables AI assistants such as Claude, Cursor, and Windsurf to create and fund agent wallets, check balances, and move money idempotently between wallets. It also lets them find and hire people by skill, rate, and rating through posted jobs with escrowed budgets, deliverables, payment release, and disputes.
    13
    46 npm
    MIT

  • tradex

    benz16107
    A
    license
    Not graded
    quality
    D
    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.
    30 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
    F
    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
Deploy Server
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

A3.5/5.0

Scored across 38 tools

Disambiguation3/5

The job/payment family is highly overlapping: create_job, submit_and_pay_job, submit_and_pay_job_from_file, submit_delegated_job, submit_delegated_job_from_file, submit_diff_review, buy_capability, buy_product, and send_payment all target similar 'hire an agent' workflows. The descriptions are unusually good at cross-referencing each other (e.g. 'prefer this over...', 'use submit_and_pay_job for auto-payment'), which mitigates but does not eliminate misselection risk.

Naming Consistency4/5

Almost every tool follows a snake_case verb_noun pattern (list_contacts, send_message, buy_product, get_order, approve_delegation), which is highly predictable. Minor deviations like the bare verb `withdraw` are the only break in an otherwise uniform convention.

Tool Count2/5

38 tools is heavy for any single server, and a big chunk is redundant parallelism (paired _from_file variants, separate delegated variants, and multiple near-equivalent purchase/submit tools). The breadth of the domain (marketplace, messaging, payments, delegation, agent lifecycle) partly justifies a larger surface, but it is well past the 25+ threshold.

Completeness4/5

Coverage is broad and coherent: messaging (send/list/read), contacts CRUD, job lifecycle (create/submit/pay/result/file/feedback/list), payments and delegation (balance/send/withdraw/estimate/approve/revoke), identity/verification, discovery, and agent management. Only minor gaps exist, such as no job cancellation, no agent profile update, and no delete_agent.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources