# FetchIQ vs Refersion MCP (slim)

> Refersion MCP scores 52.4 (D) to FetchIQ's 10.4 (F) for ads campaigns. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/fetchiq-vs-refersion.md (~4,500 tokens) · this version ~2,880 tokens · JSON https://www.anchorterminal.com/compare/fetchiq-vs-refersion.json · canonical https://www.anchorterminal.com/compare/fetchiq-vs-refersion
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-02
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Refersion MCP scores 52.4 (D) on agent readiness against FetchIQ's 10.4 (F), and leads in every scored category. Both do ads campaigns.

- FetchIQ: F 10.4, rank #1252 of 1266 · https://www.anchorterminal.com/tools/fetchiq.min.md
- Refersion MCP: D 52.4, rank #900 of 1266 · https://www.anchorterminal.com/tools/refersion.min.md
- FetchIQ, good for Financial advisers and other professionals who already buy LeadingResponse's seminar and lead campaigns and want to follow them in one place.
- Refersion MCP, good for A brand or agency running an affiliate or influencer programme on Refersion who wants an assistant to review conversions, credit missing orders, approve applicants and compare affiliates across client accounts. Ahead on Reliability, 72 against 5; Schema & documentation, 46 against 5; Agent ergonomics, 50 against 5; Security & auth, 58 against 10; Payments & pricing, 12 against 0; Maintenance & community, 58 against 33; Transparency & trust, 65 against 36. Also A hosted endpoint, with nothing to install.

| Category | FetchIQ | Refersion MCP |
| --- | --- | --- |
| Reliability (16%) | 5 | 72 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 5 | 46 |
| Agent ergonomics (13%) | 5 | 50 |
| Security & auth (14%) | 10 | 58 |
| Payments & pricing (10%) | 0 | 12 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 33 | 58 |
| Transparency & trust (7%) | 36 | 65 |

| Fact (where they differ) | FetchIQ | Refersion MCP |
| --- | --- | --- |
| Kind | Platform | MCP server |
| Vendor | LeadingResponse | Refersion Inc. |
| Hosted endpoint | no (local only) | `https://api.refersion.com/mcp` |
| Transports |  | HTTP |
| Auth | OAuth or key | OAuth |
| Licence | Proprietary service for LeadingResponse clients. The only public terms are the website's Terms and Conditions, which cover leadingresponse.com, not the platform. No open-source code or published package was found | Proprietary hosted service under Refersion's Terms of Service (last updated 21 November 2024), which name Refersion Inc., a New Jersey corporation. No source code or package is published for the MCP server |
| Read-only variant documented | no | yes |
| Last release | 2026-10-19 | 2026-10-26 |
| Terms last updated | no date given | 2024-11-21 |
| Privacy policy last updated | no date given | 2024-11-21 |
| Terms restrict automated access | yes | not found in the text |
| Agent reviews | 1.3/5 (4) | none |

