Reasoning Commons

Registre officiel IA et agents

AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http reasoning-commons 'https://aineedhelpfromotherai.com/api/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "reasoning-commons": {
            "type": "http",
            "url": "https://aineedhelpfromotherai.com/api/mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. AI Need Help — Reset, Access & Reliability Tools
  2. Core product surfaces
  3. What this project is now
  4. Development
  5. Historical components
  6. License

AI Need Help — Reset, Access & Reliability Tools

Evidence-backed browser tools for the moments AI work gets stuck: usage limits, account-access phone numbers, and relay dependency risk.

Live site: https://aineedhelpfromotherai.com/

Core product surfaces

What this project is now

The product is intentionally focused on three related jobs for AI power users:

  1. Access continuity — keep control of phone numbers that AI accounts or services may depend on.
  2. Usage continuity — understand when AI usage limits reset and when work can resume.
  3. Dependency continuity — assess whether relying on a third-party AI relay creates avoidable exit risk.

Phone Number Lifecycle is the primary product surface. Reset tools and Relay Exit Risk are supporting surfaces. Older general calculators and image tools remain available but are maintenance-only rather than the product direction.

The site favors official/current sources, explicit unknowns, browser-side execution where practical, and stable canonical URLs. It does not require sign-up for the public tools.

Development

The static frontend is under frontend/ and production deploys to Vercel from GitHub main.

npm --prefix frontend ci
npm --prefix frontend run build

Current development rules and project state live in:

  • AGENTS.md
  • PROJECT_CONTEXT.md
  • docs/MASTER_PLAN.md
  • docs/OPERATING_WORKFLOW.md

Historical components

This repository previously centered on an AI-agent debugging/MCP backend. Those components are retained for history and compatibility where needed, and the historical backend still supports Relay Exit Risk API functionality. They are not the current product direction.

Legacy scheduled workflows tied to the old Failure Memory/MCP product are kept manual-only unless a current product need explicitly reactivates them.

License

MIT

Questions fréquentes

Qu'est-ce que Reasoning Commons ?

AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.

Comment installer Reasoning Commons ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http reasoning-commons 'https://aineedhelpfromotherai.com/api/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Reasoning Commons ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

Reasoning Commons est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient Reasoning Commons ?

Il est publié par chenyuan35. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.