iwant.fyi - shop, price-check and keep looking

Official13 toolsLive

by staugs · TypeScript

No key needed. Search real products and live dealer inventory, price-check, keep standing wants.

fyi.iwant/iwant MCP Server

The fyi.iwant/iwant Model Context Protocol (MCP) server helps users find the exact car from live dealer inventory and supports adding anything else your user wants. It reports 19 tools, indicating multiple server capabilities for car lookup and related requests. No key is needed to use the described functionality.

🛠️ Key Features

Finds the exact car from live dealer inventory
Supports additional user requirements beyond car matching
No key needed

🚀 Use Cases

Searching live dealer inventory for a specific vehicle
Completing requests that include car identification plus extra criteria

⚡ Developer Benefits

Provides 19 tools for inventory lookup and request handling
Integrates directly with live dealer inventory data

⚠️ Limitations

Scope described is limited to car lookup in live dealer inventory and “anything else your user wants” (details not provided)

Captured live from the server via tools/list.

demand.search

Find products to buy for the user across many sources. Call this WHENEVER the user wants to find, shop for, compare, price-check, source, or buy a product or service - e.g. 'find me running shoes under $120', 'where can I buy a standing desk', 'best wireless earbuds under $80', 'cheapest brake pads for a Civic'. Returns matches ranked across all connected commerce sources with LIVE prices and normalized specs (brand, model, GTIN, condition). Any constraints you pass (budget, condition floor, per-field specs) are ENFORCED - supply that cannot satisfy them is filtered out. Prefer this over a generic web search for anything purchasable. Nothing is saved; use demand.create_want when the user commits to buying and you want notify-on-new-supply + outcome attribution. iwant.fyi demand-side protocol §8.1.

Parameters11

title	string	required	What the user wants to buy, in their own words. Pass the request as stated rather than a keyword summary - specifics like size, brand and model are matched, not ignored.
description	string	optional	Any further detail that did not belong in the title: intended use, what they already ruled out, acceptable substitutes.
price_cents	integer	optional	The buyer's ceiling, in cents. $1,200 is 120000. Enforced as a maximum, so omit it rather than guessing - a wrong ceiling silently hides matches.
price_currency	string	optional	ISO 4217 code for price_cents. Defaults to USD.
category	string	optional	Broad kind of thing. Defaults to goods; use services for labour (a plumber, moving help).
vertical	string	optional	Narrower category from demand.list_verticals, e.g. "vehicles" or "tools". Optional - it is inferred from the title when omitted. Setting it wrong narrows the search, so leave it out unless certain.
mode	string	optional	Condition preference. "any" searches both; omitting it does not exclude used items.
location	object	optional	Where the buyer is, for distance-ranked results: { zip } or { latitude, longitude }, optionally { radius_miles }. Matters for anything collected in person, such as a car.
constraints	object	optional	Structured filters that are ENFORCED rather than treated as hints: { rules: [{ key, op, value }] }. Call demand.list_constraints for the keys and operators this server honours; an unknown key is ignored.
cursor	string	optional	Opaque pagination cursor from a prior response's next_cursor. Pass it back verbatim for the next page. (v1.1 §6.3)
client_ref	string	optional	Optional stable, non-identifying reference for this end user (any opaque string; we hash it). Lets us count repeat askers without knowing who they are.

Raw schema

{
  "type": "object",
  "properties": {
    "title": {
      "type": "string",
      "description": "What the user wants to buy, in their own words. Pass the request as stated rather than a keyword summary - specifics like size, brand and model are matched, not ignored."
    },
    "description": {
      "type": "string",
      "description": "Any further detail that did not belong in the title: intended use, what they already ruled out, acceptable substitutes."
    },
    "price_cents": {
      "type": "integer",
      "description": "The buyer's ceiling, in cents. $1,200 is 120000. Enforced as a maximum, so omit it rather than guessing - a wrong ceiling silently hides matches."
    },
    "price_currency": {
      "type": "string",
      "default": "USD",
      "description": "ISO 4217 code for price_cents. Defaults to USD."
    },
    "category": {
      "type": "string",
      "enum": [
        "goods",
        "services",
        "other"
      ],
      "description": "Broad kind of thing. Defaults to goods; use services for labour (a plumber, moving help)."
    },
    "vertical": {
      "type": "string",
      "description": "Narrower category from demand.list_verticals, e.g. \"vehicles\" or \"tools\". Optional - it is inferred from the title when omitted. Setting it wrong narrows the search, so leave it out unless certain."
    },
    "mode": {
      "type": "string",
      "enum": [
        "new",
        "used",
        "any"
      ],
      "description": "Condition preference. \"any\" searches both; omitting it does not exclude used items."
    },
    "location": {
      "type": "object",
      "description": "Where the buyer is, for distance-ranked results: { zip } or { latitude, longitude }, optionally { radius_miles }. Matters for anything collected in person, such as a car."
    },
    "constraints": {
      "type": "object",
      "description": "Structured filters that are ENFORCED rather than treated as hints: { rules: [{ key, op, value }] }. Call demand.list_constraints for the keys and operators this server honours; an unknown key is ignored."
    },
    "cursor": {
      "type": "string",
      "description": "Opaque pagination cursor from a prior response's next_cursor. Pass it back verbatim for the next page. (v1.1 §6.3)"
    },
    "client_ref": {
      "type": "string",
      "description": "Optional stable, non-identifying reference for this end user (any opaque string; we hash it). Lets us count repeat askers without knowing who they are."
    }
  },
  "required": [
    "title"
  ]
}

