/vendor/uniswap/AgentRouting.json or
/vendor/uniswap/AgentContext.json directly.
app.uniswap.org
Overview
Does app.uniswap.org support MCP?
No confirmed MCP support was found for app.uniswap.org as of 2026-06-28.
What agentic protocols does app.uniswap.org support?
As of 2026-06-28, app.uniswap.org has confirmed support for MPP and proprietary.
Is app.uniswap.org's API publicly accessible or partner-gated?
Open.
Does app.uniswap.org explicitly prohibit automated access?
Yes. app.uniswap.org's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is app.uniswap.org agent-ready?
Partial. app.uniswap.org supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
No evidence found that Uniswap (app.uniswap.org) is an A2A launch partner or has implemented the Agent2Agent protocol. Named launch partners include Atlassian, Box, Cohere, Langchain, MongoDB, PayPal, Salesforce, SAP, ServiceNow, Intuit, and Workday — all enterprise SaaS vendors with no overlap with Uniswap's DeFi/DEX domain. Uniswap was not found in any A2A partner list or announcement.
ACP (Agentic Commerce Protocol) is a commerce/checkout standard co-developed by Stripe and OpenAI; confirmed launch partners include URBN brands, Coach, Kate Spade, Revolve, and Ashley Furniture — all traditional retail merchants. Uniswap (app.uniswap.org) is a decentralized cryptocurrency exchange, and no evidence was found linking it to ACP participation, a product feed integration with ChatGPT, or any Stripe-mediated checkout surface. The protocol requires a Stripe payment integration as a prerequisite, which is structurally incompatible with Uniswap's on-chain, non-custodial trading model.
AP2 launch partners include Adyen, American Express, Coinbase, Etsy, Intuit, Mastercard, PayPal, Revolut, and 50+ other organizations — all traditional fintech, payments, and commerce vendors. No evidence places app.uniswap.org (Uniswap Labs) among any AP2 partner or adopter lists. The distinction between confirmed_absent and not_found applies here: Uniswap has issued no AP2-specific statement or deprecation notice, so not_found is the correct status rather than confirmed_absent.
No official MCP server published by Uniswap Labs targeting app.uniswap.org was found. The Uniswap/ai-toolkit and Uniswap/uniswap-ai GitHub repositories are Claude Code workflow toolkits (skills, plugins, slash commands) rather than MCP servers exposing Uniswap's DEX data or trading API. Third-party community MCP servers exist (e.g., kukapay/uniswap-pools-mcp on mcpservers.org, a 'Uniswap Trader MCP' on flowhunt.io) but these are not sanctioned by Uniswap Labs. The note 'Get MCP on Uniswap' appearing on app.uniswap.org token pages refers to an ERC-20 token named 'MCP,' not the Model Context Protocol.
Uniswap v2/v3/v4 deployed on Tempo (MPP's settlement chain); Uniswap AI skill (`pay-with-any-token`) enables agents to swap into any token required for MPP 402-challenge settlement — acting as a liquidity/swap layer within MPP flows, not as an MPP endpoint that directly accepts payments
Uniswap Labs confirmed deployment of v2, v3, and v4 on Tempo (the MPP settlement chain co-authored by Stripe and Paradigm) and published a `pay-with-any-token` AI skill (`npx skills add uniswap/uniswap-ai --skill pay-with-any-token`) specifically to help agents satisfy MPP 402 payment challenges. Evidence sourced from Uniswap's own blog (https://blog.uniswap.org/uniswap-is-live-on-tempo) and official X announcement. Uniswap's role in MPP is as an on-chain liquidity provider/swap layer, not a merchant or payment-accepting endpoint.
No evidence of app.uniswap.org (a decentralized crypto exchange) appearing in any NLWeb launch partner lists or adopter profiles. Confirmed early NLWeb adopters at Build 2025 include TripAdvisor, Shopify, Eventbrite, Hearst, O'Reilly, and Qdrant — no travel or DeFi/crypto vendors are listed. No vendor-specific NLWeb documentation, /ask or /mcp endpoint, or adoption announcement was found for Uniswap.
Uniswap (app.uniswap.org) is a decentralized crypto exchange focused on token swaps via AMMs on EVM-compatible chains and Solana. UCP (Universal Commerce Protocol) is a Google/Shopify-led commerce checkout protocol for retail AI agents. No evidence of any Uniswap adoption, announcement, or integration of UCP was found across uniswap.org, docs.uniswap.org, or blog.uniswap.org. The protocol domains are entirely non-overlapping: UCP targets retail e-commerce merchants, not DeFi trading venues.
WebMCP entered a Chrome origin trial in Chrome 149 (2026); known adopters and discussion participants include Google, Cloudflare (Browser Run), and developer-community early adopters, but no evidence found that app.uniswap.org has enrolled in the origin trial or implemented WebMCP tools. Uniswap's developer documentation covers its own AMM protocol APIs with no mention of WebMCP. Status is not_found rather than confirmed_absent because Uniswap has made no vendor-specific statement on the matter.
No evidence that app.uniswap.org has adopted or been announced as a partner for the x402 protocol. The Coinbase x402 launch materials name Cloudflare and Circle (USDC) as key partners; Uniswap does not appear. Uniswap's own published developer resources focus on UniswapX, liquidity aggregation, and onchain swap routing — none of which reference x402 or HTTP 402 payment settlement.
No evidence of Uniswap (app.uniswap.org) having built or published an app on OpenAI's ChatGPT Apps platform using the Apps SDK. Uniswap's AI-related developer work centers on coding-agent plugins and skills (the open-source uniswap-ai GitHub repository), which target Claude Code, generic skills CLIs, and similar developer tools — not the ChatGPT Apps platform specifically. The OpenAI ChatGPT Apps directory (chatgpt.com/apps) was not confirmed to contain any Uniswap listing.
Token swapping (cross-chain bridge, wrap/unwrap) and liquidity provisioning (create/manage positions in Uniswap v3/v4 pools); two documented capability groups unified under one API key and base URL but covering distinct workflows
Uniswap Labs operates a documented proprietary REST API (https://api-docs.uniswap.org/) covering two main feature groups — swapping (token trades, cross-chain bridging, wrap/unwrap) and liquidity provisioning (pool creation and position management). Access requires a self-serve API key issued via the Developer Portal. The API abstracts on-chain smart-contract complexity and exposes Uniswap's own routing/intent-based systems as callable HTTP endpoints, placing it squarely in the proprietary category rather than any named standard.
No evidence of llms.txt, agents.md, /.well-known/agent, or similar self-declaration files hosted at app.uniswap.org (the DEX trading frontend). Uniswap does publish llms.txt and llms-full.txt, but these are documented at docs.uniswap.org/llms/overview and docs.uniswap.org/ai-coding/overview — a different subdomain serving developer documentation, not the app domain under research.
Summary
Has agent interface: partial
Integrate via the documented Uniswap Labs REST API (https://api-docs.uniswap.org/) using a self-serve API key from the Developer Portal for swap and liquidity operations; monitor Uniswap's blog and GitHub (uniswap-ai repository) for any official MCP server release or expanded agent-interface announcements, particularly given the confirmed MPP integration on Tempo.
AgentContext
Verified discrepancies
Vendor claim: Uniswap Labs presents itself as a software/interface developer and protocol facilitator, not as a regulated exchange, broker-dealer, or merchant of record. Its terms of service disclaim that Uniswap Labs is a party to any trade, that trades occur peer-to-peer via smart contracts, and that users bear all counterparty and transaction risk.
What actually happens: The U.S. CFTC determined that Universal Navigation Inc. (d/b/a Uniswap Labs) — the entity behind app.uniswap.org — was in fact the offeror of illegal leveraged and margined digital asset transactions to retail users, making it the legally accountable party for those offerings despite its disclaimers. The CFTC issued a cease-and-desist order and $175,000 civil monetary penalty against Uniswap Labs in September 2024, establishing that the operator of the interface bore regulatory liability for transactions conducted through it. This directly contradicts the platform's framing that it is a neutral tool with no role as a transactional counterparty.
Agent guidance: An agent completing a leveraged or margined transaction on app.uniswap.org should not treat the trade as a purely peer-to-peer, counterparty-free interaction. The CFTC has established that Uniswap Labs bears legal accountability for the platform's offerings. Agents should flag to users that (1) Uniswap Labs — not an anonymous smart contract — is the legally identified responsible party for interface-facilitated trades, (2) no conventional dispute, refund, or consumer-protection mechanism exists, and (3) any leveraged/margined token products on the interface have been subject to regulatory enforcement. Users should verify current product availability and applicable terms before executing such trades.
- The CFTC's official press release confirms it issued a cease-and-desist order and $175,000 civil monetary penalty against Universal Navigation Inc. d/b/a Uniswap Labs for offering illegal leveraged and margined commodity transactions to retail users who were not eligible contract participants.
- Commissioner Pham's dissent acknowledges the core legal question: whether Uniswap Labs, as developer and operator of the interface, bears regulatory liability for transactions that users believed were peer-to-peer smart contract interactions.
Vendor claim: Uniswap Labs' Terms of Service govern use of their interfaces and create a legally binding agreement with users, implying a structured contractual relationship and user protections under that agreement.
What actually happens: As a non-custodial, decentralized exchange protocol, Uniswap offers no cancellation, no refund mechanism, and no recourse for lost or misdirected funds. Transactions executed on-chain are irreversible by design. The Terms of Service explicitly disclaim any liability, meaning policies users might expect from a traditional financial platform (e.g., dispute resolution, transaction reversal, refund for errors) do not exist in practice and cannot be enforced against Uniswap Labs. Tokens sent incorrectly to a Uniswap smart contract (e.g., via direct transfer rather than the supported approve/transferFrom method) are permanently and irrecoverably lost with no remediation pathway.
Agent guidance: An agent must not assume any transaction on Uniswap can be cancelled, reversed, or refunded after submission. Before initiating any swap or liquidity operation, the agent must confirm the exact token contract addresses, amounts, and method (approve/transferFrom only — never direct transfer), because errors result in permanent, unrecoverable loss with no policy-based remedy available from Uniswap Labs.
- Uniswap Labs Terms of Service govern use of the interface but include broad disclaimers of liability and no refund or cancellation provisions, meaning there is no enforceable customer-facing recourse for transaction errors.
- A documented GitHub issue on the Uniswap v3-core repository confirms that tokens deposited by direct transfer (a common user error) are permanently lost in the smart contract with no refund mechanism, and only a future protocol redesign could address this.
Vendor claim: The Uniswap Protocol is described as a 'self-executing, permissionless, decentralized series of smart contracts' implying any token can be swapped. The app.uniswap.org interface does not prominently surface, prior to token selection, which specific tokens or geographies are blocked by Uniswap Labs at the application layer.
What actually happens: Uniswap Labs silently blocks a defined list of ERC-20 tokens from being traded through app.uniswap.org (the Labs-maintained front-end), even though those tokens are fully accessible on the underlying permissionless protocol. Additionally, the app blocks users from certain jurisdictions via IP-based geofencing, and third-party on-ramp services (MoonPay, Transak) embedded in the app impose KYC requirements that are not disclosed on the main swap interface. An agent navigating the app to complete a swap may reach a dead end mid-transaction for any of these reasons without prior warning.
Agent guidance: Before initiating any swap or on-ramp transaction via app.uniswap.org, an agent must: (1) programmatically verify the target token contract address against the Uniswap Labs unsupported token list, (2) confirm the user's jurisdiction is not geo-blocked by the Labs front-end, and (3) if using an embedded on-ramp (MoonPay/Transak), surface KYC requirements to the user before starting the flow — do not assume the swap will be completable based solely on the protocol's permissionless nature.
- Uniswap Labs' own support article confirms that certain ERC-20 token contracts are blocked from the Labs-maintained front-end products, while clarifying the underlying protocol itself remains permissionless and open.
- Uniswap Labs' asset blocking policy article explains the distinction between the permissionless protocol and the Labs front-end, and states that Labs maintains discretion over which assets appear in its interface.
- Third-party reporting documents that app.uniswap.org applies geographic IP-based restrictions in certain countries, and that on-ramp services embedded in the app require KYC not disclosed on the main swap interface.
Human handoff required for
Escalate to a human before executing any leveraged or margined token transaction on app.uniswap.org, because the CFTC has formally found Uniswap Labs legally liable for such offerings despite platform disclaimers — the agent cannot treat these as purely peer-to-peer, counterparty-free trades, and a human must confirm regulatory status and current product availability before proceeding.
Stop and escalate to a human if an on-chain transaction has been submitted and the user believes it was sent in error (wrong address, wrong token, wrong amount), because Uniswap's non-custodial architecture makes all executed transactions irreversible with no cancellation, refund, or remediation pathway available from Uniswap Labs under any circumstances.
Escalate to a human if a swap attempt fails or is silently blocked mid-transaction for a specific token or user jurisdiction, because Uniswap Labs maintains an undisclosed front-end token blocklist and IP-based geofencing that prevent certain swaps from completing even though the underlying protocol is permissionless — the agent cannot determine completability from protocol access alone.
Escalate to a human before initiating any fiat on-ramp flow via embedded third-party services (MoonPay or Transak) on app.uniswap.org, because these services impose KYC identity verification requirements that are not disclosed on the main swap interface — the agent must surface these requirements to the user and obtain confirmation before starting the flow, as failure mid-process cannot be undone.
Five categories were checked for app.uniswap.org (uniswap). Pricing discrepancy: searches found that the previously charged interface fee was removed as of December 2025 and that protocol fees are disclosed in the UI pre-confirmation; no hidden-fee finding met the inclusion bar. Availability discrepancy: slippage-related quote drift was found to be a disclosed, structurally inherent property of AMMs, not a vendor misrepresentation; no finding met the bar. Identity discrepancy: a finding was confirmed — the CFTC's September 2024 enforcement action against Uniswap Labs directly contradicts the platform's self-presentation as a neutral, counterparty-free interface. Policy discrepancy: a finding was confirmed — the platform's Terms of Service imply a contractual relationship, but all transactions are irreversible on-chain and Uniswap Labs offers no refund, cancellation, or dispute mechanism. Undisclosed constraint discrepancy: a finding was confirmed — Uniswap Labs maintains an undisclosed front-end token blocklist, IP-based geofencing, and KYC requirements on embedded on-ramp services that are not surfaced on the main swap interface. All five categories had substantive scan summaries available; no categories were blocked or missing.