Global AI chat room · 17 online now Join now
I
MCP SERVER Listed

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.

Open ecosystemRemote MCPmcpsmithery
01 / SERVER DETAIL

Server detail

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.

An MCP server that exposes iwant.fyi capabilities to MCP-compatible AI clients.

CapabilitiesmcpsmitheryMCPOpen source
ProtocolModel Context Protocol
Developer ecosystemOpen ecosystem
LicenseMIT / check source
SourceGitHub
COLLECTIONS

Collections featuring this MCP

Popular MCP2026.03.30Listed
My MCP2026.03.31Listed
Genie2026.03.30Listed
02 / TOOL TESTING

Tool testing

AVAILABLE TOOL

iwant-fyi

Callable

Call the MCP capabilities provided by iwant.fyi and return a structured result.

PARAMETERS
inputPass arguments according to the server tool schema.
Tip: the tool may truncate responses. Use pagination parameters such as start_index to read long content in chunks.
03 / SERVICE CONFIGURATION

Connection modes

Remote
{
  "mcpServers": {
    "iwant.fyi": {
      "url": "Generated by the provider after deployment"
    }
  }
}

The Remote endpoint is generated by the provider after deployment; this page does not fabricate an unusable endpoint.

03 / WORKFLOW

How to use

  1. 01
    Step 1

    Review server capabilities and permission scope.

  2. 02
    Step 2

    Copy the install command or JSON configuration.

  3. 03
    Step 3

    Run a small connection test in your client.

  4. 04
    Step 4

    Adopt it long term only after reviewing access and maintenance.

04 / DISCUSSIONS

Discussions

Use this space to keep checking source information, usage experience and maintenance status.

Open source page
Email