@nymrel/mcp-hub
OfficialRelated Servers
Alternatives to @nymrel/mcp-hub
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceExposes 20 deterministic tools for finance, data, content, and lifestyle tasks via MCP, A2A, and REST interfaces, enabling automation and multi-agent workflows.MIT

wham-engineofficial
AlicenseCqualityCmaintenanceProvides AI agents with 200 deterministic micro-services covering code auditing, 3D/robotics, media processing, cryptography, blockchain settlement, AI safety, networking, and math, with automatic x402 USDC micropayments.200MIT- AlicenseNot gradedqualityBmaintenanceEnables agents and clients to manage wallet-owned identity, private per-agent context, swarm coordination, jobs and offerings, policy-gated tool execution, and audit proofs, with Robinhood Chain execution and payment verification support.MIT

warppay402-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to access 28 monetized Web3 developer tools, including web scraping, PDF extraction, smart contract deployment, and cross-chain USDC micropayments via SSE and x402.MIT- AlicenseAqualityAmaintenanceEnables AI agents to publish, claim, submit, and settle tasks with each other, including automatic decomposition of complex work into subtasks assigned to specialized agents. Also provides a unified gateway to call multiple large language models (DeepSeek, Qwen, GPT, Claude, Doubao) with one API key, plus tools for agent messaging, balances, identity, and model preferences.16MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to register an identity and API key, call free tools such as prop-firm drawdown rules, an AI-writing check, and current LLM per-token pricing, and keep versioned memory, notes, and end-to-end encrypted storage that persists across restarts. It also lets agents claim and verify jobs, publish profiles and skills with A2A/MCP/x402 endpoints, and discover other agents by skill or tag.MIT
TDQS
Scored across 14 tools
Each tool targets a distinct functional area—commerce, proof verification, crawling, sandboxing, swarm coordination, etc.—and the descriptions make those boundaries clear. A few pairs (proof_ledger/proof_verify, swarm_claim/swarm_bus) are semantically adjacent but not interchangeable, so the risk of selecting the wrong tool is low.
All tool names follow a consistent lowercase snake_case style with the nymrel_ prefix, which aids readability and grouping. However, the second element mixes actions ('audit', 'ping', 'render') with nouns ('ledger', 'mesh', 'bus', 'sandstorm'), so there isn't one strict verb_noun or noun_verb pattern.
At 14 tools, the server is well-scoped for a multi-purpose MCP hub that covers commerce, security, swarm coordination, proof attestation, crawling, and rendering. Each tool addresses a distinct capability without redundancy or unnecessary bloat.
The tool surface covers complete workflows within its major clusters: attestation has generation and verification, swarm has claiming, communication, and health pings, and UCP has auditing as well as execution. Minor gaps exist, such as no explicit tool for deleting or managing previously generated artifacts, but these do not create dead ends for the intended agent workflows.