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 up to 102 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 graded report with the exact prompt that caused each failure and the agent's exact reply.

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, and iFixAi never sees your agent's credentials after you store them.

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

On the free plan, steps 2–3 fall away: run-inspection returns the local command directly, with your endpoint and fixture file passed as arguments.

  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 a fixture: the spec iFixAi grades against. Free.
  2. Register the endpoint. URL plus credential. Test it before spending anything.
  3. Quote the run. See the credit cost and how much of your selection can actually reach your agent.
  4. Run. Returns immediately with a run id; inspections take minutes to tens of minutes.
  5. Read the report. Findings with evidence.

Why the fixture matters. Without one, iFixAi grades your agent against a generic placeholder, and the result is meaningless. The connector refuses to start a run that would do that.

Example prompts

0. Try it free, on your own machine

"Audit the agent in this repo with iFixAi. I'm on the free plan: write the fixture, then give me the command to run it locally."

1. Set up and inspect an agent end to end

"Here's my support agent's system prompt: [paste]. Author an iFixAi fixture from it, register the agent at https://api.example.com/v1/chat/completions with my bearer token, and quote a full inspection."

2. Check the cost and coverage before committing

"What would it cost to run the core suite on my agent, and how many of those inspections actually dial 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 balance

"How many iFixAi credits do I have left, and what did my last three runs cost?"

5. Stop a run

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

Tools

Six tools answer on the free plan: get-plan, list-inspections, run-inspection, request-credits, search, fetch. The rest need a paid workspace and say so plainly when they don't have one.

ToolDoesCosts credits
get-planWhich plan this account is on and where runs executeno
get-walletCredit balance for your workspaceno
list-inspectionsThe inspection roster and what each one checksno
author-fixtureTurns your agent's description into a fixtureno
validate-fixtureWhich inspections a fixture can run, and why the rest can'tno
save-fixtureStores a fixture against a connection, so a rerun needs no re-authoringno
get-fixtureThe fixture saved for a connectionno
estimate-run-costCredit quote plus coverage warningsno
create-connectionRegisters your agent's endpoint and credentialno
test-connectionDials your agent once to check it answersno
list-connectionsEndpoints registered in your workspaceno
run-inspectionPaid: starts a billed hosted run, returns a run id immediately. Free: returns the command to run locallypaid only
get-runStatus, grade, score, credits quoted and settledno
list-runsYour runs, newest firstno
get-deliverableThe frozen report for a finished runno
get-coverageWhich inspections your recent runs already exercisedno
request-creditsRaises a credit request, priced from your billing termno
list-credit-requestsYour credit requests and where each one standsno
cancel-runStops a run; you pay only what it already used (in 50-credit blocks, never more than the quote), the rest of the hold returnspart refund
searchFind inspections and your runs by keywordno
fetchOne search result as a documentno

Choosing what to run

Suites range from smoke (3 inspections) to all (102 hosted; the free roster is the 45 open-source inspections). Quote first: estimate-run-cost tells you two things that aren't obvious from the suite name.

Reading a result

passThe agent met the inspection's threshold.
failIt didn't. The report carries the prompt and the reply.
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-credits upgrades.
workspace has no tenantProvisioning didn't finish. Ask us.
not enough creditsTop up before running.
this run has no fixtureAuthor 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, you're never billed twice for the same start.

Support

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