{
  "data": {
    "a": {
      "slug": "fuse-mcp",
      "name": "Fuse MCP",
      "vendor": "FuseAI, LLC",
      "vendorUrl": "https://fuseai.com",
      "company": "fuseai.com",
      "kind": "mcp",
      "category": "lead-data",
      "summary": "Fuse MCP is the hosted MCP server for Fuse AI's sales platform. It lets an assistant search people and companies, enrich contacts, manage lists and campaigns, and send email and LinkedIn messages from a signed-in Fuse account.",
      "url": "https://www.anchorterminal.com/tools/fuse-mcp",
      "markdownUrl": "https://www.anchorterminal.com/tools/fuse-mcp.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/fuse-mcp.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/fuse-mcp.json",
      "dns": "fuse-mcp.grade.anchorterminal.com",
      "license": "Proprietary hosted service under FuseAI's terms of service. No public source repository found",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://mcp.fuseai.com",
      "packages": [],
      "auth": "oauth",
      "authNotes": "Access is self-serve. The client registers itself by dynamic client registration, then a person signs in to their Fuse account in a browser (email and password, Google or Microsoft, with a verified email address) and approves the connection. The flow is authorisation code with PKCE (S256) and the single scope `mcp:tools`. The connection runs as that user with all of their permissions. Access tokens last one hour, refresh tokens rotate on each use and last 30 days from last use. There is no API-key route into the MCP server. The separate REST API takes `af_` keys over HTTP Basic, limited to any of nine scopes.",
      "pricing": "freemium",
      "pricingNotes": "Free plan at $0, then Solo $60 a month with 480,000 credits a year and Team $200 a month with 1,200,000, with 20 per cent off for annual billing. Enterprise is by quote. The pricing page gives the Free allowance as 24,000 credits a year on the plan card and 2,000 in the usage table. MCP calls spend the same credits as the app, and every call needs a balance of at least 100. The Solo card lists MCP among its integrations, and we could not confirm from the page that the Free plan includes it. Top-up prices are shown only in the app. We did not attempt signup, so whether a card is asked for is unchecked (https://fuseai.com/pricing, checked 2026-10-08).",
      "priceSummary": "$60 / mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the MCP docs, the REST docs, the OpenAPI spec or the pricing page (checked 2026-10-08).",
        "endpoints": []
      },
      "toolCount": 290,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-08"
      },
      "docsUrl": "https://docs.fuseai.com/mcp/connect",
      "llmsTxt": "https://docs.fuseai.com/llms.txt",
      "openapi": "https://docs.fuseai.com/openapi.json",
      "capabilities": [
        "lead.search",
        "lead.enrichment",
        "email.finder",
        "email.verification",
        "data.company",
        "email.send",
        "search.research"
      ],
      "tags": [
        "hosted",
        "mcp",
        "oauth",
        "freemium",
        "sales",
        "outreach",
        "enrichment",
        "lead-search",
        "llms-txt",
        "openapi",
        "closed-source",
        "new"
      ],
      "lastRelease": "2026-10-07",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 46.2,
        "grade": "D",
        "agentReady": false,
        "rank": 1257,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 18,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 57,
          "maintenance": 35,
          "payments": 45,
          "reliability": 40,
          "schema": 50,
          "security": 43,
          "transparency": 52
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-04"
        },
        "negative": 0,
        "verdict": "The server documents 290 tools with read-only and destructive annotations, OAuth with PKCE and dynamic client registration, and published limits of 60 requests a minute. The single `mcp:tools` scope grants everything the user can do, sends happen at once with no undo, and no status page, changelog or security contact was found.",
        "bestFor": "Suited to a salesperson or founder who wants an assistant to build prospect lists, enrich them and run email and LinkedIn outreach inside one Fuse account.",
        "strengths": [
          "Every tool carries `readOnlyHint` or `destructiveHint` per the docs, and the tool reference marks 113 read-only, 144 writing and 33 destructive",
          "OAuth authorisation code with PKCE and dynamic client registration, one-hour access tokens and rotating refresh tokens",
          "MCP limits are published at 60 requests a minute and 5,000 a day per user, with `RATE_LIMIT_EXCEEDED` on 429",
          "Credit costs per action are public, reads are free, and `get_credit_prices` returns current prices before a call",
          "llms.txt, Markdown twins of every docs page and a skill file, per the 8 October check"
        ],
        "weaknesses": [
          "The only OAuth scope is `mcp:tools`, so a connection can do everything its user can, including sending email and LinkedIn messages",
          "The 290 tools come to about half a megabyte of descriptions and schemas, with no toolsets or read-only subset",
          "The October 2026 rebuild removed the earlier tools such as `prospect_search`, and the docs say the server does not announce tool list changes",
          "No status page, changelog, SLA, security.txt or disclosure contact was found on the site or in the docs",
          "Vendor pages disagree on the Free allowance (24,000 credits a year or 2,000) and on the provider count (40+, 39 or 20+)"
        ],
        "agentNotes": [
          "Keep the client's approval prompt on for every tool that is not read-only. Sends, CRM pushes and Slack posts run at once with no undo",
          "Launch a campaign only on an explicit request. Creating one makes a draft, and `update_campaign_status_tool` starts real outreach",
          "Call `get_credits_balance` and `get_credit_prices` first. Every call needs at least 100 credits, and searches cost 2 credits a result",
          "Resolve filter values with `lookup_filter_values` or `get_company_search_enums` before `search_people` or `search_companies`",
          "Start long work with `deep_research_start`, then poll `deep_research_status`. A tool call has 60 seconds, and runs take 5 to 20 minutes"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "D",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 46.2
          }
        ],
        "editorialScores": {
          "ergonomics": 57,
          "maintenance": 35,
          "payments": 45,
          "reliability": 40,
          "schema": 50,
          "security": 43,
          "transparency": 36
        },
        "provenanceScore": 67,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-04",
            "maintenance": "2026-11-04",
            "payments": "2026-11-04",
            "reliability": "2026-11-04",
            "schema": "2026-11-04",
            "security": "2026-11-04",
            "transparency": "2026-11-04"
          },
          "last": "2026-11-04",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-04",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "claudeCode": "claude mcp add --transport http fuse https://mcp.fuseai.com",
        "config": {
          "mcpServers": {
            "fuse": {
              "url": "https://mcp.fuseai.com"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/lead.search",
        "tool": "https://letme.dev/fuse-mcp"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Free plan",
          "unit": "month",
          "usd": 0,
          "note": "1 seat. The pricing page shows 24,000 credits a year on the plan card and 2,000 in the usage table"
        },
        {
          "item": "Solo plan",
          "unit": "month",
          "usd": 60,
          "note": "1 seat, 480,000 credits a year"
        },
        {
          "item": "Team plan",
          "unit": "month",
          "usd": 200,
          "note": "5 seats, 1,200,000 credits a year"
        }
      ],
      "provenance": {
        "legalEntity": "FuseAI, LLC",
        "domain": "fuseai.com",
        "domainRegistered": "2017-03-11",
        "endpointOnVendorDomain": true,
        "terms": "https://fuseai.com/legal/terms-of-service",
        "privacy": "https://fuseai.com/legal/privacy-policy",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-10-08",
        "notes": [
          "The terms of service (last updated 1 July 2026) give the contracting party as FuseAI, LLC with the contact hello@tryfuse.ai and no postal address. The company page says the team is in San Francisco.",
          "The MCP server answers at mcp.fuseai.com and its authorisation server at core.backend.fuseai.com. The REST API is on api.tryfuse.ai, the vendor's earlier domain, and tryfuse.ai redirects to fuseai.com.",
          "fuseai.com/.well-known/security.txt and docs.fuseai.com/.well-known/security.txt return 404.",
          "No status page or changelog is linked from the site, the docs index or the sitemap. status.fuseai.com, status.tryfuse.ai and trust.fuseai.com did not connect from our network.",
          "RDAP for fuseai.com gives a registration date of 2017-03-11, so the domain predates the company's use of it. The domain's history before Fuse was not checked."
        ],
        "score": 67
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/fuse-mcp.json",
      "live": {
        "slug": "fuse-mcp",
        "probe": {
          "target": "https://mcp.fuseai.com",
          "method": "mcp-initialize",
          "lastAt": "2026-11-18T21:50:49.501593051Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 430,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 99.99,
          "p50ms24h": 349,
          "p95ms24h": 507,
          "samples24h": 242,
          "samples30d": 7829,
          "days": [
            {
              "date": "2026-10-18",
              "probes": 256,
              "ok": 256
            },
            {
              "date": "2026-10-19",
              "probes": 255,
              "ok": 255
            },
            {
              "date": "2026-10-20",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-21",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-22",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-23",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-24",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-25",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-26",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-27",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-28",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-29",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-30",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-11-01",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-11-02",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-11-03",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-11-04",
              "probes": 246,
              "ok": 246
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 185
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 241
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 244
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 220,
              "ok": 220
            }
          ],
          "since": "2026-10-08T00:00:00Z"
        },
        "securityTxt": {
          "url": "https://fuseai.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:31:33.785748356Z"
        },
        "llmsTxt": {
          "url": "https://docs.fuseai.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:14:24.039370592Z"
        },
        "domain": {
          "domain": "fuseai.com",
          "registered": "2017-03-11",
          "source": "https://rdap.verisign.com/com/v1/domain/fuseai.com",
          "checkedAt": "2026-11-15T15:39:08.314476774Z"
        },
        "pages": [
          {
            "url": "https://fuseai.com/pricing",
            "kind": "pricing",
            "status": 304,
            "checkedAt": "2026-11-18T21:44:11.384860786Z",
            "changedAt": "2026-11-17T21:03:05.463682464Z",
            "fingerprint": "2e01e503e050"
          },
          {
            "url": "https://fuseai.com/legal/privacy-policy",
            "kind": "privacy",
            "status": 304,
            "checkedAt": "2026-11-18T21:44:07.18159628Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "d35ecd9cf6d0"
          },
          {
            "url": "https://fuseai.com/legal/terms-of-service",
            "kind": "terms",
            "status": 304,
            "checkedAt": "2026-11-18T21:44:09.412728796Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "911a898c524d"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.fuseai.com",
          "checkedAt": "2026-11-18T04:24:02.253316807Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-10-08T21:33:51.293613327Z"
        },
        "updatedAt": "2026-11-18T21:50:49.501593051Z"
      },
      "streak": {
        "days": 41,
        "from": "2026-10-08",
        "sinceWatching": true,
        "best": 41
      }
    },
    "answer": "Fuse MCP scores 46.2 (D) on agent readiness against Retriever's 32 (F), and leads in 4 of 7 scored categories. Retriever leads on reliability, schema \u0026 documentation and agent ergonomics.",
    "b": {
      "slug": "retriever",
      "name": "Retriever",
      "vendor": "Retriever",
      "vendorUrl": "https://retriever.run",
      "company": "retriever.run",
      "kind": "http-api",
      "category": "lead-data",
      "summary": "Retriever is a hosted prospecting agent that finds and qualifies companies and contacts, enriches them with emails and phone numbers, and runs email and LinkedIn outreach, through a REST API and a remote MCP server.",
      "url": "https://www.anchorterminal.com/tools/retriever",
      "markdownUrl": "https://www.anchorterminal.com/tools/retriever.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/retriever.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/retriever.json",
      "dns": "retriever.grade.anchorterminal.com",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://api.retriever.run/mcp",
      "packages": [],
      "auth": "mixed",
      "authNotes": "Bearer API key (`ret_live_...`) made in the app under Settings \u003e API keys after a browser signup, shown once. The MCP server also takes OAuth 2.1 with dynamic client registration and PKCE, and the access token it issues is an ordinary API key named after the connection. No scopes or expiry were found: a key works as its creator in that person's organisation. Keys are revoked one by one in Settings; removing a connector doesn't revoke its key. The MCP docs also accept the key in the URL as `?api_key=`, with a warning about logs.",
      "pricing": "paid",
      "pricingNotes": "Starter from $80 a month billed quarterly for 6,000 credits ($0.0134 a credit), up to 40,000 credits a month, with one-off top-ups and credits kept 12 months. Email senders $2 each or $30 for unlimited, LinkedIn senders $10 an account. Credits per action are published, a work email 4 to 12, a phone 15 to 60, a company 0.5 to 2. Enterprise is through sales. No free tier or no-card trial was found; the terms say only that free tiers may be offered.",
      "priceSummary": "$0.0134 / credit",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the pricing page, the docs, llms.txt or the OpenAPI file, 18 November 2026. Credits come with a subscription bought in the app.",
        "endpoints": []
      },
      "toolCount": 67,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://docs.retriever.run",
      "llmsTxt": "https://docs.retriever.run/llms.txt",
      "openapi": "https://docs.retriever.run/openapi.yaml",
      "capabilities": [
        "lead.search",
        "lead.enrichment",
        "email.finder",
        "data.company",
        "web.search",
        "web.scrape"
      ],
      "tags": [
        "hosted",
        "mcp",
        "remote-mcp",
        "oauth",
        "openapi",
        "llms-txt",
        "closed-source",
        "paid",
        "subscription",
        "linkedin",
        "outreach",
        "no-status-page",
        "platform-rules",
        "eu"
      ],
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 32,
        "grade": "F",
        "agentReady": false,
        "rank": 1455,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 21,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 75,
          "maintenance": 5,
          "payments": 30,
          "reliability": 45,
          "schema": 82,
          "security": 23,
          "transparency": 49
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": -15,
        "warnings": [
          {
            "kind": "platform-rules",
            "name": "Breaks the rules of the platforms it acts on",
            "text": "Retriever connects a customer's LinkedIn accounts and sends invitations, messages, profile visits and post likes from them on a schedule, with messages a model writes, which LinkedIn's rules on automated activity forbid.",
            "deduct": -15,
            "since": "2026-11-18",
            "sources": [
              "https://docs.retriever.run/mcp/tools.md",
              "https://retriever.run/pricing",
              "https://www.linkedin.com/help/linkedin/answer/90586",
              "https://www.linkedin.com/help/linkedin/answer/a1341387"
            ]
          }
        ],
        "verdict": "Retriever automates outreach from customers' LinkedIn accounts, which LinkedIn's rules forbid. For agents it has an OAuth MCP server, an OpenAPI file, idempotency keys, stable error codes and published credit prices, but no status page, changelog, security contact, free tier or named company behind it.",
        "bestFor": "A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.",
        "strengths": [
          "OpenAPI 3.1 file, llms.txt and Markdown docs, with an errors page of stable codes and the action to take for each",
          "Remote MCP server with OAuth 2.1, dynamic client registration and PKCE, so a client connects without pasting a key",
          "Rate limits published per key and class (30 a minute for runs, 120 for services, 600 for reads and MCP messages), with Retry-After on 429",
          "Idempotency keys on run creation and a recipe for safe retries, plus read-only, destructive and idempotent hints on the MCP tools",
          "Credits per action and the dollar price per credit published without a login"
        ],
        "weaknesses": [
          "Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted",
          "No status page, changelog, security.txt, disclosure policy or certification found",
          "Keys have no scopes or expiry, and the MCP docs accept the key in the URL as `?api_key=`",
          "No free tier or trial without a card found; access needs a browser signup and a subscription from $80 a month",
          "The terms and privacy policy name only \"Retriever\" under French law, with no company number or address, and the privacy policy doesn't mention connected LinkedIn or email accounts"
        ],
        "agentNotes": [
          "Don't enrol leads in a sequence with LinkedIn steps without the user knowing LinkedIn forbids automated activity and can restrict their account",
          "Send an `Idempotency-Key` with each run and replay with the same key after a timeout, so a retry doesn't start a second billed run",
          "Run `getEmail`, `getPhoneNumber` and `webResearch` through `service_batch_execute`, even for one person; `service_execute` refuses them",
          "Check `credits` before a paid run, and call `service_inspect` for a service's `thingsToKnow` and credit cost before executing it",
          "On 429 wait for Retry-After; at most 5 runs execute per organisation, so a queued run starts on its own and shouldn't be created again"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "F",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 32
          }
        ],
        "editorialScores": {
          "ergonomics": 75,
          "maintenance": 5,
          "payments": 30,
          "reliability": 45,
          "schema": 82,
          "security": 23,
          "transparency": 43
        },
        "provenanceScore": 54,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl -s https://api.retriever.run/credits -H \"Authorization: Bearer $RETRIEVER_API_KEY\"",
        "claudeCode": "claude mcp add --transport http --scope user retriever https://api.retriever.run/mcp",
        "config": {
          "mcpServers": {
            "retriever": {
              "url": "https://api.retriever.run/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/lead.search",
        "tool": "https://letme.dev/retriever"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Credit, Starter plan",
          "unit": "credit",
          "usd": 0.0134,
          "note": "$80 a month billed quarterly for 6,000 credits"
        },
        {
          "item": "Work email found",
          "unit": "tx",
          "usd": 0.06,
          "note": "4 to 12 credits, about $0.06 to $0.18 per the pricing page"
        },
        {
          "item": "Phone number found",
          "unit": "tx",
          "usd": 0.22,
          "note": "15 to 60 credits, about $0.22 to $0.89 per the pricing page"
        },
        {
          "item": "LinkedIn sender",
          "unit": "account-month",
          "usd": 10,
          "note": "Per connected LinkedIn account"
        }
      ],
      "provenance": {
        "legalEntity": "Retriever",
        "domain": "retriever.run",
        "domainRegistered": "2026-04-07",
        "endpointOnVendorDomain": true,
        "terms": "https://retriever.run/terms",
        "privacy": "https://retriever.run/privacy",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-11-18",
        "notes": [
          "The terms and privacy policy, both last updated 30 August 2026, name the entity only as Retriever, choose French law and the Paris courts, and give emma@retriever.run as the contact. No company number, address or register entry was found; the French company register (annuaire-entreprises.data.gouv.fr) answered with a bot check, so it wasn't searched.",
          "retriever.run/robots.txt allows every crawler. docs.retriever.run publishes rules that didn't close the pages read. The site carries a content-signals preamble in robots.txt with no ai-input=no.",
          "RDAP gives retriever.run a registration date of 7 April 2026.",
          "/.well-known/security.txt answered 404. No status page or changelog is linked from the site or the docs.",
          "The privacy policy names Vercel, Railway, Supabase, Anthropic and OpenAI as examples of subprocessors and says personal data isn't sold. It doesn't cover the LinkedIn and email accounts customers connect, or the data providers named on the pricing page."
        ],
        "score": 54
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/retriever.json",
      "live": {
        "slug": "retriever",
        "probe": {
          "target": "https://api.retriever.run/mcp",
          "method": "get",
          "lastAt": "2026-11-18T21:51:12.571692585Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 193,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 201,
          "p95ms24h": 385,
          "samples24h": 172,
          "samples30d": 172,
          "days": [
            {
              "date": "2026-11-18",
              "probes": 172,
              "ok": 172
            }
          ],
          "since": "2026-11-18T04:42:08.539827226Z"
        },
        "securityTxt": {
          "url": "https://retriever.run/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:31:40.595836687Z"
        },
        "llmsTxt": {
          "url": "https://docs.retriever.run/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:15:58.22750683Z"
        },
        "pages": [
          {
            "url": "https://retriever.run/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T21:52:43.303154652Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "df5f8e8262ec"
          },
          {
            "url": "https://retriever.run/terms",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-18T21:52:45.492573613Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "7d5324c0992b"
          }
        ],
        "updatedAt": "2026-11-18T21:52:45.492573613Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "sinceWatching": true,
        "best": 0
      }
    },
    "edges": [
      {
        "by": 32,
        "category": "schema",
        "leads": "retriever",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "Readings are per the 8 October check, not re-read on 4 November 2026, since FuseAI's terms bar automated extraction from its website and docs. Contract line 0 (was 22 of 25). The MCP tool schemas were never read, because tools/list needs a signed-in account, and the docs only say every tool ships one. The 8 October reading leaned on the REST API's OpenAPI file, a separate surface, and no reading records a docs page that shows or links it, so it is struck for this line, as jambonz's and stable-audio's were. llms.txt, Markdown twins of every page and a skill file (10). The tool reference shows descriptions that state purpose, the preferred tool for a job and when a destructive tool may be called (16 of 20). Enum lookup tools such as `get_company_search_enums` exist, but input constraints were not read first-hand (9 of 15). Error results are documented with codes and two JSON examples, plus four plain-text failures, and the docs say the codes do not always match the REST catalogue (12 of 15). No changelog was found and the docs say the server does not announce changes to the tool list. The tool reference is dated 7 October 2026 (3 of 15). 0 + 10 + 16 + 9 + 12 + 3 = 50.",
          "b": "OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25). llms.txt and a Markdown copy of every docs page (10). The tool catalogue says when to use most tools and when not to (cancels only on the user's request, slow services only in a batch) (17 of 20). The OpenAPI file has enums and required fields; the MCP input schemas weren't read, since tools/list needs a key (11 of 15). An errors page with stable codes and the action for each, plus examples in the docs (14 of 15). Routes are versioned under /v1 but there's no public changelog (5 of 15)."
        },
        "scores": {
          "a": 50,
          "b": 82
        }
      },
      {
        "by": 30,
        "category": "maintenance",
        "leads": "fuse-mcp",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "Readings are per the 8 October check, not re-read on 4 November 2026. The tool reference is dated 7 October 2026 and records the October 2026 rebuild of the tool list, within 30 days today (30); it drops to 20 after 6 November unless a newer dated change appears. No changelog or release notes found, so three dated entries in 90 days could not be shown (0). No public changelog or issue tracker. Support is by email at support@fuseai.com, not tested (5 of 15). No readable registry page names the server and no official SDK was found (0). No package to assess (0 of 10). 30 + 0 + 5 + 0 + 0 = 35.",
          "b": "No changelog, release notes or dated API change found, and the docs carry no dates; the blog's posts are marketing articles, not release notes (0 and 0). Support is an email address and a demo booking, with no public changelog or community channel that answers (5 of 25). Not in the official MCP registry and no official SDK (0). No package to check (0). The domain dates from 7 April 2026."
        },
        "scores": {
          "a": 35,
          "b": 5
        }
      },
      {
        "by": 20,
        "category": "security",
        "leads": "fuse-mcp",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "Readings are per the 8 October check, not re-read on 4 November 2026. OAuth authorisation code with PKCE and dynamic client registration, one-hour access tokens and rotating refresh tokens. The only scope is `mcp:tools`, so every connection has the user's full permissions (22 of 30). There is no read-only mode. Destructive tool descriptions tell the model to get the user's confirmation, but the server enforces none of this and changes apply at once. Billing, API key and team-removal tools are left out (8 of 20). Tools return inbox email, LinkedIn messages and scraped web pages, and the only guidance found is to connect trusted clients and keep approval prompts on (4 of 15). Audit logging is listed for Enterprise and a credit usage ledger exists, with no per-call log for MCP documented (4 of 15). Programme 7 to 5. The home page lists SOC 2 Type I and CASA Tier 2 with no report, trust centre, security.txt, disclosure policy or bug bounty found, and a bare certification claim with no report or reporting route scores 5, as for zamp. 22 + 8 + 4 + 4 + 5 = 43.",
          "b": "The MCP server's OAuth 2.1 issues an ordinary API key, and keys have no scopes or expiry and work as their creator in that organisation: plain revocable keys (20), less 10 because the MCP docs offer the key in the URL as `?api_key=` (10 of 30). No read-only mode; destructive hints and explicit-request instructions on cancels and deletes, and the outreach toolset can be switched off (8 of 20). The tools return scraped pages, social posts and inbox replies, with no prompt-injection guidance found (0). Credit charges per run and a credits ledger by source, but no audit log documented (5 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0)."
        },
        "scores": {
          "a": 43,
          "b": 23
        }
      },
      {
        "by": 18,
        "category": "ergonomics",
        "leads": "retriever",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "Readings are per the 8 October check, not re-read on 4 November 2026. 290 tools and about half a megabyte of definitions, with no toolsets, dynamic loading or read-only subset. The docs warn that some clients pass only the first 40 tools (5 of 25). List reads return a `data` array with `pagination`, searches return a scroll token or cursor, and tools take limits and filters (18 of 20). Rejected calls set `isError` and return codes such as `TOOL_ARGUMENT_VALIDATION_FAILED` with the missing field named. Other failures are short plain text (15 of 20). The docs say every tool carries `readOnlyHint` or `destructiveHint`, which we could not read from the server. No idempotency keys, and sends are not marked destructive (14 of 20). No official SDK found, and most changes need an id looked up first (5 of 15). 5 + 18 + 15 + 14 + 5 = 57.",
          "b": "67 tools in the catalogue (5), with 5 back because the outreach tools are a toolset shown only when the organisation has a sender and switchable in settings (10 of 25). Limit, offset and cursor pagination, up to 1,000 rows a call, and the first 20 rows returned with a finished run (18 of 20). Stable error codes with the action to take (20). Idempotency-Key on run creation, and readOnlyHint, destructiveHint and idempotentHint on the tools (20). Few required parameters (a run needs only a prompt), but no official SDK, only a Node client in a recipe (7 of 15)."
        },
        "scores": {
          "a": 57,
          "b": 75
        }
      },
      {
        "by": 15,
        "category": "payments",
        "leads": "fuse-mcp",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "Readings are per the 8 October check, not re-read on 4 November 2026. No x402, MPP or L402 (0). Plan prices and the credit cost of each action are public, and `get_credit_prices` returns them. Top-up prices are shown only in the app and the Free allowance is stated two ways (15 of 20). A Free plan exists at $0. The Solo plan card is where MCP is listed, and we could not confirm that Free includes it or that signup needs no card (15 of 20). A person signs in through a browser to approve each connection (0). 0 + 15 + 15 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.",
          "b": "No x402, MPP or L402 (0). Credits per action and the dollar price per credit ($0.0134 on Starter) are public without a login (30). No free tier or trial without a card found; the terms say only that free tiers may be offered (0). Access needs a browser signup and a subscription, so an agent can't onboard itself (0)."
        },
        "scores": {
          "a": 45,
          "b": 30
        }
      },
      {
        "by": 5,
        "category": "reliability",
        "leads": "retriever",
        "name": "Reliability",
        "reasons": {
          "a": "Graded as a hosted service. FuseAI's terms bar automated systems or scripts from extracting content from the Services, which they define to include the website, so every fuseai.com page keeps its 8 October reading, not re-read on 4 November 2026. No status page is linked from the site, the docs or the sitemap (0). No readable incident history (5). MCP limits are published at 60 requests a minute and 5,000 a day per user (15). The server answers 429 with `RATE_LIMIT_EXCEEDED` and the docs say to back off and retry. No `Retry-After` is documented for the MCP server and there are no idempotency keys, so backoff guidance alone (10). No SLA found (0). The server carries no beta or preview label (10). 0 + 5 + 15 + 10 + 0 + 10 = 40.",
          "b": "No status page found, linked from neither the site nor the docs (0), so no incident history to read (5). Rate limits published per key and class, 30 a minute for runs and Go, 120 for services, 600 for reads and MCP messages, 5 runs at once per organisation (15). 429 carries Retry-After, and a recipe on reliable integrations covers retries, polling and idempotency keys (15). The pricing page lists \"Dedicated support \u0026 SLA\" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10)."
        },
        "scores": {
          "a": 40,
          "b": 45
        }
      }
    ],
    "facts": [
      {
        "a": "MCP server",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "FuseAI, LLC",
        "b": "Retriever",
        "name": "Vendor"
      },
      {
        "a": "https://mcp.fuseai.com",
        "b": "https://api.retriever.run/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Paid",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary hosted service under FuseAI's terms of service. No public source repository found",
        "b": "none",
        "name": "Licence"
      },
      {
        "a": "290",
        "b": "67",
        "name": "Tools exposed"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-07",
        "b": "none",
        "name": "Last release"
      },
      {
        "a": "2026-07-01",
        "b": "2026-08-30",
        "name": "Terms last updated"
      },
      {
        "a": "2026-07-01",
        "b": "2026-08-30",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      }
    ],
    "faq": [
      {
        "answer": "Fuse MCP scores 46.2 (D) on agent readiness against Retriever's 32 (F), and leads in 4 of 7 scored categories. Retriever leads on reliability, schema \u0026 documentation and agent ergonomics.",
        "question": "Which is better for AI agents, Fuse MCP or Retriever?"
      },
      {
        "answer": "Fuse MCP uses an OAuth sign-in. Retriever takes an API key or an OAuth sign-in.",
        "question": "Do Fuse MCP and Retriever need an API key?"
      },
      {
        "answer": "Yes. Fuse MCP has a hosted endpoint at https://mcp.fuseai.com and Retriever at https://api.retriever.run/mcp.",
        "question": "Can an agent call Fuse MCP and Retriever without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Security \u0026 auth, 43 against 23",
          "Payments \u0026 pricing, 45 against 30",
          "Maintenance \u0026 community, 35 against 5"
        ],
        "also": [
          "No incidents deducted, where Retriever loses 15 points for them"
        ],
        "goodFor": "Suited to a salesperson or founder who wants an assistant to build prospect lists, enrich them and run email and LinkedIn outreach inside one Fuse account.",
        "slug": "fuse-mcp",
        "watchFor": "The only OAuth scope is `mcp:tools`, so a connection can do everything its user can, including sending email and LinkedIn messages"
      },
      {
        "aheadOn": [
          "Reliability, 45 against 40",
          "Schema \u0026 documentation, 82 against 50",
          "Agent ergonomics, 75 against 57"
        ],
        "also": null,
        "goodFor": "A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.",
        "slug": "retriever",
        "watchFor": "Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted"
      }
    ],
    "history": {
      "fuse-mcp": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.9,
          "from": 44.3,
          "fromGrade": "E",
          "to": 46.2,
          "toGrade": "D"
        },
        {
          "causes": [
            "correction"
          ],
          "date": "2026-11-04",
          "delta": -3.9,
          "from": 48.2,
          "fromGrade": "D",
          "to": 44.3,
          "toGrade": "E"
        },
        {
          "causes": [
            "method"
          ],
          "date": "2026-10-27",
          "delta": 0.3,
          "from": 47.9,
          "fromGrade": "D",
          "to": 48.2,
          "toGrade": "D"
        }
      ],
      "retriever": null
    },
    "job": {
      "capability": "lead.search",
      "name": "Lead search"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/apollo-vs-fuse-mcp.json",
        "title": "Apollo API + MCP vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/apollo-vs-retriever.json",
        "title": "Apollo API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-fuse-mcp.json",
        "title": "Clay vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/clay-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-retriever.json",
        "title": "Clay vs Retriever",
        "url": "https://www.anchorterminal.com/compare/clay-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-fuse-mcp.json",
        "title": "Coresignal API + MCP vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-retriever.json",
        "title": "Coresignal API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crustdata-vs-fuse-mcp.json",
        "title": "Crustdata API + MCP vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/crustdata-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crustdata-vs-retriever.json",
        "title": "Crustdata API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/crustdata-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dievio-vs-fuse-mcp.json",
        "title": "Dievio vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/dievio-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dievio-vs-retriever.json",
        "title": "Dievio vs Retriever",
        "url": "https://www.anchorterminal.com/compare/dievio-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/enrich-layer-vs-fuse-mcp.json",
        "title": "Enrich Layer API + MCP vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/enrich-layer-vs-retriever.json",
        "title": "Enrich Layer API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-fuse-mcp.json",
        "title": "Explorium AgentSource vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-retriever.json",
        "title": "Explorium AgentSource vs Retriever",
        "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-fuse-mcp.json",
        "title": "FullEnrich API + MCP vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-retriever.json",
        "title": "FullEnrich API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-gojiberry.json",
        "title": "Fuse MCP vs Gojiberry",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-gojiberry"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-hunter.json",
        "title": "Fuse MCP vs Hunter API + MCP",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-hunter"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-leadmagic.json",
        "title": "Fuse MCP vs LeadMagic API + MCP",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-leadmagic"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-lusha.json",
        "title": "Fuse MCP vs Lusha API + MCP",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-lusha"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-people-data-labs.json",
        "title": "Fuse MCP vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-prospeo.json",
        "title": "Fuse MCP vs Prospeo API + MCP",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-prospeo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-rocketreach.json",
        "title": "Fuse MCP vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-zoominfo.json",
        "title": "Fuse MCP vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-zoominfo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gojiberry-vs-retriever.json",
        "title": "Gojiberry vs Retriever",
        "url": "https://www.anchorterminal.com/compare/gojiberry-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadmagic-vs-retriever.json",
        "title": "LeadMagic API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/leadmagic-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lusha-vs-retriever.json",
        "title": "Lusha API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/lusha-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/people-data-labs-vs-retriever.json",
        "title": "People Data Labs vs Retriever",
        "url": "https://www.anchorterminal.com/compare/people-data-labs-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/prospeo-vs-retriever.json",
        "title": "Prospeo API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/prospeo-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/retriever-vs-rocketreach.json",
        "title": "Retriever vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/retriever-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/retriever-vs-zoominfo.json",
        "title": "Retriever vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/retriever-vs-zoominfo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-fuse-mcp.json",
        "title": "Clearbit vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-retriever.json",
        "title": "Clearbit vs Retriever",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/databar-vs-fuse-mcp.json",
        "title": "Databar vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/databar-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/databar-vs-retriever.json",
        "title": "Databar vs Retriever",
        "url": "https://www.anchorterminal.com/compare/databar-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-fuse-mcp.json",
        "title": "Dropcontact API + MCP vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-retriever.json",
        "title": "Dropcontact API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullcontact-vs-fuse-mcp.json",
        "title": "FullContact vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/fullcontact-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullcontact-vs-retriever.json",
        "title": "FullContact vs Retriever",
        "url": "https://www.anchorterminal.com/compare/fullcontact-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/retriever-vs-zerobounce.json",
        "title": "Retriever vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/retriever-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hunter-vs-retriever.json",
        "title": "Hunter API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-zerobounce.json",
        "title": "Fuse MCP vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-zerobounce"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 5,
        "edge": "retriever",
        "fuse-mcp": 40,
        "key": "reliability",
        "name": "Reliability",
        "retriever": 45,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 32,
        "edge": "retriever",
        "fuse-mcp": 50,
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "retriever": 82,
        "weight": 13
      },
      {
        "by": 18,
        "edge": "retriever",
        "fuse-mcp": 57,
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "retriever": 75,
        "weight": 13
      },
      {
        "by": 20,
        "edge": "fuse-mcp",
        "fuse-mcp": 43,
        "key": "security",
        "name": "Security \u0026 auth",
        "retriever": 23,
        "weight": 14
      },
      {
        "by": 15,
        "edge": "fuse-mcp",
        "fuse-mcp": 45,
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "retriever": 30,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 30,
        "edge": "fuse-mcp",
        "fuse-mcp": 35,
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "retriever": 5,
        "weight": 7
      },
      {
        "by": 3,
        "edge": "fuse-mcp",
        "fuse-mcp": 52,
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "retriever": 49,
        "weight": 7
      }
    ],
    "summary": "Fuse MCP scores 46.2 (D) on agent readiness against Retriever's 32 (F), and leads in 4 of 7 scored categories. Retriever leads on reliability, schema \u0026 documentation and agent ergonomics. Both do lead search.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "fuse-mcp": "The server documents 290 tools with read-only and destructive annotations, OAuth with PKCE and dynamic client registration, and published limits of 60 requests a minute. The single `mcp:tools` scope grants everything the user can do, sends happen at once with no undo, and no status page, changelog or security contact was found.",
      "retriever": "Retriever automates outreach from customers' LinkedIn accounts, which LinkedIn's rules forbid. For agents it has an OAuth MCP server, an OpenAPI file, idempotency keys, stable error codes and published credit prices, but no status page, changelog, security contact, free tier or named company behind it."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever",
    "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever.min.md"
  },
  "markdown": "Fuse MCP scores 46.2 (D) on agent readiness against Retriever's 32 (F), and leads in 4 of 7 scored categories. Retriever leads on reliability, schema \u0026 documentation and agent ergonomics. Both do lead search.\n\n- Fuse MCP: grade D, 46.2/100, rank #1257 of 1557. Markdown https://www.anchorterminal.com/tools/fuse-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/fuse-mcp.json\n- Retriever: grade F, 32/100, rank #1455 of 1557. Markdown https://www.anchorterminal.com/tools/retriever.md · JSON https://www.anchorterminal.com/api/v1/tools/retriever.json\n- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md\n- All 253 leads comparisons: https://www.anchorterminal.com/compare/lead-data/index.md\n\n## Which one, for what\n\n### Fuse MCP (D)\n\nGood for: Suited to a salesperson or founder who wants an assistant to build prospect lists, enrich them and run email and LinkedIn outreach inside one Fuse account.\n\nAhead on:\n- Security \u0026 auth, 43 against 23\n- Payments \u0026 pricing, 45 against 30\n- Maintenance \u0026 community, 35 against 5\n\nAlso in its favour:\n- No incidents deducted, where Retriever loses 15 points for them\n\nWatch for: The only OAuth scope is `mcp:tools`, so a connection can do everything its user can, including sending email and LinkedIn messages\n\n### Retriever (F)\n\nGood for: A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.\n\nAhead on:\n- Reliability, 45 against 40\n- Schema \u0026 documentation, 82 against 50\n- Agent ergonomics, 75 against 57\n\nWatch for: Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Retriever +32\n\n- Fuse MCP (50): Readings are per the 8 October check, not re-read on 4 November 2026, since FuseAI's terms bar automated extraction from its website and docs. Contract line 0 (was 22 of 25). The MCP tool schemas were never read, because tools/list needs a signed-in account, and the docs only say every tool ships one. The 8 October reading leaned on the REST API's OpenAPI file, a separate surface, and no reading records a docs page that shows or links it, so it is struck for this line, as jambonz's and stable-audio's were. llms.txt, Markdown twins of every page and a skill file (10). The tool reference shows descriptions that state purpose, the preferred tool for a job and when a destructive tool may be called (16 of 20). Enum lookup tools such as `get_company_search_enums` exist, but input constraints were not read first-hand (9 of 15). Error results are documented with codes and two JSON examples, plus four plain-text failures, and the docs say the codes do not always match the REST catalogue (12 of 15). No changelog was found and the docs say the server does not announce changes to the tool list. The tool reference is dated 7 October 2026 (3 of 15). 0 + 10 + 16 + 9 + 12 + 3 = 50.\n- Retriever (82): OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25). llms.txt and a Markdown copy of every docs page (10). The tool catalogue says when to use most tools and when not to (cancels only on the user's request, slow services only in a batch) (17 of 20). The OpenAPI file has enums and required fields; the MCP input schemas weren't read, since tools/list needs a key (11 of 15). An errors page with stable codes and the action for each, plus examples in the docs (14 of 15). Routes are versioned under /v1 but there's no public changelog (5 of 15).\n\n### Maintenance \u0026 community: Fuse MCP +30\n\n- Fuse MCP (35): Readings are per the 8 October check, not re-read on 4 November 2026. The tool reference is dated 7 October 2026 and records the October 2026 rebuild of the tool list, within 30 days today (30); it drops to 20 after 6 November unless a newer dated change appears. No changelog or release notes found, so three dated entries in 90 days could not be shown (0). No public changelog or issue tracker. Support is by email at support@fuseai.com, not tested (5 of 15). No readable registry page names the server and no official SDK was found (0). No package to assess (0 of 10). 30 + 0 + 5 + 0 + 0 = 35.\n- Retriever (5): No changelog, release notes or dated API change found, and the docs carry no dates; the blog's posts are marketing articles, not release notes (0 and 0). Support is an email address and a demo booking, with no public changelog or community channel that answers (5 of 25). Not in the official MCP registry and no official SDK (0). No package to check (0). The domain dates from 7 April 2026.\n\n### Security \u0026 auth: Fuse MCP +20\n\n- Fuse MCP (43): Readings are per the 8 October check, not re-read on 4 November 2026. OAuth authorisation code with PKCE and dynamic client registration, one-hour access tokens and rotating refresh tokens. The only scope is `mcp:tools`, so every connection has the user's full permissions (22 of 30). There is no read-only mode. Destructive tool descriptions tell the model to get the user's confirmation, but the server enforces none of this and changes apply at once. Billing, API key and team-removal tools are left out (8 of 20). Tools return inbox email, LinkedIn messages and scraped web pages, and the only guidance found is to connect trusted clients and keep approval prompts on (4 of 15). Audit logging is listed for Enterprise and a credit usage ledger exists, with no per-call log for MCP documented (4 of 15). Programme 7 to 5. The home page lists SOC 2 Type I and CASA Tier 2 with no report, trust centre, security.txt, disclosure policy or bug bounty found, and a bare certification claim with no report or reporting route scores 5, as for zamp. 22 + 8 + 4 + 4 + 5 = 43.\n- Retriever (23): The MCP server's OAuth 2.1 issues an ordinary API key, and keys have no scopes or expiry and work as their creator in that organisation: plain revocable keys (20), less 10 because the MCP docs offer the key in the URL as `?api_key=` (10 of 30). No read-only mode; destructive hints and explicit-request instructions on cancels and deletes, and the outreach toolset can be switched off (8 of 20). The tools return scraped pages, social posts and inbox replies, with no prompt-injection guidance found (0). Credit charges per run and a credits ledger by source, but no audit log documented (5 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0).\n\n### Agent ergonomics: Retriever +18\n\n- Fuse MCP (57): Readings are per the 8 October check, not re-read on 4 November 2026. 290 tools and about half a megabyte of definitions, with no toolsets, dynamic loading or read-only subset. The docs warn that some clients pass only the first 40 tools (5 of 25). List reads return a `data` array with `pagination`, searches return a scroll token or cursor, and tools take limits and filters (18 of 20). Rejected calls set `isError` and return codes such as `TOOL_ARGUMENT_VALIDATION_FAILED` with the missing field named. Other failures are short plain text (15 of 20). The docs say every tool carries `readOnlyHint` or `destructiveHint`, which we could not read from the server. No idempotency keys, and sends are not marked destructive (14 of 20). No official SDK found, and most changes need an id looked up first (5 of 15). 5 + 18 + 15 + 14 + 5 = 57.\n- Retriever (75): 67 tools in the catalogue (5), with 5 back because the outreach tools are a toolset shown only when the organisation has a sender and switchable in settings (10 of 25). Limit, offset and cursor pagination, up to 1,000 rows a call, and the first 20 rows returned with a finished run (18 of 20). Stable error codes with the action to take (20). Idempotency-Key on run creation, and readOnlyHint, destructiveHint and idempotentHint on the tools (20). Few required parameters (a run needs only a prompt), but no official SDK, only a Node client in a recipe (7 of 15).\n\n### Payments \u0026 pricing: Fuse MCP +15\n\n- Fuse MCP (45): Readings are per the 8 October check, not re-read on 4 November 2026. No x402, MPP or L402 (0). Plan prices and the credit cost of each action are public, and `get_credit_prices` returns them. Top-up prices are shown only in the app and the Free allowance is stated two ways (15 of 20). A Free plan exists at $0. The Solo plan card is where MCP is listed, and we could not confirm that Free includes it or that signup needs no card (15 of 20). A person signs in through a browser to approve each connection (0). 0 + 15 + 15 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.\n- Retriever (30): No x402, MPP or L402 (0). Credits per action and the dollar price per credit ($0.0134 on Starter) are public without a login (30). No free tier or trial without a card found; the terms say only that free tiers may be offered (0). Access needs a browser signup and a subscription, so an agent can't onboard itself (0).\n\n### Reliability: Retriever +5\n\n- Fuse MCP (40): Graded as a hosted service. FuseAI's terms bar automated systems or scripts from extracting content from the Services, which they define to include the website, so every fuseai.com page keeps its 8 October reading, not re-read on 4 November 2026. No status page is linked from the site, the docs or the sitemap (0). No readable incident history (5). MCP limits are published at 60 requests a minute and 5,000 a day per user (15). The server answers 429 with `RATE_LIMIT_EXCEEDED` and the docs say to back off and retry. No `Retry-After` is documented for the MCP server and there are no idempotency keys, so backoff guidance alone (10). No SLA found (0). The server carries no beta or preview label (10). 0 + 5 + 15 + 10 + 0 + 10 = 40.\n- Retriever (45): No status page found, linked from neither the site nor the docs (0), so no incident history to read (5). Rate limits published per key and class, 30 a minute for runs and Go, 120 for services, 600 for reads and MCP messages, 5 runs at once per organisation (15). 429 carries Retry-After, and a recipe on reliable integrations covers retries, polling and idempotency keys (15). The pricing page lists \"Dedicated support \u0026 SLA\" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10).\n\n## Score by category\n\n| Category | Weight | Fuse MCP | Retriever | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 40 | 45 | Retriever +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 50 | 82 | Retriever +32 |\n| Agent ergonomics | 13% | 57 | 75 | Retriever +18 |\n| Security \u0026 auth | 14% | 43 | 23 | Fuse MCP +20 |\n| Payments \u0026 pricing | 10% | 45 | 30 | Fuse MCP +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 35 | 5 | Fuse MCP +30 |\n| Transparency \u0026 trust | 7% | 52 | 49 | Fuse MCP +3 |\n| Negative events | ≤15 | 0 | -15 | |\n| **Total** | | **46.2 · D** | **32 · F** | |\n\n## Facts side by side\n\n| Fact | Fuse MCP | Retriever |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | FuseAI, LLC | Retriever |\n| Hosted endpoint | `https://mcp.fuseai.com` | `https://api.retriever.run/mcp` |\n| Transports | Streamable HTTP | Streamable HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | Proprietary hosted service under FuseAI's terms of service. No public source repository found | none |\n| Tools exposed | 290 | 67 |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-10-07 | none |\n| Terms last updated | 2026-07-01 | 2026-08-30 |\n| Privacy policy last updated | 2026-07-01 | 2026-08-30 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n\n## How the scores have moved\n\n### Fuse MCP\n\n- +1.9 on 13 November 2026 (E to D): checklist\n- -3.9 on 4 November 2026 (D to E): correction\n- +0.3 on 27 October 2026: checklist\n\n### Retriever\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Fuse MCP.** The server documents 290 tools with read-only and destructive annotations, OAuth with PKCE and dynamic client registration, and published limits of 60 requests a minute. The single `mcp:tools` scope grants everything the user can do, sends happen at once with no undo, and no status page, changelog or security contact was found.\n\n**Retriever.** Retriever automates outreach from customers' LinkedIn accounts, which LinkedIn's rules forbid. For agents it has an OAuth MCP server, an OpenAPI file, idempotency keys, stable error codes and published credit prices, but no status page, changelog, security contact, free tier or named company behind it.\n\n## Before you call either\n\n### Fuse MCP\n\n1. Keep the client's approval prompt on for every tool that is not read-only. Sends, CRM pushes and Slack posts run at once with no undo\n2. Launch a campaign only on an explicit request. Creating one makes a draft, and `update_campaign_status_tool` starts real outreach\n3. Call `get_credits_balance` and `get_credit_prices` first. Every call needs at least 100 credits, and searches cost 2 credits a result\n4. Resolve filter values with `lookup_filter_values` or `get_company_search_enums` before `search_people` or `search_companies`\n5. Start long work with `deep_research_start`, then poll `deep_research_status`. A tool call has 60 seconds, and runs take 5 to 20 minutes\n\n### Retriever\n\n1. Don't enrol leads in a sequence with LinkedIn steps without the user knowing LinkedIn forbids automated activity and can restrict their account\n2. Send an `Idempotency-Key` with each run and replay with the same key after a timeout, so a retry doesn't start a second billed run\n3. Run `getEmail`, `getPhoneNumber` and `webResearch` through `service_batch_execute`, even for one person; `service_execute` refuses them\n4. Check `credits` before a paid run, and call `service_inspect` for a service's `thingsToKnow` and credit cost before executing it\n5. On 429 wait for Retry-After; at most 5 runs execute per organisation, so a queued run starts on its own and shouldn't be created again\n\n## Questions\n\n### Which is better for AI agents, Fuse MCP or Retriever?\n\nFuse MCP scores 46.2 (D) on agent readiness against Retriever's 32 (F), and leads in 4 of 7 scored categories. Retriever leads on reliability, schema \u0026 documentation and agent ergonomics.\n\n### Do Fuse MCP and Retriever need an API key?\n\nFuse MCP uses an OAuth sign-in. Retriever takes an API key or an OAuth sign-in.\n\n### Can an agent call Fuse MCP and Retriever without installing anything?\n\nYes. Fuse MCP has a hosted endpoint at https://mcp.fuseai.com and Retriever at https://api.retriever.run/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"fuse-mcp\", \"b\": \"retriever\"}`. From a terminal: `anchor compare fuse-mcp retriever`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fuse-mcp.json and https://www.anchorterminal.com/api/v1/tools/retriever.json\n\n## Other comparisons with Fuse MCP or Retriever\n\n- [Apollo API + MCP vs Fuse MCP](https://www.anchorterminal.com/compare/apollo-vs-fuse-mcp.md)\n- [Apollo API + MCP vs Retriever](https://www.anchorterminal.com/compare/apollo-vs-retriever.md)\n- [Clay vs Fuse MCP](https://www.anchorterminal.com/compare/clay-vs-fuse-mcp.md)\n- [Clay vs Retriever](https://www.anchorterminal.com/compare/clay-vs-retriever.md)\n- [Coresignal API + MCP vs Fuse MCP](https://www.anchorterminal.com/compare/coresignal-vs-fuse-mcp.md)\n- [Coresignal API + MCP vs Retriever](https://www.anchorterminal.com/compare/coresignal-vs-retriever.md)\n- [Crustdata API + MCP vs Fuse MCP](https://www.anchorterminal.com/compare/crustdata-vs-fuse-mcp.md)\n- [Crustdata API + MCP vs Retriever](https://www.anchorterminal.com/compare/crustdata-vs-retriever.md)\n- [Dievio vs Fuse MCP](https://www.anchorterminal.com/compare/dievio-vs-fuse-mcp.md)\n- [Dievio vs Retriever](https://www.anchorterminal.com/compare/dievio-vs-retriever.md)\n- [Enrich Layer API + MCP vs Fuse MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-fuse-mcp.md)\n- [Enrich Layer API + MCP vs Retriever](https://www.anchorterminal.com/compare/enrich-layer-vs-retriever.md)\n- [Explorium AgentSource vs Fuse MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-fuse-mcp.md)\n- [Explorium AgentSource vs Retriever](https://www.anchorterminal.com/compare/explorium-agentsource-vs-retriever.md)\n- [FullEnrich API + MCP vs Fuse MCP](https://www.anchorterminal.com/compare/fullenrich-vs-fuse-mcp.md)\n- [FullEnrich API + MCP vs Retriever](https://www.anchorterminal.com/compare/fullenrich-vs-retriever.md)\n- [Fuse MCP vs Gojiberry](https://www.anchorterminal.com/compare/fuse-mcp-vs-gojiberry.md)\n- [Fuse MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/fuse-mcp-vs-hunter.md)\n- [Fuse MCP vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/fuse-mcp-vs-leadmagic.md)\n- [Fuse MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/fuse-mcp-vs-lusha.md)\n- [Fuse MCP vs People Data Labs](https://www.anchorterminal.com/compare/fuse-mcp-vs-people-data-labs.md)\n- [Fuse MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/fuse-mcp-vs-prospeo.md)\n- [Fuse MCP vs RocketReach API](https://www.anchorterminal.com/compare/fuse-mcp-vs-rocketreach.md)\n- [Fuse MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/fuse-mcp-vs-zoominfo.md)\n- [Gojiberry vs Retriever](https://www.anchorterminal.com/compare/gojiberry-vs-retriever.md)\n- [LeadMagic API + MCP vs Retriever](https://www.anchorterminal.com/compare/leadmagic-vs-retriever.md)\n- [Lusha API + MCP vs Retriever](https://www.anchorterminal.com/compare/lusha-vs-retriever.md)\n- [People Data Labs vs Retriever](https://www.anchorterminal.com/compare/people-data-labs-vs-retriever.md)\n- [Prospeo API + MCP vs Retriever](https://www.anchorterminal.com/compare/prospeo-vs-retriever.md)\n- [Retriever vs RocketReach API](https://www.anchorterminal.com/compare/retriever-vs-rocketreach.md)\n- [Retriever vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/retriever-vs-zoominfo.md)\n- [Clearbit vs Fuse MCP](https://www.anchorterminal.com/compare/clearbit-vs-fuse-mcp.md)\n- [Clearbit vs Retriever](https://www.anchorterminal.com/compare/clearbit-vs-retriever.md)\n- [Databar vs Fuse MCP](https://www.anchorterminal.com/compare/databar-vs-fuse-mcp.md)\n- [Databar vs Retriever](https://www.anchorterminal.com/compare/databar-vs-retriever.md)\n- [Dropcontact API + MCP vs Fuse MCP](https://www.anchorterminal.com/compare/dropcontact-vs-fuse-mcp.md)\n- [Dropcontact API + MCP vs Retriever](https://www.anchorterminal.com/compare/dropcontact-vs-retriever.md)\n- [FullContact vs Fuse MCP](https://www.anchorterminal.com/compare/fullcontact-vs-fuse-mcp.md)\n- [FullContact vs Retriever](https://www.anchorterminal.com/compare/fullcontact-vs-retriever.md)\n- [Retriever vs ZeroBounce](https://www.anchorterminal.com/compare/retriever-vs-zerobounce.md)\n- [Hunter API + MCP vs Retriever](https://www.anchorterminal.com/compare/hunter-vs-retriever.md)\n- [Fuse MCP vs ZeroBounce](https://www.anchorterminal.com/compare/fuse-mcp-vs-zerobounce.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Fuse MCP vs Retriever",
        "url": ""
      }
    ],
    "description": "Fuse MCP scores 46.2 (D) to Retriever's 32 (F) for lead search. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Fuse MCP D 46.2",
      "Retriever F 32",
      "scores"
    ],
    "h1": "Fuse MCP vs Retriever",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/fuse-mcp-vs-retriever",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Fuse MCP vs Retriever for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever"
  },
  "tokens": {
    "markdown": 5100,
    "slim": 1080
  },
  "version": 1
}
