iFixAi · MCP connector

Inspect your AI agent from your coding assistant

iFixAi runs an operational-misalignment diagnostic against an AI agent you already have deployed. This connector lets Claude or ChatGPT drive it: describe your agent, register its endpoint, run inspections, and read what went wrong.

What it does

iFixAi dials your agent over its own HTTP endpoint and puts it through inspections: does it invent facts, exceed its authority, leak data it shouldn't, change its story under pressure, act when it should escalate. You get a report of findings, each with the exact prompt that caused it and the agent's exact reply as proof.

It reports what your agent got wrong. It does not prescribe fixes.

Two plans, one connector

What you need first

Connect

Add the server URL in your client's connector settings:

https://mcp.ifixai.ai/mcp

Your client will open a browser window to sign in to iFixAi and ask you to approve access. That's standard OAuth 2.1. The connector never sees your password. Your agent's key never goes through the chat: you paste it on a one-time link, or Claude Code sends it with the key command. It is stored server-side and never shown again.

Not sure which plan you're on? Ask for get-plan first. Every paid-only tool tells a free caller plainly what it does and that a paid workspace unlocks it, rather than leaving you guessing.

The order things happen in

  1. Describe your agent. Paste its system prompt, or a plain description: roles and their limits, the tools it can call, the data it reads, the rules it must follow. This becomes its simulation environment: what the agent is supposed to do, which every inspection tests it against. Free.
  2. Register the endpoint. Just the URL. Its key goes through a one-time link or the key command, never the chat. Test it before you start a run.
  3. Preview the run. See what is outside your package, how much of your selection can actually reach your agent, and the audits left this month.
  4. Run. Returns immediately with a run id; inspections take minutes to tens of minutes.
  5. Read the report. Findings with evidence.

Why the simulation environment matters. Without one, iFixAi would test your agent against a generic placeholder, and its findings would mean nothing. The connector refuses to start a run that would do that.

Example prompts

1. Set up and inspect an agent end to end

"Here's my support agent's system prompt: [paste]. Build its iFixAi simulation environment from it, register the agent at https://api.example.com/v1/chat/completions, which takes a bearer token, and preview a full audit."

2. Check coverage before you run

"What would a full audit of my agent cover, and how many of those inspections actually reach it?"

3. Read the result of a finished run

"Get run run_ab12… and tell me what my agent got wrong, worst first."

4. Check the package

"Which iFixAi package am I on, and how many audits do I have left this month?"

5. Stop a run

"Cancel the inspection I just started. I picked the wrong suite."

Tools

Seven tools answer on the free plan: get-plan, run-demo-audit, claim-fast-audit, redeem-code, request-access, search, fetch. The rest need a paid workspace and say so plainly when they don't have one.

ToolDoesCounts an audit
get-planWhich plan this account is on, its package and this month's auditsno
run-demo-auditA demo audit of a made-up support bot; nothing runsno
claim-fast-auditClaims this account's one free fast auditno
redeem-codeRedeems a promo code you were given, one per accountno
select-repo-filesPicks the repo files worth reading for a build, and how to upload themno
build-simulation-envTurns your agent's repo or description into its simulation environmentno
preview-runWhat is outside your package, audits left, plus coverage warningsno
create-connectionRegisters your agent's endpoint. Its key comes by a one-time link or the key command, never the chatno
set-role-loginsSets a test login per role, so messages sent as a role use its tokenno
wire-sandboxA prompt for your coding agent that points your test copy's actions at our sandboxno
get-sandbox-addressThe sandbox address behind the wire-sandbox Copy button, for the widget onlyno
rotate-sandboxReplaces a leaked sandbox address; the old one stops working at onceno
test-connectionSends your agent two test messages, plus one per role login, to check it answersno
list-connectionsEndpoints registered in your workspaceno
run-inspectionStarts a hosted run, returns a run id immediatelypaid, once it completes
get-runStatus, and how many inspections have passed and failed so farno
list-runsYour runs, newest firstno
get-deliverableThe frozen report for a finished runno
get-deliverable-payloadThe same report for the report widget to show, not for the chatno
request-accessAsks for a package, or a bigger one; we assign it by handno
stop-runStops a run and keeps what finished as a partial reportonce anything finished
searchFinds your runs by run id, agent name or statusno
fetchOne search result as a documentno

Choosing what to run

Suites range from a few inspections to all (hosted, as far as your package reaches). Preview first: preview-run tells you one thing that isn't obvious from the suite name.

Reading a result

passNo finding: the agent did what the inspection looks for.
failA finding, with the prompt we sent and your agent's reply as proof.
inconclusiveThe inspection couldn't reach a verdict, usually a surface your endpoint doesn't expose. Not a failure, and not a pass either.

When something goes wrong

MessageMeans
this needs a paid workspaceYou're on the free plan. The message says what the tool does and what paying adds; request-access asks for a package.
workspace has no tenantProvisioning didn't finish. Ask us.
no package, outside the package, audits used upEach names the way out: drop the inspections, wait for the 1st, or request-access for the package that has it.
this agent has no simulation environmentBuild one first, see step 1.
backend unreachableOurs, not yours. Try again shortly.

A run keeps going even if your client disconnects. Poll get-run with the id to pick it back up. The same start never counts as two audits.

Support

Email support@ifixai.ai. Include your run id if it's about a specific run.