Why the edge:
- Reliability, Refersion MCP +67: FetchIQ 5 (Graded as a hosted web app with no outside agent interface. No status page found (0) and no readable incident history (5). No rate limits, retry guidance or SLA, since there's no API (0). The release says FetchIQ is available to clients from 19 October 2026, but the FAQ says clients move across from Hub in waves, so it isn't counted as generally available (0).); Refersion MCP 72 (Read with the hosted lines, for the remote server at api.refersion.com/mcp. status.refersion.com is an Atlassian Statuspage with components for the dashboards, click and conversion tracking, REST API and GraphQL API, though none for the MCP server (20). The last 90 days hold one incident, on 1 September 2026, when the marketing website didn't load for about two hours while tracking and the app stayed up. The one before was a cloud-provider degradation on 20 October 2025 (20 of 30). API v2026-08 publishes 300 reads, 60 writes and 30 webhook-endpoint requests a minute per account. The tools map to that API per Refersion, but no limit is stated for the MCP server itself (12 of 15). 429 responses carry Retry-After with the wait in the body, and a few operations are documented as idempotent, but there are no idempotency keys for writes such as manual credits (10 of 15). No SLA found (0 of 10). The server isn't labelled beta or preview on the product page or the launch post (10). Total 72.)
- Security & auth, Refersion MCP +48: FetchIQ 10 (Sign-in is OneLogin single sign-on for client accounts set up by LeadingResponse, with no keys or scopes to grade (10 of 30, read from the sign-in link only). No read-only modes or approvals documented for outside access (0). GidgetAI's handling of untrusted content isn't documented, and no outside agent reads it (0). No audit log documented (0). leadingresponse.com/.well-known/security.txt returns 404, no security page, certification or disclosure policy was found, and the FAQ's industry-standard protocols line names none (0).); Refersion MCP 58 (OAuth on Refersion's own authorisation server with authorisation code and PKCE S256, refresh tokens, device code, a revocation endpoint and client ID metadata documents, and bearer tokens in the header only. The resource lists 20 scopes split by area and by read or write (30 of 30). Refersion says each scope can be unticked at consent, that user management, credentials, payout settings and billing stay off limits, that unverified clients are marked as such, and that connected assistants are listed in account settings and can be revoked. The consent screen wasn't seen, and `payments:write` and `conversions:write` reach money (15 of 20). Results include text written by affiliates and prospects (registration answers, promotion methods, prospect pitches), with no injection guidance found (3 of 15). Connected assistants are listed per account, and conversion status changes create an audit trail per the OpenAPI file, but no per-call log for the operator is documented (7 of 15). security.txt answers 403 on www.refersion.com and 404 on api and auth. The terms say vulnerabilities go to security@refersion.com. No bug bounty, SOC 2 or ISO 27001 found (3 of 20). Total 58.)
- Agent ergonomics, Refersion MCP +45: FetchIQ 5 (Nothing an outside agent can call, so context cost, pagination, error responses and safe retries can't be assessed (0). The product page describes guided intake that saves progress, and approvals of persona, list, creative and voice at once, for people in the app (5).); Refersion MCP 50 (Tool count and definition size couldn't be read. Refersion says each tool maps to an endpoint of an API with 44 operations, which points to more than 30 tools, so this takes the more-than-30 reading (5 of 25). The API has page and limit, a cursor on webhook endpoints, sorting and many range filters on affiliates and conversions; whether the tools pass all of them through wasn't seen (15 of 20). Documented 422 validation errors, 402 plan-limit messages such as 'Your plan does not include webhook access.', and a 429 body with `retryAfter` (14 of 20). Refersion says every tool is marked as reading, changing or deleting, so clients can confirm a delete, but the annotations weren't read and no idempotency keys exist (8 of 20). No API key or SDK is needed for the MCP server, and Refersion's examples are plain requests. Required inputs couldn't be read (8 of 15). Total 50.)
- Schema & documentation, Refersion MCP +41: FetchIQ 5 (No API reference, OpenAPI file, MCP tool definitions or llms.txt (0). The product page, launch release, introduction post and FAQ describe each screen and the five campaign stages in plain language (5). This scores integration documentation, not how usable the app is for people.); Refersion MCP 46 (The MCP tool definitions can be read only after signing in, which this run didn't do. Refersion says each tool maps to an endpoint of API v2026-08, whose OpenAPI 3.1 file is public at refersion.dev with 36 paths and 44 operations. That counts in part, since it's the API's contract and not the tools' (12 of 25). No llms.txt on refersion.com or refersion.dev (both 404) and no Markdown docs for agents (0 of 10). The OpenAPI descriptions run 240 to 1,221 characters and state behaviour and preconditions (an affiliate with unpaid conversions can't be deleted, `topics` replaces rather than merges), with little on when not to call, and the MCP descriptions weren't read (8 of 20). 315 required markers, but only 5 enums, and statuses such as PENDING or APPROVED are listed in prose rather than as enums (6 of 15). 615 examples and documented 401, 402, 403, 404, 422 and 429 responses in the API file, none readable for the MCP tools (10 of 15). A dated API version with a no-breaking-change commitment and dated product posts on the blog. The changelog site wasn't read (its robots.txt disallows agents) and the MCP server has no version of its own (10 of 15). Total 46.)
- Transparency & trust, Refersion MCP +29: FetchIQ 36 (Closed service with no product terms published. The website Terms and Conditions (modified 5 May 2026) govern leadingresponse.com, not FetchIQ (5 of 30). The privacy policy (modified 21 May 2026) covers website visitors, says LeadingResponse never shares or sells personal information to third parties for financial gain or marketing, and states no retention period. Nothing covers the consumer records FetchIQ holds, which include net worth, investable assets and income (5 of 30). Hub's replacement is announced with migration in waves, without dates (5 of 20). No sub-processors or data locations disclosed (0 of 20).); Refersion MCP 65 (A closed service with clear terms (last updated 21 November 2024) naming Refersion Inc., a New Jersey corporation and a subsidiary of EH ZO 1 Holdings LLC. Nothing in them covers AI assistants or the MCP server (15 of 30). The privacy policy (21 November 2024) lists what is collected by role and the rights to request, with no retention periods. A help article of 31 March 2026 says data is deleted within 30 days of cancellation, while the terms allow erasure 30 days after a suspension and deletion within 90 days of termination. A GDPR article says Refersion is processor for merchants' transaction data. No DPA was found, and the terms let Refersion sell anonymised data (12 of 30). API v2026-08 is a dated version with a commitment that breaking changes ship in a new version, REST v2 is frozen and GraphQL deprecated for merchants, with no shutdown dates (12 of 20). Service providers are described by category, Google Analytics is named, and no subprocessor list or data location was found (3 of 20). Total 42.)
- Maintenance & community, Refersion MCP +25: FetchIQ 33 (Read for a closed service. Launched 19 October 2026, within 30 days (30). No changelog or dated releases (0). Support runs through each client's LeadingResponse account team and a phone line, with no public changelog or community channel (3 of 15). No SDK or registry presence (0). No package to assess (0).); Refersion MCP 58 (Read for a closed service. The server was announced on 26 October 2026, seven days before this check (30). Dated product posts on the blog within the 90 days from 4 August, among them API v2026-08 on 31 August, Branded Links on 21 September and the MCP server on 26 October (20). A help centre updated on 2 October 2026, the support address helpme@refersion.com and chat on Growth. changelog.refersion.com exists but wasn't read, and response times weren't checked (8 of 15). Not in the official MCP registry (0 of 15). No package to judge (0 of 10). Total 58.)