mcp-registry/fyi.iwant/iwant · v1.35.0
Also listed as glama/staugs/iwant.fyi-mcp-server
As of 2026-10-18 04:48 UTC, the Iwant MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
No key needed. Search real products and live dealer inventory, price-check, keep standing wants.
Claude Code
claude mcp add --transport http iwant-mcp-server https://iwant.fyi/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"iwant-mcp-server": {
"type": "http",
"url": "https://iwant.fyi/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
13 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).
Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →
Handshake + tools/list takes ~1,744 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 0 tool(s) removed and 4 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Ffyi.iwant%2Fiwant/fixes
{
"name": "demand_ask",
"description": "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 sin",
"inputSchema": {
"type": "object",
"required": [
"message"
],
"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)."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
},
"title": "Ask iwant.fyi to find something (conversational)"
}{
"name": "demand_cancel_watch",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"watch_id"
],
"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."
}
}
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": false
},
"title": "Cancel a standing want"
}{
"name": "demand_capabilities",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
},
"title": "Discover protocol features + limits"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/fyi.iwant/iwant"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/fyi.iwant/iwant"}) over MCP.
demand.search ~750 tokensdemand.find_vehicle ~649 tokensdemand.create_watch ~568 tokensdemand.price_check ~542 tokensdemand.request_introduction ~332 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Ffyi.iwant%2Fiwant?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Ffyi.iwant%2Fiwant?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Ffyi.iwant%2Fiwant.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Ffyi.iwant%2Fiwant.svg :target: https://glimind.com/server/mcp-registry%2Ffyi.iwant%2Fiwant?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:9ebc90c51e15351b…, first seen 2026-10-17, included at leaf 5192 of 20,360. Version history · verify what your client received.
Compare: most reliable search servers · most reliable other servers · most reliable communication servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 04:48 UTC, the Iwant MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Iwant MCP server advertises 13 tools, including demand.ask, demand.cancel_watch, demand.capabilities, demand.create_watch, demand.find_vehicle.
Point your MCP client at this streamable-http endpoint: https://iwant.fyi/api/mcp
Glimind scanned all 13 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.