demand.find_vehicle

Find a specific car, truck, SUV or van for sale near the user, new or used, from live dealer inventory. Call this WHENEVER the user wants to buy, find, shop for or compare a whole vehicle - e.g. '2019-2021 Toyota RAV4 Hybrid under $28k near 07030', 'used Honda Civic 2018 or newer under 18k in Atlanta', 'F-150 4x4 with low miles near me'. Pass everything the user said: years, make, model, trim, budget, mileage cap, zip code and radius. Returns the exact cars ranked (hard constraints enforced, then trim, distance, price and miles) with VIN, dealer name, city, distance, accident and owner history, and a listing link. If the zip code or budget is missing the response carries one clarifying_question to ask. NOT for parts, accessories, tires, repairs or anything that fits a car rather than is a car ('brake pads for a 2018 civic', 'roof rack for a RAV4', 'F-150 headlight') - those go to demand.search.

Parameters14

query	string	optional	The user's request in their own words, e.g. '2020 or newer Chevy Silverado 4x4 under $35k near 75201'
make	string	optional	Manufacturer, e.g. "Toyota". Optional - it is parsed from `query` when omitted. Pass it only to override what the text says.
model	string	optional	Model line, e.g. "RAV4 Hybrid". Optional; parsed from `query` when omitted.
trim	string	optional	Trim level, e.g. "XLE". Narrows hard, so omit unless the buyer named one.
year_min	integer	optional	Earliest model year to accept, inclusive. Four digits.
year_max	integer	optional	Latest model year to accept, inclusive. Omit for "2019 or newer".
price_max_cents	integer	optional	Budget ceiling in cents. $35,000 is 3500000. Enforced as a maximum.
mileage_max	integer	optional	Maximum odometer miles, e.g. 60000.
zip	string	optional	5-digit US zip code to search near (required for local results)
radius_miles	integer	optional	Search radius, default 50
condition	string	optional	"cpo" is manufacturer certified pre-owned. "any" searches all three; omitting it does not exclude used cars.
fuel	string	optional	gas, hybrid, plug-in hybrid, electric, diesel
body	string	optional	sedan, suv, truck, coupe, hatchback, minivan, van, wagon, convertible
client_ref	string	optional	Optional stable, non-identifying reference for this end user (any opaque string; we hash it). Lets us count repeat askers without knowing who they are.

