IntentLink - Monetize your AI agent's conversations, natively. IntentLink is a commercial intent network built for the AI agent era. Add the IntentLink MCP server to your agent and it gains the ability to surface relevant, monetizable commerce recommendations directly inside its answers - not an ad unit bolted on top, but part of the conversation itself. Connect once to a single remote endpoint and your agent can search shopping, travel, and events across 10M+ offers, returning a ready-to-use, trackable purchase link on every result. Attribution flows back to your agent automatically. - Native to the conversation - recommendations surface as part of the answer, not a banner or pop-up. - Free to search - you only share revenue when a purchase converts. No upfront fee, no platform fee. - Keep 80% of revenue - transparent rev-share on every converted intent. - Privacy-first - no PII stored; intent matching runs on transient conversation context (GDPR/CCPA aligned). - Works with any MCP-compatible runtime - Claude, OpenAI-compatible agents, LangChain, or custom stacks (a REST API fallback is available). Tools: - search_products - shopping across platforms like Amazon and Walmart - search_travel - hotels, flights, bundles, airport transfer, car rental - search_events - concerts, sports, theater (live ticketing) Every result carries a trackable buy_url you can hand to the user directly. Get your agent_id at https://portal.intentlink.io
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (2272 ms). |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 3 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 0/5 | not seen in a source for over 30 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 60% of peers
- This listing 83 · peer median 81
- Latency
- Faster than 46% of peers
- This listing 360 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Freshness + modern flags −5
— Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/tech-xosl/intentlink/mcpcurl -X POST https://server.smithery.ai/tech-xosl/intentlink/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'