INDIVIDUAL MCP TOOL

demand.health

iwant.fyi demand-side protocol v1.0 §8.2: liveness and readiness check.

iwant.fyinone authenticationAvailability not checked

LIVE ENDPOINT

https://iwant.fyi/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for demand.health and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.fyi]
url = "https://iwant.fyi/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "fyi": {
      "type": "http",
      "url": "https://iwant.fyi/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: fyi
Remote MCP URL: https://iwant.fyi/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "fyi": {
      "url": "https://iwant.fyi/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "fyi": {
      "type": "http",
      "url": "https://iwant.fyi/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "fyi",
  "transport": "streamable-http",
  "url": "https://iwant.fyi/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

demand.search — Find products to buy for the user across many sources.
demand.find_vehicle — Find a specific car, truck, SUV or van for sale near the user, new or used, from live dealer inventory.
demand.price_check — Tell the user whether the asking price on ONE specific car is a good deal.
demand.request_introduction — Ask a specific seller to answer the user about one car from demand.find_vehicle.
demand.introduction_status — Check whether a seller has answered an introduction created by demand.request_introduction, and read the reply.
demand.list_verticals — iwant.fyi demand-side protocol v1.0 §8.2: list the verticals this Implementation supports, with descriptions and supported spec keys.
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.capabilities — iwant.fyi demand-side protocol v1.1 §8.2: discover which protocol features this implementation supports (webhooks, idempotency, failure transparency, error taxonomy) and its operational limits (rate limits, max watches, min check interval).