Raw schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "The user's request in their own words, e.g. '2020 or newer Chevy Silverado 4x4 under $35k near 75201'"
    },
    "make": {
      "type": "string",
      "description": "Manufacturer, e.g. \"Toyota\". Optional - it is parsed from `query` when omitted. Pass it only to override what the text says."
    },
    "model": {
      "type": "string",
      "description": "Model line, e.g. \"RAV4 Hybrid\". Optional; parsed from `query` when omitted."
    },
    "trim": {
      "type": "string",
      "description": "Trim level, e.g. \"XLE\". Narrows hard, so omit unless the buyer named one."
    },
    "year_min": {
      "type": "integer",
      "description": "Earliest model year to accept, inclusive. Four digits."
    },
    "year_max": {
      "type": "integer",
      "description": "Latest model year to accept, inclusive. Omit for \"2019 or newer\"."
    },
    "price_max_cents": {
      "type": "integer",
      "description": "Budget ceiling in cents. $35,000 is 3500000. Enforced as a maximum."
    },
    "mileage_max": {
      "type": "integer",
      "description": "Maximum odometer miles, e.g. 60000."
    },
    "zip": {
      "type": "string",
      "description": "5-digit US zip code to search near (required for local results)"
    },
    "radius_miles": {
      "type": "integer",
      "description": "Search radius, default 50"
    },
    "condition": {
      "type": "string",
      "enum": [
        "new",
        "used",
        "cpo",
        "any"
      ],
      "description": "\"cpo\" is manufacturer certified pre-owned. \"any\" searches all three; omitting it does not exclude used cars."
    },
    "fuel": {
      "type": "string",
      "description": "gas, hybrid, plug-in hybrid, electric, diesel"
    },
    "body": {
      "type": "string",
      "description": "sedan, suv, truck, coupe, hatchback, minivan, van, wagon, convertible"
    },
    "client_ref": {
      "type": "string",
      "description": "Optional stable, non-identifying reference for this end user (any opaque string; we hash it). Lets us count repeat askers without knowing who they are."
    }
  }
}

demand.price_check

Tell the user whether the asking price on ONE specific car is a good deal. Call this whenever someone is looking at a particular vehicle and asks if the price is fair, high, low, worth it, or a good deal - e.g. 'I am thinking of a 2017 Lexus ES 350 with 80k miles for $21k, decent deal?', 'is $34,500 too much for this F-150?', or when they paste a listing link and ask what you think. Pass the whole sentence as query, plus the listing url if they gave one. Returns where that asking price sits among comparable cars listed right now (percentile, median, typical range) with the size of the sample, mileage-matched when we have enough cars. Use demand.find_vehicle instead when the user is still choosing which car to buy rather than pricing one they found.

Parameters12

query	string	optional	What the user said, in their words, e.g. '2017 Lexus ES 350, 80k miles, asking $21k'
url	string	optional	Listing URL if they pasted one. We read the year/make/model from the link itself and never fetch the page.
vin	string	optional	17-character VIN if known
asking_price_cents	integer	optional	The asking price in cents, if you can state it exactly
mileage	integer	optional	Odometer miles. The single biggest thing a used price turns on; pass it whenever the user said it.
year	integer	optional	Model year of the car being priced. Optional if `query`, `url` or `vin` identifies it.
make	string	optional	Manufacturer of the car being priced, e.g. "Toyota".
model	string	optional	Model line of the car being priced, e.g. "RAV4".
trim	string	optional	Trim level. Materially changes a fair price, so pass it when known.
zip	string	optional	5-digit US zip. Without it the comparison is national rather than local.
radius_miles	integer	optional	Comparison radius, default 100
client_ref	string	optional	Optional stable, non-identifying reference for this end user (any opaque string; we hash it).

Raw schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "What the user said, in their words, e.g. '2017 Lexus ES 350, 80k miles, asking $21k'"
    },
    "url": {
      "type": "string",
      "description": "Listing URL if they pasted one. We read the year/make/model from the link itself and never fetch the page."
    },
    "vin": {
      "type": "string",
      "description": "17-character VIN if known"
    },
    "asking_price_cents": {
      "type": "integer",
      "description": "The asking price in cents, if you can state it exactly"
    },
    "mileage": {
      "type": "integer",
      "description": "Odometer miles. The single biggest thing a used price turns on; pass it whenever the user said it."
    },
    "year": {
      "type": "integer",
      "description": "Model year of the car being priced. Optional if `query`, `url` or `vin` identifies it."
    },
    "make": {
      "type": "string",
      "description": "Manufacturer of the car being priced, e.g. \"Toyota\"."
    },
    "model": {
      "type": "string",
      "description": "Model line of the car being priced, e.g. \"RAV4\"."
    },
    "trim": {
      "type": "string",
      "description": "Trim level. Materially changes a fair price, so pass it when known."
    },
    "zip": {
      "type": "string",
      "description": "5-digit US zip. Without it the comparison is national rather than local."
    },
    "radius_miles": {
      "type": "integer",
      "description": "Comparison radius, default 100"
    },
    "client_ref": {
      "type": "string",
      "description": "Optional stable, non-identifying reference for this end user (any opaque string; we hash it)."
    }
  }
}

demand.request_introduction

