An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Edison Experimentation Prover to ChatGPT and Claude

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Stop accepting the first solution your agent suggests.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 1 capability

We ship only the actions that matter.

Capability set01 / 01

01

1 capability in this set.

Part of 1 available through Edison Experimentation Prover.

  1. 01

    Validate edison experimentation

    This capability subjects your agent's proposed solution to a structured R&D audit. It checks if the agent tested multiple alternatives, documented failures with root causes, and proved viability through quantified evidence rather than assumptions.

Real work

What teams actually run

01

Software Architecture Selection

Verify that a chosen database or framework was actually the best fit for the specific load and constraints.

02

Process Optimization

Ensure new operational workflows are tested against old methods with clear success metrics.

03

Hardware Prototyping

Apply systematic material testing and iterative design to physical product development.

04

Infrastructure Deployment

Confirm that a new cloud setup includes the necessary failover and monitoring to be considered 'complete'.

Automate a task

Put Edison Experimentation Prover to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Edison Experimentation Prover works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Edison Experimentation Prover to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

866ms average. Fast in production.

Edison Experimentation Prover is checked daily against the live service.

Daily averagePeak 1184ms
Oct 3Today
Fastest day
732ms
Slowest day
1184ms
14-day trend
Stable+4%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 1 capability arrives ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Edison Experimentation Prover, so you can see the experience inside your AI.

It does not authenticate your account with Edison Experimentation Prover. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Edison Experimentation Prover Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_UMZPgT3WihcCcSB3Nac36KXLZfuGNzCN6Yn2jL8p/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Edison Experimentation Prover capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "edison-experimentation-prover-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_UMZPgT3WihcCcSB3Nac36KXLZfuGNzCN6Yn2jL8p/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Edison Experimentation Prover in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Edison Experimentation Prover owners hand off.

This MCP is for technical teams who need to move from 'it works on my machine' to industrial-grade reliability.

  • 01

    Product Managers

    Hand off feature requirements to ensure the proposed roadmap isn't just a list of assumptions.

  • 02

    Software Architects

    Use it to validate that a chosen tech stack or system design has been tested against viable alternatives.

  • 03

    R&D Engineers

    Apply it to formalize the documentation of failed experiments and iterative improvements.

FAQ

Questions Edison Experimentation Prover owners ask.

  • 01

    What does EXPERIMENT_ABSENT mean?

    It means the agent picked the first idea or a 'standard' solution without testing any actual alternatives against measured criteria.

  • 02

    How does this MCP prevent bad software decisions?

    It forces the agent to prove that a solution is viable, complete, and has been iterated upon, rather than just being 'good enough'.

  • 03

    Can I use this with Cursor or Windsurf?

    Yes, this MCP works with any MCP-compatible client, including Cursor, Windsurf, and VS Code.

  • 04

    What is the difference between iteration and experimentation?

    Experimentation is testing different approaches to find the right one. Iteration is refining the chosen approach through measured cycles to reach peak performance.

  • 05

    Does this capability provide the data for the experiments?

    No, the capability acts as a validator. Your agent must provide the data, the alternatives tested, and the results for the capability to audit.

  • 06

    Doesn't requiring experiments slow down decision-making?

    A 2-day pilot testing 3 alternatives is faster than an 8-month correction after choosing wrong. Edison's Menlo Park produced a major invention every 10 days. systematic experimentation is FASTER than guessing, because you avoid expensive dead ends. The team that picked the traditional system without testing spent 6 weeks migrating. A 3-day comparison pilot would have cost 1/30th of the migration.

  • 07

    What counts as sufficient iteration?

    Test variations until you hit diminishing returns. At minimum 3 variations beyond the first working version. Measure the delta between each: V1 → V2 improved throughput 40%. V2 → V3 improved 12%. V3 → V4 improved 2%. Diminishing returns at V3. ship V3. Edison tested 10,000 battery experiments but he was measuring progress. If V2 shows < 3% improvement over V1 for a non-critical metric, iteration on THAT axis is done. Move to the next constraint.

  • 08

    How does it differ from the Watt Efficiency Prover?

    Watt validates OPTIMIZATION of existing systems. measuring waste, isolating bottlenecks, quantifying improvement. Edison validates DECISION-MAKING for new choices. testing alternatives, iterating designs, building ecosystems, proving viability. Watt asks 'where is 80% of your resources being wasted?' Edison asks 'how many alternatives did you test before choosing this one?' Use Watt when tuning a running operation. Use Edison when making a strategic choice or building a new capability.

Explore

More in Complex Reasoning

Suggestions

Connect Edison Experimentation Prover to Claude, Cursor, ChatGPT & more