Axint — Claude Code MCP server: Swift checks with Xcode proof
Checks the Swift an AI agent writes, runs the actual Xcode build and tests, then hands back a signed report with the repairs to make next.
claude mcp add --transport http axint https://mcp.axint.ai/mcpWhat Axint does
Axint acts as a gate in front of a merge. It locates the Xcode project and scheme, runs static checks, executes whatever builds and tests are available, and pulls the results into a single verdict. Findings carry an evidence label: confirmed by analysis or compiler output, probable, advisory, or suppressed when stronger data contradicts them. Logs stay on disk; the agent gets a short summary for its next turn.
A one-off run needs no account: npx -y -p @axint/compiler axint prove --dir /path/to/MyApp. Output lands in .axint/proof and source code is not uploaded. Passing --fix turns on the deterministic rewrites the tool supports and repeats the loop. axint receipt verify checks the report's integrity and its embedded signer, though a locally signed file carries no externally trusted identity until CI pins the signer fingerprint or a managed key.
Real proof calls for macOS with Xcode. Without a build and tests the run will not return a passing verdict, and missing tests are not counted as a pass. The server is reachable at https://mcp.axint.ai/mcp, or locally through npx -y @axint/compiler.
What it helps with
- check that agent-written Swift compiles before merging
- run the Xcode test suite and get a verdict with its evidence
- hand the agent a compact fix packet with the exact next step
- verify the signature and integrity of a build report
- wire Swift checks into a CI job on a macOS runner
Example prompts for the agent
- Prove the project at
/path/to/MyAppwith Axint and show me the verdict and findings - Build the scheme and attach the report from
.axint/proof; if tests fail, return the fix packet - Verify the report signature:
axint receipt verify /path/to/MyApp/.axint/proof/latest.proof.json
How to install Axint
1Platform CLI: remote server
claude mcp add --transport http axint https://mcp.axint.ai/mcp2Platform CLI
claude mcp add axint -- npx -y @axint/compiler1Platform CLI: remote server
codex mcp add axint --url https://mcp.axint.ai/mcp2Platform CLI
codex mcp add axint -- npx -y @axint/compilerConfig file
{
"mcpServers": {
"axint": {
"url": "https://mcp.axint.ai/mcp"
}
}
}{
"mcpServers": {
"axint": {
"command": "npx",
"args": [
"-y",
"@axint/compiler"
]
}
}
}Config file
{
"servers": {
"axint": {
"type": "http",
"url": "https://mcp.axint.ai/mcp"
}
}
}{
"servers": {
"axint": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@axint/compiler"
]
}
}
}1Platform CLI: remote server
gemini mcp add -t http axint https://mcp.axint.ai/mcp2Platform CLI
gemini mcp add axint npx -y @axint/compilerStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Axint
How do I install Axint in Claude Code?
Run claude mcp add --transport http axint https://mcp.axint.ai/mcp. For a local server use claude mcp add axint -- npx -y @axint/compiler.
What does Axint do?
It validates Swift in an Xcode project, runs the build and tests, reconciles the findings with Apple tooling output, and returns a signed report with repair guidance.
What is required for Axint to produce proof?
macOS with Xcode, plus a build and tests it can actually run. A run with no available build or tests will not come back as proof.