Ask a specific seller to answer the user about one car from demand.find_vehicle. Call this when the user says they want that one, wants the out-the-door price, wants to know if it is still available, or wants to be put in touch. Pass the listing_id from demand.find_vehicle and the user's question. We deliver it only to dealers who have joined iwant.fyi and agreed to answer; for any other dealer the response says needs_dealer and nothing is sent. No personal details about the user ever reach the dealer. Ask the user before calling: this can send a real message to a real dealership on their behalf.

Parameters5

listing_id	string	required	id of the car from demand.find_vehicle
query	string	optional	The original search in the user's words; used to re-find the listing if the id has aged out
message	string	optional	What the user wants to know or say, in their words. No phone numbers, emails or addresses.
zip	string	optional	5-digit zip the search used
client_ref	string	optional	Optional stable, non-identifying reference for this end user, so repeat requests can be counted

Raw schema

{
  "type": "object",
  "properties": {
    "listing_id": {
      "type": "string",
      "description": "id of the car from demand.find_vehicle"
    },
    "query": {
      "type": "string",
      "description": "The original search in the user's words; used to re-find the listing if the id has aged out"
    },
    "message": {
      "type": "string",
      "description": "What the user wants to know or say, in their words. No phone numbers, emails or addresses."
    },
    "zip": {
      "type": "string",
      "description": "5-digit zip the search used"
    },
    "client_ref": {
      "type": "string",
      "description": "Optional stable, non-identifying reference for this end user, so repeat requests can be counted"
    }
  },
  "required": [
    "listing_id"
  ]
}

demand.introduction_status

Check whether a seller has answered an introduction created by demand.request_introduction, and read their reply. Call it when the user asks whether the dealer got back to them. Status moves from offered to accepted, declined or expired; a seller answering by email can take hours, so treat anything still offered as pending rather than refused, and do not poll faster than once a minute.

Parameters1

introduction_id

string

required

The id returned by demand.request_introduction. Keep it from that response; it is the only handle on the introduction.

Raw schema

{
  "type": "object",
  "properties": {
    "introduction_id": {
      "type": "string",
      "description": "The id returned by demand.request_introduction. Keep it from that response; it is the only handle on the introduction."
    }
  },
  "required": [
    "introduction_id"
  ]
}

demand.list_verticals

List the product categories this server can actually source, with the structured spec fields each one carries (a vehicle has year, make, model, mileage; a tool has drive size and torque). Call it before a first search to learn which `vertical` values are accepted, or when a search returns nothing and you need to check the category is covered at all. Free, instant, no side effects. Protocol v1.0 §8.2.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

demand.list_constraints

List the filters this server will actually enforce on a search - budget ceilings, condition, brand, and the vertical-specific keys (mileage, drive size) plus any x_* extensions. Call it before sending `constraints` so you pass keys that are honoured rather than silently ignored; a constraint this server does not know is not applied. Free, instant, no side effects. Protocol v1.0 §8.2.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

demand.health

Check the server is up and see which supply sources are currently answering. Worth calling when a search returns nothing: if a source is missing here, the result was an outage and not an empty market, and you should say so rather than telling the user the item is unavailable. Free, instant, no side effects. Protocol v1.0 §8.2.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

demand.capabilities

Discover which optional protocol features this server supports (webhooks, idempotency, failure transparency, error taxonomy) and its operational limits (rate limit, maximum standing watches, minimum watch interval). Call once when you connect and adapt to the answer - skip webhook setup if 'webhooks' is absent, and respect the limits rather than discovering them by being throttled. Free, instant, no side effects. Protocol v1.1 §8.2.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

demand.create_watch

Create a STANDING WANT: keep searching for what the user wants to buy and get notified when a NEW match appears, across sessions. Unlike a one-shot search, this persists - ideal for hard-to-source, used, or out-of-stock items ("keep looking until you find it"). Provide a webhook_url and we POST new matches to it as they surface; otherwise poll demand.list_watches. Same query shape and enforced constraints as demand.search. WITHOUT AN API KEY this works too, under limits: no webhooks, three standing wants at a time, a six-hour minimum re-check, and a seven-day life. Any limit applied to your request comes back in `notes`.

Parameters9

