# io.github.whalefuntech/intentlink (remote · api.intentlink.io)

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

- Trust score: 63/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.intentlink.io`: 63/100 (this document), [markdown](https://verifymcp.io/servers/whalefuntech-intentlink/api.md), [page](https://verifymcp.io/servers/whalefuntech-intentlink/api)

## Channel facts

- Endpoint: `https://api.intentlink.io/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1399 tokens (~233/item across 6 items; 3 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http whalefuntech-intentlink https://api.intentlink.io/mcp/
```

### Codex

```toml
[mcp_servers.whalefuntech-intentlink]
url = "https://api.intentlink.io/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "whalefuntech-intentlink": {
      "type": "remote",
      "url": "https://api.intentlink.io/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add whalefuntech-intentlink --url https://api.intentlink.io/mcp/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  whalefuntech-intentlink:
    url: "https://api.intentlink.io/mcp/"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 61, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (3)

### `search_products` (~422 tokens)

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.

Input parameters:

- `agent_id` (string, required)
- `commerce_l2s`
- `intent`
- `keywords`
- `limit` (integer)
- `max_price`
- `min_price`
- `platforms`
- `query` (string, required)
- `require_commission`

### `search_travel` (~366 tokens)

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.

Input parameters:

- `agent_id` (string, required)
- `city` (string, required)
- `hotel`
- `limit` (integer)
- `type` (required)

### `search_events` (~460 tokens)

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.

Input parameters:

- `agent_id` (string, required)
- `categories`
- `city`
- `date_from`
- `date_to`
- `keywords`
- `limit` (integer)
- `max_price`
- `min_price`
- `query` (string, required)
- `sort`
- `state`
- `when`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/whalefuntech-intentlink/api#diagnostics

## Score history

- 2026-08-03: 63
- 2026-08-02: 62
- 2026-08-01: 62
- 2026-07-31: 61
- 2026-07-30: 60
- 2026-07-29: 59
- 2026-07-28: 59
- 2026-07-27: 58
- 2026-07-26: 57

## Links

- Remote endpoint: https://api.intentlink.io/mcp/
- Repository: https://github.com/whalefuntech/intentlink_docs
- Website: https://intentlink.io/
- Changelog RSS feed: https://verifymcp.io/servers/whalefuntech-intentlink/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/whalefuntech-intentlink/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/whalefuntech-intentlink/api