Soma
Related Servers
Alternatives to Soma
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceCryptographic identity and trust protocol for AI agents. 38 MCP tools across 8 protocol layers: Ed25519 identity, delegation chains, values compliance, signed communication, policy engine, task coordination, cross-layer integration, and agentic commerce. 264 tests passing.154368 npm4Apache 2.0
- AlicenseCqualityAmaintenanceMCP services for agent security preflight, source scanning, injection screening, proof-of-work policy rehearsal, carbon accounting, climate disclosure and regulatory monitoring. Use each hosted endpoint in the README. Inspect a free quote before buyer-authorized x402/USDC payment. Includes free trust and settlement tools. Maxwell rehearsal does not activate runtime protection.220Apache 2.0
- AlicenseAqualityBmaintenanceTrust layer for AI agents: check any x402 endpoint or MCP server before paying (live status, real price, payTo vs listing, OFAC), plus agent passports with two-sided signed receipts and signed skill releases. Every result is a signed event in a public transparency log.216Apache 2.0
- AlicenseNot gradedqualityBmaintenanceThe kernel that doesn't believe the agents — a domain-free trust substrate for fleets of autonomous agents: verify what shipped, arbitrate collisions, refuse with structured reasons.209 PyPI21MIT
- AlicenseBqualityBmaintenanceOpen end-to-end encrypted messaging protocol and MCP server (a4a-mcp) that gives AI agents a cryptographic address (apub1...) to exchange messages, tasks, and signed agreements directly across NAT without port forwarding.443MIT
- AlicenseNot gradedqualityBmaintenanceEnables users' AI agents to join signed, hash-chained rooms with another person's agent to negotiate, coordinate, or hand off work, while a locally enforced mandate filters every outbound message. Commitments such as accepts, grants, or priced proposals are released only by an approval signed by the human principal and bound to that exact message.18 npmApache 2.0
TDQS
Scored across 17 tools
Each tool maps to a distinct operation in the agent workflow: sending, listing, claiming, completing, routing, verification, memory, registration, reputation, and cold storage. Overlaps such as inbox vs claim and agents vs reputation are clarified by their descriptions and different scopes.
All tools consistently use the soma_ prefix and snake_case, making the namespace predictable. The only minor inconsistency is that several tools are noun-only resource names (soma_agents, soma_inbox, soma_stats) rather than a strict verb_noun pattern.
The 17 tools cover a broad but coherent agent-hub domain with multiple sub-areas: envelopes, registry, memory, reputation, and cold storage. The count is slightly heavy but each tool earns its place; no obvious redundant tool is present.
Core lifecycle operations are covered: register, discover, send, claim, complete, verify, route, remember/recall, export, and cold-storage put/get. Minor gaps remain, such as no explicit receipt issuance/verification despite paid envelopes, and no update/delete operations for facts or cancellation of envelopes.