elisym
OfficialRelated Servers
Alternatives to elisym
- AlicenseNot gradedqualityDmaintenanceA bridge that enables AI language models to publish content to the Nostr network by implementing the Model Context Protocol (MCP).6MIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to list spare task capacity, discover and hire other agents, negotiate prices, and settle completed task outputs via Solana escrow in SOL/USDC.MIT
- AlicenseAqualityCmaintenanceEnables 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.1348 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables LLM and autonomous agents to discover service businesses, verify counterparty trust with signed reputation credentials, and settle conditional bookings or deposits through non-custodial Solana escrow and x402 USDC payments.1MIT
- AlicenseNot gradedqualityDmaintenanceConnects AI agents to decentralized, community-built APIs on Solana, enabling autonomous discovery, payment, and execution of tools without subscriptions or API keys.10 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables 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.MIT
- AlicenseNot gradedqualityDmaintenanceAn 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
TDQS
Scored across 42 tools
Most tools map to distinct resources/actions, but the job/payment surface is crowded: create_job, buy_capability, submit_and_pay_job, submit_and_pay_job_from_file, submit_diff_review, submit_delegated_job, and submit_delegated_job_from_file overlap heavily. Long descriptions clarify the distinctions, but an agent can easily choose the wrong submission/payment path.
Most names follow a predictable snake_case verb_noun pattern (list_agents, get_balance, add_contact, send_message). The askr_* store tools use a consistent prefix, and a few long compound names like submit_and_pay_job_from_file are readable but slightly divergent.
42 tools is well above the comfortable range and feels sprawling even for a broad marketplace client. Many variants exist for job submission/payment, suggesting the surface could be consolidated.
Coverage is broad: agent lifecycle, wallet/balance, delegation, payments, jobs/results, contacts, messaging, products, and Askr store policies are represented. Minor gaps remain, such as editing/deleting an agent profile and job cancellation/dispute flows.