Back to Browse

Iwantfyi Spec MCP Server

by Staugs
Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Demand-side commerce: agents post a user's purchase intent, get ranked cross-source matches.

About

Demand-side commerce: agents post a user's purchase intent, get ranked cross-source matches.

Remote endpoints: streamable-http: https://iwant.fyi/api/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

19 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

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

Documentation

View on GitHub

From the project's GitHub README.

iwant.fyi demand-side protocol

The iwant.fyi demand-side protocol defines how AI agents express structured purchase intent on behalf of users, receive matched supply across multiple sources, and report outcomes back. It is MCP-native, transport-flexible, and intentionally agnostic about who matches the demand, who fulfills it, and how money moves.

Why

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:

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.fyihttps://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)

FrameworkPackageRepo
TypeScript / generic@iwantfyi/sdkstaugs/iwantfyi-sdk
LangChain (Python)iwantfyi-langchainstaugs/iwantfyi-langchain
Composio (Python)iwantfyi-composiostaugs/iwantfyi-composio
CrewAI (Python)iwantfyi-crewaistaugs/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.

Reviews

No reviews yet

Be the first to review this server!