Conduit Agentic Commerce MCP Server

by aiconduit Your server? Claim it

answering

Conduit Agentic Commerce is answering right now. Last checked 10 min ago. It exposes 20 tools.

Search multi-merchant supply, checkout, and track orders via MCP.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 47 days of history

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

414 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 57

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 August 2026. No other catalogue keeps this.

14 Sep a tool changed the parameters it asks for order_update_status

14 Sep a tool changed version

10 Sep a tool changed version3 times that day

10 Sep 2 tools changed the parameters they ask for order_execute, supply_delivery

10 Sep a tool appeared supply_options

8 Sep a tool changed version

7 Sep 2 tools changed the parameters they ask for agent_create, agent_update

7 Sep a tool changed version

4 Sep a tool changed the parameters it asks for order_execute

4 Sep a tool changed version

and 45 more, back to 11 August 2026

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add conduit --transport http https://mcp.aiconduit.app/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "conduit": {
      "url": "https://mcp.aiconduit.app/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.conduit]
url = "https://mcp.aiconduit.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "conduit": {
      "url": "https://mcp.aiconduit.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "conduit": {
      "url": "https://mcp.aiconduit.app/mcp"
    }
  }
}

Available tools 20

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

agent

agent_authenticate

Two-step re-auth. Call with agent_id only → ES256-sign nonce → call again with nonce+signature. Prefer keys from ~/.conduit ({handle}.credentials.json or legacy credentials.json; CONDUIT_CREDENTIALS_PATH pins one file). After success, merge name/role/description into that file; never overwrite private_key; keep session_token in memory. Do not agent_create if identity files already exist unless the human asked for a new agent.

agent_create

Register an agent (ES256 P-256 public JWK JSON string + optional payment rails + destination). BEFORE: list ~/.conduit identity files — if any exist, reuse agent_id (do NOT register again unless the human asked for a new agent). AFTER: write persist.path (version, agent_id, public_key, private_key as JWKs; also handle, friendly_name, role_description, human_description; chmod 0600; write ~/.conduit/active). Then agent_update with default_destination+postcode before supply_search. Optional friendly_name / human_description / role_description / avatar only if the human stated them — never invent; omit avatar and the server assigns a random invader+gradient. Omit handle to auto-generate (e.g. parcel-watcher-12).

agent_notify

Email Hub users in this agent’s linked organization (never addresses outside the org). to=all or { user_id } / { role } / { email } matching agent_organization members. Optional actions (Hub URLs only), severity, idempotency_key. Channel is email.

agent_organization

Read the linked organization (name, slug, country, default address) and members (user_id, name, role, email) for an agent. Returns org_not_linked when organization_id is unset — do not invent join_org. Use members to target agent_notify.

agent_outreach

Email outside addresses (suppliers, carriers). to is a string email, { email }, or { emails } (max 5). Not to=all and not a Hub user_id / role — those are agent_notify. Linked agents set Reply-To to an org member (default OWNER). No action buttons. Channel is email.

agent_report_issue

Report unexpected tool errors or confusing Conduit outcomes for AX review (agent_report_issue — not order_feedback). Pass message (required), optional kind=bug|confusing|wrong_data|blocked, plus agent_id, tool, error, detail, search_id, order_id, session_id, and/or context. Dedupes open reports with the same tool+error+correlation. Does not change reputation.

agent_update

Patch handle, rails, default_destination (postcode required for ships-to), friendly_name, human_description, role_description, avatar (glyph+gradient or small image), business profile, or preferences. Set avatar only if the human chose it. Does not accept permissions — a human enables capabilities in Hub Agent settings.

order

order_dispute

Refund/chargeback/report paths for an order. Requires owning agent_id.

order_events

Lifecycle timeline — transitions only. Pair with order_track. Requires owning agent_id.

order_execute

Handoff or autonomous checkout. Handoff continue_url is a Conduit /handoff/{org_slug}/{order_id} link: open it as returned (records the open, then redirects to the merchant). Autonomous needs badge payable_now (covering mandate fits). No covering mandate, or a spent covering budget, still returns a handoff with continue_url (handoff_reason). Use idempotency_key. Prefer supply_delivery when only comparing delivery.

order_feedback

Attest delivery outcome (outcome=on_time|late|never_arrived|damaged|wrong_item). Requires owning agent_id. Can supersede a system-derived score once; a second agent attestation returns already_recorded. Poor outcomes next→order_dispute. Omit quality/carrier_rating if unknown.

order_list

List orders for an agent ({ orders }). Optional status or open_only filter.

order_track