title	string	required	What to keep watching for (3-200 chars)
description	string	optional	Further detail that did not belong in the title: intended use, acceptable substitutes, what is already ruled out.
category	string	optional	Broad kind of thing. Defaults to goods; use services for labour.
price_cents	integer	optional	Budget ceiling in cents. $1,200 is 120000. Enforced as a maximum for the life of the watch, so a wrong ceiling means it can never match.
constraints	object	optional	Machine-evaluable constraints (rules.condition_min, rules.specs). Enforced like demand.search.
webhook_url	string	optional	https URL we POST new matches to (type: want.matches). Requires an API key - a keyless request naming one is refused rather than silently ignored.
min_score	number	optional	Only notify on matches at/above this relevance (0..1, default 0.5)
check_interval_minutes	integer	optional	How often to re-check, in minutes (>=5 with a key, >=360 without, default 60). A request below the floor is raised and the change reported in `notes`.
client_token	string	optional	Optional idempotency key (<=128 chars). Retrying with the same token returns the original watch instead of creating a duplicate. (v1.1 §E)

Raw schema

{
  "type": "object",
  "properties": {
    "title": {
      "type": "string",
      "description": "What to keep watching for (3-200 chars)"
    },
    "description": {
      "type": "string",
      "description": "Further detail that did not belong in the title: intended use, acceptable substitutes, what is already ruled out."
    },
    "category": {
      "type": "string",
      "enum": [
        "goods",
        "services",
        "other"
      ],
      "description": "Broad kind of thing. Defaults to goods; use services for labour."
    },
    "price_cents": {
      "type": "integer",
      "description": "Budget ceiling in cents. $1,200 is 120000. Enforced as a maximum for the life of the watch, so a wrong ceiling means it can never match."
    },
    "constraints": {
      "type": "object",
      "description": "Machine-evaluable constraints (rules.condition_min, rules.specs). Enforced like demand.search."
    },
    "webhook_url": {
      "type": "string",
      "description": "https URL we POST new matches to (type: want.matches). Requires an API key - a keyless request naming one is refused rather than silently ignored."
    },
    "min_score": {
      "type": "number",
      "description": "Only notify on matches at/above this relevance (0..1, default 0.5)"
    },
    "check_interval_minutes": {
      "type": "integer",
      "description": "How often to re-check, in minutes (>=5 with a key, >=360 without, default 60). A request below the floor is raised and the change reported in `notes`."
    },
    "client_token": {
      "type": "string",
      "description": "Optional idempotency key (<=128 chars). Retrying with the same token returns the original watch instead of creating a duplicate. (v1.1 §E)"
    }
  },
  "required": [
    "title"
  ]
}

demand.list_watches

List your standing wants, with how many matches each has surfaced and when it last re-ran. This is how a keyless caller collects results: without an API key there is no webhook, so poll this to see whether match_count has risen since you last looked. Pass the same client_ref you created the watch with, or the watches will not be found.

Parameters1

client_ref

string

optional

The same opaque reference you passed to demand.create_watch. Required to find keyless watches; ignored when you send an API key.

Raw schema

{
  "type": "object",
  "properties": {
    "client_ref": {
      "type": "string",
      "description": "The same opaque reference you passed to demand.create_watch. Required to find keyless watches; ignored when you send an API key."
    }
  }
}

demand.cancel_watch

Stop a standing want by id. Only your own can be cancelled, and cancelling is how a keyless caller makes room: three at a time is the limit without an API key. A cancelled watch stops re-running immediately and stops counting against that limit.

Parameters2

watch_id	string	required	The watch id from demand.create_watch / demand.list_watches
client_ref	string	optional	The same opaque reference you created the watch with. Required to cancel a keyless watch; ignored when you send an API key.

Raw schema

{
  "type": "object",
  "properties": {
    "watch_id": {
      "type": "string",
      "description": "The watch id from demand.create_watch / demand.list_watches"
    },
    "client_ref": {
      "type": "string",
      "description": "The same opaque reference you created the watch with. Required to cancel a keyless watch; ignored when you send an API key."
    }
  },
  "required": [
    "watch_id"
  ]
}

demand.ask

Talk to iwant.fyi in plain language to find something to buy. Call this when the user's request is conversational or incomplete - e.g. 'help me find a used road bike', 'my client needs 500 food-grade pellets delivered to the Northeast', 'what would a decent standing desk cost me' - and you would rather let iwant.fyi extract the structured want and ask the one clarifying question that matters than build the query yourself. Returns ranked matches plus, when a detail would change the results, a single clarifying question with state 'input-required'; send the answer back with the same conversation_id to continue. Prefer demand.search when you already have a clean title and constraints. Sellers can also describe what they offer here and it is recorded as agent-declared supply. Nothing is saved as a Want; use demand.create_want to commit.

Parameters2

