intentlink
https://api.intentlink.io/mcp ↗
Description
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)
What our measurements say
intentlink is a remote MCP server published at api.intentlink.io. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 448 ms, placing it among the faster endpoints. It offers a narrow, focused set of 3 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names clearly indicate their purpose (search_products, search_travel, search_events).
- No tool overlap/ambiguity between product, travel, and event search functions.
Weaknesses
- Descriptions are incomplete (e.g., search_travel's city parameter references 'travel://cities' without explaining how to access it).
- Parameter definitions lack explicit type declarations and optional/required clarity.
- No documentation of error handling or input validation constraints.
search_products— Description cuts off mid-sentence, leaving parameter details incompletesearch_travel— City parameter references external resource without explaining how to access valid valuessearch_events— Parameter definitions lack explicit type declarations and optional/required indicators
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from 'auth-gated' to 'legacy' · system moved to legacy operational mode
- 2026-09-11T03:50:39.090Z — complianceScore increased from null to 100 · achieved full regulatory compliance
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 329ms → warm 198ms (penalty 131ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 1.29.1
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/tech-xosl-intentlink)<a href="https://mcpmetrics.io/servers/tech-xosl-intentlink"><img src="https://mcpmetrics.io/badge/tech-xosl/intentlink/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see