Honest deal-type-aware status (never fabricates carrier scans). Requires owning agent_id.

order_update_status

Agent manual correction or degraded handoff recovery. note required except cancelled. Owning agent_id required.

supply

supply_delivery

Non-committing checkout probe for shipping ETA/cost. Uses agent default_destination, else linked org default address, or country override. status describes how far the merchant checkout got: ready_for_complete (priced and completable), incomplete (merchant returned partial rates, quote may firm up at checkout), requires_escalation (merchant wants a human at checkout, so this offer is handoff-only however its badge reads). needs_interaction=true means the same. None of these block a handoff; they predict whether autonomous completion can work.

supply_details

Re-reads one offer from the search cache and refreshes its badge/action against current mandate state. For most catalog offers the payload equals the object supply_search already returned, so skip this if you still hold that offer and only need its fields. Carries no shipping data: use supply_delivery for ETA and cost. Re-run supply_search if offer_not_in_cache.

supply_options

Lists the selectable options (size, color, pack) for an offer whose has_options=true, with one variant per combination. Each variant carries its OWN supply_id, price and availability: to buy a chosen option, call order_execute with that variant's supply_id, not the one you searched with. Reads the merchant storefront live, so call it only when a person is actually choosing. Returns variants_not_found when the offer is not in cache or the storefront cannot be read. A single-variant product returns options:[] variants:[].

supply_search

Multi-provider discovery (live REAL merchants by default). Returns a ranked page (default limit=30, max 100) with total/has_more/next_offset. Follow next.args (search_id+offset+limit) to page without re-fanout. Optional fetch_limit (max 300) deepens the upstream pull on new searches. Pass include_sandbox=true only to append DEMO/SANDBOX test merchants at the bottom (test_offer=true). Always pass agent_id for mandate-aware badges. Carry search_id through supply_details / order_execute / order_feedback.

payment

payment_mandate

AP2 spend mandates. action=request (needs scope) → approval_url; list (includes remaining, window_resets_at, coverage); update (mandate_id+scope); revoke (mandate_id). update NEVER approves. Widening returns an ACTIVE mandate to PENDING_HUMAN_APPROVAL; narrowing keeps whatever status it already had. monthly_cap is a rolling 30-day window from create. Same category set as a live mandate replaces it at approval and keeps this period's spend. No covering mandate at checkout is handoff, not an error.

payment_methods

List or enable agent payment methods (action=list|enable) with friendly labels. Defaults: cod + x402. invoice (B2B) is coming_soon. bank_card is handoff-only.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.aiconduit.app/mcp	streamable-http	answering	536 ms	10 min ago

Alternatives to Conduit Agentic Commerce

same job, measured the same way

FinCore Agentic Commerce

by athenalion

Agentic commerce with 58 MCP tools for product search, checkout, A2A negotiation, C-Suite analytics.

7 tools answering

MCP Gateway

by trusteed

Agentic commerce gateway: discovery, search, checkout across Shopify/Woo/Odoo/PrestaShop.

19 tools answering

AIURION Agentic 3D Printing

by aiurion

Create 3D print quotes, approved Stripe Checkout links, and track AIURION manufacturing orders.

7 tools answering

Ordercore MCP

by ordercore

Commerce backend for AI agents: catalog, prices, inventory, orders, idempotent checkout.

47 installs/wk local only

Agentmemory MCP

by agentmemory

Paid remote MCP for persistent AI agent memory, analytics, checkout, and search-readiness.

answering

Agent Checkout

by agentcheckoutapi

AI shopping gateway for product search, inventory, carts, and merchant-hosted checkout.

8 tools answering

Nexez Agentic Commerce

by nexez

Find Nexez sellers, inspect offers, and validate checkout or negotiation before buyer approval.

5 tools answering

MCP Gera Market

by geraservicesuk

E-commerce marketplace: search products, order, track shipments. 50+ countries.

24 installs/wk local only

Conduit Agentic Commerce — questions

Answers built from our own checks of this server.

What can Conduit Agentic Commerce do?

It exposes 20 tools, read directly from the server on our last check. Among them: agent_authenticate, agent_create, agent_notify, agent_organization, agent_outreach, agent_report_issue and 14 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Conduit Agentic Commerce mostly used for?

Its tools cluster around agent, order and supply. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Conduit Agentic Commerce working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 414 ms. The bar chart above shows every period we have measured.

Is Conduit Agentic Commerce still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Conduit Agentic Commerce?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Conduit Agentic Commerce need an API key?

No. Conduit Agentic Commerce completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 20 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Conduit Agentic Commerce?

It answers our handshake in 414 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.