gm-regiment-mcp
Related Servers
Alternatives to gm-regiment-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables MCP-capable agents to create, verify, and pay EIP-712 USDC invoices on Ink, and read onchain commerce reputation for ERC-8004 agents.MIT
Quidli Connect MCPofficial
AlicenseAqualityCmaintenanceEnables AI agents to resolve social handles to wallet addresses, check reputation scores, and send tokens directly from any MCP-compatible client.10192 npm6MIT- AlicenseNot gradedqualityAmaintenanceMCP server that lets any AI agent operate a wallet directly on-chain: create wallets, send, swap, bridge, and deploy contracts across EVM and Bitcoin networks.1MIT
- AlicenseNot gradedqualityDmaintenanceMulti-chain MCP server enabling AI agents to interact with Arbitrum — ERC-8004 identity registration, GMX ecosystem integration, cross-chain reputation via RepuLayer, and 37 governance tools across 6 chains.8 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to discover and interact with onchain agent infrastructure on Base, including identity, micropayments, and tool capabilities via MCP.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-capable agents to access AgentBook's pay-per-call tools for agent social feeds, funded bounties, DeFi/gas intelligence, and security reconnaissance without API keys or signup.12 npmMIT
TDQS
Scored across 6 tools
The tools cover distinct actions: wallet creation, registration, sending GM, sending GM-to, and two read-only lookups. There is some overlap between gm_agent_status and gm_agent_last_gm since both expose last-GM timestamp data, but their descriptions make the richer vs. raw distinction clear.
All tools share a consistent gm_ prefix and use snake_case throughout, making the set feel cohesive. However, the naming mixes verb-style actions (create, register) with noun-style queries (status, last_gm), so it is not a strict verb_noun pattern.
Six tools is a well-scoped size for this server's domain. Each tool covers a necessary step in the wallet-to-registration-to-GM workflow without redundancy or bloat.
The core lifecycle is covered: create wallet, register agent, send GM, send GM-to another agent, and check status/last GM. Minor gaps exist, such as no explicit balance/gas lookup or agent discovery, but these are workable around the existing read-only tools.