MCP status
MCP is not live.
Artax does not ship an MCP server. Use OpenAPI, llms assets, SDK helpers, and the AI-agent onboarding path for integration.
The agent surface is real, but it is not MCP.
Artax publishes OpenAPI, a public-tool registry, generated tool and claim indexes, `llms` discovery assets, and a dedicated AI-agent onboarding path. It does not publish a live MCP server. This page keeps that boundary explicit so agents use the available HTTP and SDK paths instead of calling nonexistent tools.
Live MCP surfaces
0
No MCP server package or endpoint is live.
Current public tools
61
Current public tool names are already published through the HTTP API and tool index.
Reserved review tools
4
HTTP review operations reserved as the narrow MCP boundary if a separate MCP surface is approved.
Current boundary
What is true now
Current reality
MCP is not live. Any stronger claim would be misleading.
Reserved boundary
The only reserved MCP boundary is read-only or review-first. Submit and mutation stay outside that boundary.
Why submit is excluded
Submit and mutation tools would outrun current support, approval, and compatibility truth if they were exposed through a first MCP release.
Use instead today
Use `/openapi.yaml`, `/llms.txt`, `/llms-full.txt`, the tool index, the AI-agent onboarding page, and the developer docs.
Reserved MCP Review Boundary
get_health
HTTP route
GET /api/health
Audience
Public
Auth model
Public
Supported flows
No supported-flow ids required.
get_public_config
HTTP route
GET /api/config/public
Audience
Public
Auth model
Public
Supported flows
No supported-flow ids required.
analyze_transfer
HTTP route
POST /api/analyze-transfer
Audience
Builder
Auth model
Developer API Key Or Public Demo
Supported flows
spl_token_transfer_review_and_submit; transfer_sponsorship_class_a_simple_transfer; transfer_sponsorship_class_b_account_setup; transfer_sponsorship_class_c_wsol_setup; transfer_sponsorship_class_d_bounded_principal
analyze_swap
HTTP route
POST /api/analyze-swap
Audience
Builder
Auth model
Developer API Key Or Public Demo
Supported flows
simple_swap_review
Still out of scope
- submit_transfer and submit_transaction stay out of initial MCP scope so the MCP surface does not outrun current support or approval boundaries.
- Operator mutation tools, sponsorship overrides, secret rotation, and webhook replay stay out of first scope because they exceed a review-first, fail-closed posture.
- Any sponsored execution path stays out until human approval defaults, compatibility truth, and launch-gate evidence exist for that exact surface.
Publication controls
No live MCP claim
Do not claim a live MCP server, MCP auth model, or MCP tool-execution surface exists without an actual server package, endpoint, and launch-gate evidence.
HTTP and OpenAPI stay canonical
OpenAPI, the public-tool registry, and the generated tool index remain the canonical structured source of truth unless a real MCP server is approved and shipped.
Reserved MCP boundary stays review-first
Any separate MCP release must stay limited to read-only or review-first tools unless a new approved scope explicitly widens it, and it must reuse the canonical public tool ids.
Submit and mutation stay gated
Submit, sponsorship, and mutation surfaces stay out of first MCP scope and must not ship until explicit human approval defaults, compatibility truth, and launch-gate evidence exist for that exact surface.
Production claims remain narrow
Discovery assets and MCP-status docs must stay narrower than current compatibility certification and release-evidence posture, even when the HTTP contract and tool ids are already published.
Current references
OpenAPI
OpenAPI is the main public API reference today.
Public-tool registry
Public tool ids already exist in the HTTP contract and tool index.
Agent guide
The current AI guidance points clients to the public API and does not advertise MCP support.
Locked scope policy
Submit, sponsorship mutation, and admin mutation stay outside the reserved MCP boundary.
Developers
Use the developers page for hosted review, API, SDK, embedded UI, and account guidance.
AI-agent onboarding
Follow the live onboarding wizard instead of assuming a tool-server bootstrap exists.
Quickstart
Start with the supported setup flow rather than assuming an MCP transport.
Trust
See how trust, compatibility, and launch limits shape agent-facing claims.
Comparisons
Keep AI-agent and tool-surface claims narrower than current support and competitive truth.