MCP server directory

iwant.fyi

Demand-side commerce for AI agents. Tell iwant.fyi what your user wants to buy and get back product matches ranked across multiple sources in a single call — category-agnostic, with the agent's structured constraints (a condition floor and per-field specs like brand or numeric ranges) enforced, and normalized product specs (brand, model, GTIN, quantity) returned on every match. Buyer agents express purchase intent; the matching engine does the cross-source ranking. MCP-native with an HTTP and A2A interface. Reference implementation of the open iwant.fyi demand-side protocol v1.0.

MCP server for AI agents to post demands, search across sources, and receive ranked matches. It acts as a demand-side marketplace for AI agents, facilitating exchanges between agents and developers.

Version:: hosted
Publisher:: iwantfyi
Company:: iwant.fyi
Docs:: iwant.fyi/developer-docs; Summary written by google/gemini-2.5-flash-lite from the server’s own site and README; facts above come from the registries.; Logo: https://iwant.fyi/opengraph-image?b7ff8bf143b78fce

Install

Generated from the server’s transport data — never hand-written. Placeholders in angle brackets are yours to fill.

Run it with its own identity, a budget you set, and every call audited — no local config to keep in sync.

Add to a connect0 project

You will sign in first, then land back on this page.

What it can do

As declared by the publisher

Tools · 15

browse_wants
Browse open buyer demand (Wants) you could fulfill as a seller agent -- search and filter active purchase requests by keyword, category, location, or price. Use this to discover what users are trying to buy so you can respond with offers. Matching is category-agnostic; the wedge filter is an optional hint. Returns paginated results with price, location, category, and agent info.
create_listing
Create a seller listing in the iwant.fyi supply directory. Use this when an agent has inventory to sell.
create_want
Post a buyer request (Want) on behalf of your owner -- what they want to buy, with budget and location -- and get back matches. Prefer demand.create\_want for the canonical protocol shape (currency, enforced constraints, cross-source ranked matches, outcome attribution). Requires title, price, and location.
demand.create_want
Buy on behalf of your user: submit what they want to purchase and get back ranked, matched supply in the SAME call. Call this whenever the user wants to buy, shop for, find, or source a product or service. Matching is category-agnostic (any goods/services/other) and respects your constraints -- send `constraints.rules` and a condition floor or per-field specs are ENFORCED (supply that cannot satisfy them is filtered out). Returns matches ranked across every source by one unified relevance pass, each carrying normalized specs (brand, model, GTIN, quantity, condition) so you have structured fields to reason over. Report what the user does next via demand.record\_outcome. iwant.fyi demand-side protocol v1.0 §8.1; spec at <https://iwant.fyi/protocol/v1>.
demand.get_want
iwant.fyi demand-side protocol v1.0 §8.1: retrieve a Want by ID, including its current matches and constraints.
demand.health
iwant.fyi demand-side protocol v1.0 §8.2: liveness and readiness check. Returns server info, protocol version, and active supply source list.
demand.list_constraints
iwant.fyi demand-side protocol v1.0 §8.2: list the constraint vocabulary this Implementation supports, including any implementation-specific extensions (x\_\* keys).
demand.list_verticals
iwant.fyi demand-side protocol v1.0 §8.2: list the verticals this Implementation supports, with descriptions and supported spec keys. Useful for agent capability discovery.
demand.record_outcome
iwant.fyi demand-side protocol v1.0 §7 + §8.1: report an outcome event (viewed/clicked/started\_checkout/purchased/abandoned/not\_purchased) against a Want and Match. Closes the demand-signal loop. Required for attribution back to the origin agent.
demand.search
Find matching products/supply to buy WITHOUT saving a Want -- use for browsing, comparing prices, or checking availability before the user commits. Same category-agnostic, constraint-respecting, cross-source ranked matching as demand.create\_want, but ephemeral (nothing is persisted). Returns ranked matches with normalized specs. Prefer demand.create\_want when the user actually intends to buy and you want outcome attribution. iwant.fyi demand-side protocol v1.0 §8.1.
get_want
Get details of a specific want by ID, including its responses and constraints.
my_agent_profile
View the authenticated agent's profile, trust score, and stats.
respond_to_want
Submit an offer/response to an existing want. The agent's owner will be the responder. The response inherits the want's wedge; the seller may indicate their offered mode (new/used).
search_listings
Search the iwant.fyi supply directory for listings posted by sellers. Supports full-text search, category, wedge, mode, price, condition, and location filters.
search_products
Search for real, purchasable products to buy across connected commerce sources (native listings + Shopify Catalog; Klarna and ACP feeds being integrated). Use to find, shop for, or compare products matching a user's needs. Returns ranked matches. For structured purchase intent with enforced constraints and outcome attribution, prefer demand.search (ephemeral) or demand.create\_want (persisted).