
Reasoning Commons
io.github.chenyuan35Published by GitHub account chenyuan35v1.0.0Updated Nov 2, 2026
AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.
The publisher's own server: AI Reasoning Commons
Overview
Remote MCP endpoint for an AI reasoning cache and consensus layer, exposing 11 tools over Streamable HTTP alongside AI usage-reset and relay-risk tools.
- What you can do
- The manifest lists no individual tools, so capabilities come from the description and README.
- The registry describes a reasoning cache and consensus layer with 11 MCP tools served over Streamable HTTP.
- The README frames the site around three jobs: keeping control of phone numbers AI accounts depend on, tracking when AI usage limits reset, and assessing dependency risk from third-party AI relays.
- Supporting surfaces include a Cursor usage reset calculator, a Claude Code limit reset calculator, and an evidence-backed 0-100 Exit Risk Index for AI relays.
- Older general calculators and image tools are described as maintenance-only.
- When to use it
- Consider it when you want an assistant to consult a shared reasoning cache or consensus layer, or to look up AI usage-limit reset timing and relay dependency risk. It is aimed at AI power users managing access, usage and vendor dependency.
- Requirements
- A remote Streamable HTTP endpoint; no package installation. The manifest declares no authentication, environment variables or headers, and the README says the public tools need no sign-up. Network access to the hosted site is required.
Installation
In SourceWeft
- Open Reasoning Commons in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.chenyuan35%2Freasoning-commons/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"reasoning-commons": {
"type": "http",
"url": "https://aineedhelpfromotherai.com/api/mcp"
}
}
}README
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
- Phone Number Survival Guide — plan how to buy, activate, verify, use abroad, keep alive, and recover a number that an important account may need again
- Cursor Usage Reset Calculator — understand Cursor reset timing and usage pacing
- Claude Code Limit Reset Calculator — track session and weekly reset timing from the reset information shown by Claude
- AI Relay Exit Risk Checker — assess relay dependency with an evidence-backed 0–100 Exit Risk Index
- All tools
What this project is now
The product is intentionally focused on three related jobs for AI power users:
- Access continuity — keep control of phone numbers that AI accounts or services may depend on.
- Usage continuity — understand when AI usage limits reset and when work can resume.
- 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.
Current development rules and project state live in:
AGENTS.mdPROJECT_CONTEXT.mddocs/MASTER_PLAN.mddocs/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
Source: README.md at commit 2dc0d66
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.