Home / MCP registry index / app.aiconduit/conduit
Conduit Agentic Commerce
app.aiconduit/conduit in the official MCP registry.
Endpoint https://mcp.aiconduit.app/mcp. Source: github.com/asmodeoux/conduit.
The registry describes it as: Search multi-merchant supply, checkout, and track orders via MCP.
We read its 25 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
agent_create agent_authenticate agent_update agent_organization agent_notify agent_outreach agent_report_issue payment_methods payment_mandate supply_search supply_details supply_options supply_delivery order_execute order_list order_track order_events order_update_status order_dispute order_feedback inventory_levels inventory_replenishment inventory_suppliers supply_availability inventory_purchase_order
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-aiconduit-conduit)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.