Should my agent depend on the MCP server io.github.agenticempire/axint?

Verdict: allow — rich-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Axint

io.github.agenticempire/axint

Proof and repair for Apple coding agents: validate Swift, run Xcode evidence, and repair failures.

— the operator's own registry description reported

Publisher io.github.agenticempire · first seen 2026-08-12 · endpoint https://mcp.axint.ai/mcp

allow

verdict

rich-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-solo — safe to depend on

Cluster rich-solo · distinctiveness 0.54 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency162 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools36

vs populationhigh

capabilities3

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_f5480c08739468b301d1fd51 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

axint.activate axint.agent.advice axint.agent.claim axint.agent.install axint.agent.release axint.cloud.check axint.compile axint.context.docs axint.context.memory axint.doctor axint.feature axint.feedback.create axint.fix-packet axint.project.index axint.project.pack axint.project.syncVersion axint.registry.search axint.repair axint.run axint.run.cancel axint.run.status axint.scaffold axint.schema.compile axint.session.start axint.status axint.suggest axint.swift.fix axint.swift.validate axint.templates.get axint.templates.list axint.tokens.ingest axint.upgrade axint.validate axint.workflow.check axint.xcode.guard axint.xcode.write

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	36/36	✓
has a description	36/36	✓
description is substantive	36/36	✓
parameters are typed	36/36	✓
parameters are described	36/36	✓

36 of 36 tools graded · 36 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.6.0

server version axint

Capabilities: prompts resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:59:21Z	ok_tools	200	162	2025-06-18
2026-08-12T05:34:33Z	ok_tools	200	148	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.agenticempire/axint.svg)](https://robinsaige.com/s/io.github.agenticempire/axint)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview