tokonomix-council-mcp
OfficialRelated Servers
Alternatives to tokonomix-council-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI coding agents to consult a multi-model deliberation council before irreversible, high-stakes decisions, returning structured architectural decision records with consensus and dissenting risks.-
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to send a prompt to multiple LLMs simultaneously and get a judge model's structured comparison of their responses. This surfaces consensus, contradictions, and blind spots, letting Claude write a more informed final answer.1MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to create council hearings where multiple LLMs (Claude, GPT, Gemini, Grok) debate topics and synthesize verdicts with trust scores and diverse perspectives.28Apache 2.0
- AlicenseAqualityBmaintenanceEnables role-based, multi-model AI orchestration by assigning specialized expert roles to a hybrid panel of local and cloud LLMs, generating unified advisory council reports for complex tasks.61MIT
- AlicenseAqualityDmaintenanceProvides access to multiple frontier LLM models (GPT, Claude, Gemini, Grok, DeepSeek) for consulting a "conclave" of AI perspectives, enabling peer-ranked evaluations and synthesized consensus answers for important decisions.81MIT
- AlicenseNot gradedqualityCmaintenanceIntegrates AI Consensus into coding agents, routing decisions through three frontier AI models for independent analysis and cross-examination, returning a recommendation and strongest dissent.68MIT
TDQS
Scored across 11 tools
Each tool has a uniquely defined purpose: balance check, single vs consensus asks, model listing, skill version/content, onboarding steps, rating, human feedback, and context upload. The two ask tools are clearly differentiated by consensus vs single-model mode, and the two feedback tools separate agent rating from human relay. No overlap or ambiguity exists.
All tools share the tokonomix_ prefix and snake_case, with most following a verb_noun pattern (get_balance, list_models, rate_consensus, relay_human_feedback). Minor deviations include skill_version (noun_verb) and onboard_verify (compound verb), but the overall pattern remains predictable and readable.
At 11 tools, the set is well-scoped for its purpose: onboarding, billing, model discovery, request execution, context staging, feedback, and self-documentation. Each tool earns its place without redundancy or bloat, and the count aligns with typical MCP servers.
The toolset covers the full user lifecycle: onboarding (onboard/verify), account status (get_balance), model discovery (list_models), calling (single/consensus ask), large-context upload, and both human and agent feedback loops. It also includes a self-updating skill doc, and no obvious operational gaps exist for the stated purpose.