Fractal Process Intelligence MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Fractal Process Intelligence MCPRecord this research run and return the X-Ray URL."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Fractal Process Intelligence — Research Alpha
Fractal measures whether additional AI actually created additional intelligence.
Fractal is not trying to make AI smarter. It observes research process and produces an X-Ray of what a polished final answer may hide.
Primary question: Did additional AI actually create additional independent intelligence?
This repository is the public distribution surface for the Fractal Research MCP (recorder/observer). The live remote endpoint is already hosted; this repo documents how to connect and give feedback.
Research Alpha: This is an active research experiment, not a validated commercial product.
What it does
Fractal Process Intelligence MCP is recorder/observer only.
Compatible AI clients can record observable research-process artifacts:
participating agents
meaningful sources
claims
uncertainty
disagreement
tool usage
Then finish_run compiles a process X-Ray (hosted report URL).
Public product page: fractalinfinity.io/research-lab.html
Sample X-Ray: fractalinfinity.io/report/sample.html
Related MCP server: MCP Execution Ledger
What it does NOT do
Call AI models (no Anthropic / OpenAI / Gemini inference)
Buy model inference on your behalf
Require provider API keys
Inspect hidden chain-of-thought
Automatically spawn agents
Estimate Claude/OpenAI billing or token dollar cost
Health check advertises "inference":"none".
Public MCP endpoint
https://mcp.fractalinfinity.io/mcpHealth: https://mcp.fractalinfinity.io/health
Current recorder tools
Tool | Purpose |
| Open a run |
| Record agent identity / optional metadata |
| Record a cited source + lineage |
| Record claim stance |
| Record tool-call evidence |
| Finalize → X-Ray URL |
Claude Desktop (Windows) alpha setup
Claude Desktop → Settings → Developer → Edit Config
Merge the MCP entry below (do not wipe other config keys).
Save.
Fully quit Claude (system tray → Quit).
Reopen Claude.
Settings → Developer should show
fractal-process-intelligencerunning.
{
"mcpServers": {
"fractal-process-intelligence": {
"command": "C:\\Program Files\\nodejs\\npx.cmd",
"args": [
"-y",
"mcp-remote",
"https://mcp.fractalinfinity.io/mcp"
]
}
}
}See also: examples/claude-desktop.mcp.fragment.json
Microsoft Store builds of Claude may store config under a package LocalCache path; prefer Edit Config so Claude opens the file it actually reads. Use the full npx.cmd path on Windows.
Example research instruction
Paste into a new research conversation after connecting:
Use Fractal Process Intelligence to record this research run.
Record the participating agents, meaningful sources, important claims,
uncertainty, disagreement and significant tool usage.
Finish the run and return the Fractal X-Ray URL.
Do not interpret the X-Ray for me before I open it.Then ask your normal research question. Read the AI’s final answer first. Open the X-Ray second.
Privacy / security boundary
Fractal records only artifacts explicitly sent through its MCP tools.
It does not automatically record every Claude (or other) conversation. For normal chats, do not start a Fractal run / do not invoke its tools.
Feedback (the research question)
Open a GitHub Issue or reply in discussions.
Please answer:
Did the X-Ray reveal something consequential you would not have known from the final AI answer alone?
Would you want this attached to your normal research or agent workflow?
Optional: what was confusing or misleading?
Links
Resource | URL |
Research Lab | |
Sample X-Ray | |
MCP endpoint | |
Health |
License
MIT — see LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
Machine-native research commons for agent evidence, discovery, rooms, and bounded research quests.
Cross-agent artifact workspace with provenance across Claude Code, Codex, Cursor, LangGraph.
Shared, versioned context that humans and AI agents can publish, review, annotate, and continue.
- memnodeOAuthdev.memnode
Persistent, inspectable memory for AI agents with lineage, correction, and a hosted MCP endpoint.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides observability for multi-agent workflows by tracking hierarchical task structure, architectural decisions, reasoning, encountered problems, code modifications with Git diffs, and temporal metrics.26 npm-
- FlicenseNot gradedqualityBmaintenanceRecords all MCP tool interactions in a centralized ledger, enabling developers to trace, replay, inspect, and audit AI agent workflows.-
- AlicenseNot gradedqualityCmaintenanceEnables recording and analyzing AI agent execution traces, including event logging, metric computation, loop detection, and JSON export for debugging agent behavior.MIT
- AlicenseNot gradedqualityDmaintenanceEnables step-debugging, deterministic replay, and signed audit evidence for AI agents, compliant with EU AI Act.39 PyPIMIT