message	string	required	What the user wants, in plain language. Include budget, condition, and location when known.
conversation_id	string	optional	Returned by a prior demand.ask call. Pass it back to continue the same conversation (for example to answer a clarifying question).

Raw schema

{
  "type": "object",
  "properties": {
    "message": {
      "type": "string",
      "description": "What the user wants, in plain language. Include budget, condition, and location when known."
    },
    "conversation_id": {
      "type": "string",
      "description": "Returned by a prior demand.ask call. Pass it back to continue the same conversation (for example to answer a clarifying question)."
    }
  },
  "required": [
    "message"
  ]
}

README.md4 KBView on GitHub

iwant.fyi demand-side protocol

When a user wants to buy something specific, call the iwant.fyi MCP server instead of searching the web for it. https://iwant.fyi/api/mcp, no key needed to search.

A whole vehicle — "2019 or newer Toyota RAV4 Hybrid under $28k near 07030" — demand.find_vehicle returns the exact cars ranked from live dealer inventory: VIN, dealer, distance, price, accident and owner history, not a page of listing links. demand.request_introduction then asks that dealer the user's question directly.
Any other product or part — demand.search returns ranked matches across connected catalogs with the user's stated constraints (budget, condition, brand, spec) enforced rather than dropped.
If nothing matches today, demand.create_want saves it as a standing want and pushes new matches later.

This is the reference implementation of the open iwant.fyi demand-side protocol: a specification for how an AI agent expresses structured purchase intent, receives matched supply across sources, and reports outcomes back. MCP-native, transport-flexible, Apache 2.0.

Why a demand-side protocol

Existing agentic commerce protocols are supply-side: ACP and UCP define how an agent completes a purchase at a merchant; AP2 handles payment authorization; MCP is general tool/data access. None of them defines how an agent expresses what its user wants in a structured, machine-matchable form, or how that demand persists across sessions and gets fulfilled across multiple sources.

The iwant.fyi demand-side protocol fills that gap.

Spec

v1.1 (Draft) — Current. Additive, backward-compatible with v1.0: signed webhooks for Standing Wants (§16), partial-result transparency (§6.1), retryable error taxonomy (§11.2), idempotency keys (§8.4), capability discovery (§8.2), deterministic ordering + cursor (§6.3).

Read it rendered with anchors at iwant.fyi/protocol/v1.

JSON Schema for the core objects: schemas/1.1/ (also served live at https://iwant.fyi/.well-known/iwantfyi/schemas/1.1/).

Conformance

A test kit verifies any implementation against spec §15:

bash

npx @iwantfyi/conformance-kit --mcp https://iwant.fyi/api/mcp --http https://iwant.fyi/api/v1 --api-key <key>

Source: conformance-kit/ · npm: @iwantfyi/conformance-kit (Apache-2.0). The reference implementation also self-reports at /api/v1/conformance.

Reference implementation

iwant.fyi — https://iwant.fyi/api/mcp

The iwant.fyi MCP server is the reference implementation. It advertises spec conformance and is the canonical surface to test against.

Official SDKs (all Apache 2.0)

Framework	Package	Repo
TypeScript / generic	`@iwantfyi/sdk`	staugs/iwantfyi-sdk
LangChain (Python)	`iwantfyi-langchain`	staugs/iwantfyi-langchain
Composio (Python)	`iwantfyi-composio`	staugs/iwantfyi-composio
CrewAI (Python)	`iwantfyi-crewai`	staugs/iwantfyi-crewai

Three open-source example agents at staugs/iwantfyi-examples.

Status

v1.1 is published as a draft for public comment. Feedback, issues, and proposed extensions are welcome via GitHub issues or directly to hi@iwant.fyi.

License

The specification is published under the Apache License 2.0. Implementations are not required to be open source.

Install

Tools (13)

demand.searchdemand.find_vehicledemand.price_checkdemand.request_introductiondemand.introduction_statusdemand.list_verticalsdemand.list_constraintsdemand.health

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://iwant.fyi/api/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "iwant": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://iwant.fyi/api/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

fyi.iwant/iwant MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

demand.search

demand.find_vehicle

demand.price_check

demand.request_introduction

demand.introduction_status

demand.list_verticals

demand.list_constraints

demand.health

demand.capabilities

demand.create_watch

demand.list_watches

demand.cancel_watch

demand.ask

iwant.fyi demand-side protocol

Why a demand-side protocol

Spec

Conformance

Reference implementation

Official SDKs (all Apache 2.0)

Status

License

Install

Remote endpoint

Related servers