Intentlink

io.github.whalefuntechPublished by GitHub account whalefuntechv1.0.0Updated Oct 27, 2026

The best agent monetization tool: free search, clear rev-share, 10M+ commerce/travel/local offers.

VerifiedStreamable HTTPWeb executableLocation & LifestyleBusiness & Commerce

Overview

AI-generated overview

IntentLink is a remote MCP server that lets an assistant search affiliate shopping, travel and event offers and return trackable booking or purchase links.

What you can do
  • Search shopping products by natural-language query and get ranked recommendations, with optional keyword and product-type filters
  • Search travel offers for hotels, flights, bundles, airport transfers and car rentals in supported cities, returning trackable booking links
  • Search live ticketing and events such as concerts, sports and theater, returning ranked event bundles
  • Read a travel cities resource to find valid city values for travel searches
When to use it
Use it when an assistant should turn a shopper's or traveler's request into concrete commercial recommendations with links the user can act on, and when the operator wants affiliate attribution tied to an agent ID.
Requirements
A remote MCP endpoint; no local package or runtime. An agent_id obtained from the provider's portal, passed per tool call rather than in the static configuration. Network access to the hosted endpoint.
Before you install
Results are monetized affiliate recommendations, so suggestions may be commercially motivated; the README states the operator keeps 80% of revenue on converted intents. The agent_id is passed on each tool call and attribution flows back to it. The README says no PII is stored and matching uses transient conversation context, but user queries are still sent to a third-party service.

Installation

In SourceWeft

  1. Open Intentlink in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.whalefuntech%2Fintentlink/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "intentlink": {
      "type": "http",
      "url": "https://api.intentlink.io/mcp/"
    }
  }
}

README

IntentLink

Monetize your AI agent's conversations — natively, without banners.

IntentLink is a commercial intent network built for the AI agent era. Add the IntentLink MCP server (or REST API) to your agent, and it gains the ability to surface relevant, monetizable commerce recommendations directly inside its answers — not as an ad unit bolted on top, but as part of the conversation itself.

Website · Docs · Developer Dashboard · For Merchants & Partners

Why IntentLink

  • Native to the conversation. Recommendations surface as part of the agent's answer — contextual and relevant, not a banner or pop-up.
  • Zero UX disruption. Your agent stays your agent. No iframes, no forced redirects, no interruption of the conversation flow.
  • You keep 80% of revenue. Transparent rev-share on every converted intent. No upfront fee, no platform fee — IntentLink only earns when you do.
  • Privacy-first by design. No PII is stored. Intent matching runs on transient conversation context only, aligned with GDPR/CCPA.
  • Works with any MCP-compatible runtime — Claude, OpenAI-compatible agents, LangChain, or custom stacks (a language-agnostic REST API is available as a fallback).

Quick Start

Add IntentLink as a remote MCP server:

json
{"mcpServers": {"intentlink": {"url": "https://api.intentlink.io/mcp/"}}}

Your agent_id is passed per tool call, not in the static config — get one at portal.intentlink.io.

Prefer REST? See the full docs for the language-agnostic API.

What it does

Once connected, your agent can match user intent to relevant commercial offers and return a trackable purchase link for the user to complete the transaction — attribution flows back to your agent_id automatically.

About this repo

This repository hosts public documentation and integration resources for IntentLink. The IntentLink MCP server itself is remotely hosted (not distributed as an installable package) — see Quick Start above to connect.

License

MIT — see LICENSE file for details.

Source: README.md at commit c541e92

Tools

3

search_products

Search affiliate shopping products and get ranked recommendations. Only `query` is required — a natural-language description of what the shopper wants (e.g. "a warm waterproof jacket for winter hiking"). Add fields to narrow results: - keywords: exact product terms. Use a SPECIFIC product type ("women running shoes", "stainless steel knife set"), not a bare generic noun ("shoes", "knife") — a generic keyword can surface the wrong audience. Audience/occasion go in `query`. - commerce_l2s: category ids to restrict to (read the `commerce://categories` resource for valid values — that taxonomy is for shopping only). - max_price / min_price: price band (USD). platforms: ["amazon"|"walmart"] (empty=all). - intent: ranking preset — "cheapest" | "best_discount" | "top_rated" | "best_value". - require_commission: only return products that pay a commission (default: server setting, normally on). Pass false to include zero/unknown-commission products. - limit: max results (default 10). `agent_id` is REQUIRED: your registered, active agent id. It is the attribution key and the access key — a missing/blank or unregistered agent_id is rejected (no anonymous use). Returns {count, products:[{offer_id,title,brand,price,rating,...,buy_url,product_url}]}. Each product's `buy_url` is ALREADY the trackable affiliate buy link — hand it to the shopper directly. (`product_url` is the plain product page.) There is no separate resolve/click step.

Parameterslimitqueryrequiredintentagent_idrequiredkeywordsmax_pricemin_priceplatformscommerce_l2srequire_commission

search_travel

Search travel offers and get trackable booking links for a given product type + city. REQUIRED: - type: which travel product — one of ["hotel","flights","bundle","airport_transfer","car_rental"]. - city: city name from the supported list — read the `travel://cities` resource for valid values (that city list is for travel only). Pass hotel.state (e.g. "NY") when the city name is ambiguous. - agent_id: your registered, active agent id — the attribution + access key. A missing/blank or unregistered agent_id is rejected (no anonymous use). HOTEL runs a live Trip.com search — pass the `hotel` object with the stay: check_in / check_out (YYYY-MM-DD), rooms, adults, children, state. If those are missing/invalid or the city can't be resolved, you get the hotel default links instead. Other types currently return curated default links (the `hotel` object is ignored for them). Returns {status, reason, message, links:{<type>:[{title, brand, platform, buy_url, product_url, ...}]}}. status is "ok" = a live hotel result; "fallback" = curated default links (see `reason`); "no_results" = nothing available for the type; "error" = the agent_id was rejected. Each `buy_url` is ALREADY the trackable booking link — hand it to the traveler directly. `product_url` is the plain merchant page.

Parameterscityrequiredtyperequiredhotellimitagent_idrequired

search_events

Search live ticketing/events (concerts, sports, theater) and get ranked event bundles. Only `query` is required — a natural-language description of what the buyer wants (e.g. "taylor swift concert near LA this summer"). Add fields to narrow results: - keywords: exact terms — performer / team / show / venue (a precise lookup). - categories: e.g. ["Concerts"|"Sports"|"Theater"] (read the `events://categories` resource for valid values). - city / state: location (e.g. city="Los Angeles", state="CA"). country defaults to US. - date_from / date_to: explicit date window, YYYY-MM-DD (event dates are date-only). - when: fuzzy time — "this_weekend" | "this_week" | "this_month" | "next_7_days" | "next_30_days" (ignored if date_from/date_to are given). - min_price / max_price: ticket 'from' price band (USD). - sort: "relevance" (default) | "soonest" | "cheapest". - limit: max results (default 10). `agent_id` is REQUIRED: your registered, active agent id — the attribution + access key. A missing/blank or unregistered agent_id is rejected (no anonymous use). Returns {count, message, events:[{bundle_id,title,venue,city,next_date,price_min,..., sessions:[{date,price,buy_url,landing_url}]}]}. Each session's `buy_url` is ALREADY the trackable ticket link — hand it to the buyer directly. `landing_url` is the plain event page. When a date filter is given, `sessions` are the in-window dates.

Parameterscitysortwhenlimitqueryrequiredstatedate_toagent_idrequiredkeywordsdate_frommax_pricemin_price+1 more

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts