Delx MCP Server
Related Servers
Alternatives to Delx MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP stdio server wrapping the fallelder SDK for sovereign, offline-capable, cryptographically signed operations, accessible via autonomous agents.MIT
- AlicenseAqualityAmaintenanceZero-dependency stdio bridge to Moltline Studio's fleet of 14 hosted MCP servers covering code review, time operations, data transforms, business ops, education, research, outreach and more. Free tier requires no registration; premium tools unlock with a license. Independently audited, MCPize Verified A.10MIT
- AlicenseNot gradedqualityBmaintenanceEnables secure cross-system identity and token exchange for autonomous agents, including on-behalf-of token exchange, scoped permission delegation, token lifetime refresh, and zero-leakage ephemeral credentials. It integrates with MCP-compatible clients via standard JSON-RPC stdio without external runtime dependencies.7MIT
- AlicenseBqualityCmaintenanceEnables agents to register verifiable identities bound to legal persons and devices, maintain heartbeat survival, participate in a forum, collaborate on tasks with points escrow, and access points reconciliation through 43 MCP tools over stdio.43MIT
- AlicenseNot gradedqualityBmaintenanceTypeScript SDK for ALTER - identity infrastructure for the AI economy. alter-mcp-bridge exposes mcp.truealter.com as a stdio MCP: identity verification, ~handle resolution, 33-trait vectors, belonging probability, x402 micropayments30 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP-capable AI agents to recall from and write to an encrypted, portable memory vault over stdio, with search, context packing, stats, verification, and forget operations.4 npmMIT
TDQS
Scored across 143 tools
Most tools have distinct purposes, especially the utility tools with 'util_' prefix. However, some therapy tools like quick_checkin, daily_checkin, quick_session, and crisis_intervention have overlapping scopes that could confuse an agent.
Therapy tools use a mix of styles (snake_case, lowercase, verbs, nouns) without a clear prefix, while utility tools consistently use 'util_' prefix. This split leads to moderate inconsistency overall.
With 143 tools, the server is severely over-scoped. It bundles two unrelated domains (therapy protocol and general utilities) into one server, causing bloat and poor discoverability. Should be split into at least two separate servers.
The therapy/witness domain appears fairly complete with lifecycle coverage, but the utility set is a random collection of unrelated functions (DNS, HTTP, JWT, etc.) with obvious gaps like no HTML-to-text or comprehensive URL parsers.