# Dievio vs Fuse MCP (slim)

> Fuse MCP scores 48.2 (D) to Dievio's 43 (E) for lead search. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/dievio-vs-fuse-mcp.md (~6,350 tokens) · this version ~4,080 tokens · JSON https://www.anchorterminal.com/compare/dievio-vs-fuse-mcp.json · canonical https://www.anchorterminal.com/compare/dievio-vs-fuse-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-10-31
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Fuse MCP scores 48.2 (D) on agent readiness against Dievio's 43 (E), and leads in 4 of 7 scored categories. Dievio leads on agent ergonomics, security & auth and payments & pricing. Both do lead search.

- Dievio: E 43, rank #1090 of 1245 · https://www.anchorterminal.com/tools/dievio.min.md
- Fuse MCP: D 48.2, rank #1002 of 1245 · https://www.anchorterminal.com/tools/fuse-mcp.min.md
- Dievio, good for Agents building small prospect lists by title, seniority, department, location, company size and industry at a low published price per lead, previewing the count for free first, and handing the user a CSV, JSON or JSONL file from a shared list without opening the dashboard. Ahead on Agent ergonomics, 63 against 57; Security & auth, 56 against 45; Payments & pricing, 35 against 30. Also Free to start without a card.
- Fuse MCP, good 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. Ahead on Reliability, 40 against 28; Schema & documentation, 72 against 50; Maintenance & community, 35 against 28; Transparency & trust, 52 against 27.

| Category | Dievio | Fuse MCP |
| --- | --- | --- |
| Reliability (16%) | 28 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 50 | 72 |
| Agent ergonomics (13%) | 63 | 57 |
| Security & auth (14%) | 56 | 45 |
| Payments & pricing (10%) | 35 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 28 | 35 |
| Transparency & trust (7%) | 27 | 52 |

| Fact (where they differ) | Dievio | Fuse MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Dievio | FuseAI, LLC |
| Hosted endpoint | `https://dievio.com/api/public` | `https://mcp.fuseai.com` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Licence | Proprietary hosted service under Dievio's Terms of Service (last updated 31 October 2026). No source is published; the only public code is a third-party MIT OpenClaw skill and an n8n template on GitHub | Proprietary hosted service under FuseAI's terms of service. No public source repository found |
| Tools exposed | 30 | 290 |
| Read-only variant documented | no | yes |
| Last release | none | 2026-10-07 |
| Terms last updated | not read yet | 2026-07-01 |
| Privacy policy last updated | not read yet | 2026-07-01 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |

Why the edge:
- Transparency & trust, Fuse MCP +25: Dievio 27 (Closed service. The terms (last updated 31 October 2026) cover use, credits, connected agents, a 30-day refund and availability in about 300 words but name no legal entity, address, governing law or jurisdiction, so the contracting party is unknown (8 of 30). The privacy policy (31 October 2026) lists the categories processed, the purposes, recipients by category, the agent connection data, and the access periods (authorization requests 10 minutes, codes 5, access tokens an hour, refresh 30 days, export links 15 minutes), says lead search uses Dievio's own contact database without saying where records are collected from, lets people in the database ask for access, correction, deletion or suppression by email, keeps records for as long as needed with no periods, and agrees with the terms and the docs on credits, revocation and link expiry; no DPA was found (14 of 30). No deprecation policy or notices; the terms allow the service to change at any time, and plan allowances and API prices changed between the 20 May and 31 October 2026 copies of the pricing pages with no dated notice (0 of 20). Service providers are named by category only (hosting, databases, authentication, contact processing, analytics, email delivery, payments), with no names, locations or transfer basis (4 of 20). 8+14+0+4 = 26.); Fuse MCP 52 (Closed service with published terms of service, last updated 1 July 2026, naming FuseAI, LLC (15). The privacy policy of the same date is general. Retention is as long as necessary with no periods, and no DPA or subprocessor list was found. It says Google Workspace data is not used to train AI models and points to a Do Not Sell or Share tool (10 of 30). No deprecation policy. The docs record the October 2026 removal of the earlier tools and that the earlier server URL keeps working (5 of 20). The docs name 39 external data providers. Hosting, data locations and subprocessors are not disclosed (6 of 20).)
- Schema & documentation, Fuse MCP +22: Dievio 50 (API reading, with the MCP server described. No OpenAPI or other machine-readable contract for the REST API; the MCP tool reference says clients discover exact input schemas through tools/list, that unknown fields and unlisted arguments are rejected, and the server publishes a dievio://schema/search-filters JSON resource, but no session was opened to read them (10 of 25). llms.txt and llms-full.txt on docs.dievio.com, generated on each build, plus llms.txt, pricing.md and product.md on dievio.com (10). The MCP reference says what each tool does, which tools are free, which scope each needs, when to prefer export_list_file over export_list and how to retry; the REST pages say what each endpoint returns and little about when to use search against lookup, and the MCP page says a preview does not unlock contacts and a count is not a guaranteed result (12 of 20). Filters are typed as strings, string arrays, booleans and integers with enumerations listed for seniority, department, employee size, business model, salary and email_status, bounds on page, limit, max_results and array length, and UUID ids; industries and locations are examples only, the funding dates are a year over REST and an ISO date over MCP, and the contact object for add_leads_to_list carries a free JSON lead_data field (10 of 15). curl examples with example responses for both REST endpoints, a pagination loop and six MCP worked prompts; errors are four status codes with one line each and no documented body, and the MCP error shape is not shown (8 of 15). No version in the path (/api/public), no changelog or release notes on either host, and plan allowances and API prices changed between the May and October 2026 copies of the pricing pages with no dated notice (0 of 15). 10+10+12+10+8+0 = 50.); Fuse MCP 72 (The docs say every tool ships a description and an input schema, about half a megabyte in all. We could not call tools/list without an account, so the schemas themselves were not read. The REST API beside it has a public OpenAPI 3.1 spec with 146 operations (22 of 25). 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. 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).)
- Reliability, Fuse MCP +12: Dievio 28 (Hosted reading, for the REST API with the MCP server it shares a database with. No public status page was found. None is linked from the docs or the footer, https://dievio.com/status answers 404 and status.dievio.com does not resolve (0). No readable incident history, so the floor (5). No rate limit is published for the REST API or the MCP tools. The only numbers are the export cap of 10 download starts a minute per connection and 100,000 contacts a file, the OAuth timers and input bounds such as 500 LinkedIn URLs a call, and the privacy policy mentions hashed rate-limit keys without a figure (5 of 15). No 429 or Retry-After is documented, and the REST errors are 401, 402, 500 and 502 with no retry guidance; every MCP mutation takes a request_id UUID replayed when retried with identical arguments, the workflows page says never to repeat a paid lookup with a new ID and to reconcile against the job list first, and a low balance returns fewer rows rather than failing, while a retried REST search has no idempotency key and is charged again (8 of 15). No SLA. The terms (last updated 31 October 2026) say uptime is not guaranteed and the service may change at any time (0). The REST API and the 30-tool MCP server carry no beta label, though the search response documents `search_id` as currently null and `counting` as currently false, and the server is unversioned (10). 0+5+5+8+0+10 = 28.); Fuse MCP 40 (Graded as a hosted service. No status page is linked from the site, the docs or the sitemap, and status.fuseai.com did not connect from our network (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, and long jobs return at once and are polled. No `Retry-After` is documented for the MCP server, there are no idempotency keys, and the docs say changes have no undo (10 of 15). No SLA found (0). The server carries no beta or preview label, although its tool list was replaced in October 2026 (10).)
- Security & auth, Dievio +11: Dievio 56 (MCP uses OAuth with the authorization code flow, PKCE S256, dynamic registration of public clients, refresh tokens of 30 days, a revocation endpoint and six scopes, revoked per connection on the dashboard; REST uses a plain API key from the dashboard as a bearer or X-API-Key header, with no documented scopes, rotation, expiry or revocation, and nothing documents a secret in a query string (25 of 30). mcp:read is the required baseline and cannot spend credits, leads:search, lists:write, leads:export and team:manage are separate consents, team:manage works for the owner only, the permissions page asks agents to confirm before deleting saved data and to invite or remove people only when asked, and the terms ask users to review filters and the maximum result count before authorising a paid operation; nothing asks for confirmation inside the server and REST keys have no least-privilege mode (16 of 20). Returned records are third-party contact data, and the permissions page says to treat names, descriptions, URLs and other field values as data rather than instructions, with no further mitigation (8 of 15). get_account reports the selected account, permissions and balances, list_search_jobs lists recent jobs, the dashboard lists and revokes each connection, and the privacy policy says operation results are kept to prevent duplicate actions; no audit log or per-call record is exposed to the operator (7 of 15). No security.txt on either host (404), no disclosure policy, bug bounty, SOC 2 or ISO 27001 (0 of 20). 25+16+8+7+0 = 56.); Fuse MCP 45 (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 and launch tools tell it to confirm first, but the server enforces none of this and changes apply at once. Billing, API key and team-removal tools are left out, as are tools that take a password or key (8 of 20). Tools return inbox email, LinkedIn messages and scraped web pages. The only guidance found is to connect trusted clients and keep approval prompts on (4 of 15). Audit logging is listed for Enterprise on the pricing page, and a credit usage ledger exists. No per-call log for MCP is documented (4 of 15). The home page lists SOC 2 Type I and CASA Tier 2 with no report or trust centre found. No security.txt, disclosure policy or bug bounty found (7 of 20).)
- Maintenance & community, Fuse MCP +7: Dievio 28 (Closed service with no changelog, release notes or version numbers. The latest dated changes on the vendor's pages are the terms and privacy policy of 31 October 2026, which describe the agent integration, token lifetimes and export expiry, and blog posts of 21 and 30 October 2026 on API billing; the MCP server, absent from the February and May 2026 archived copies, carries no date, and the API landing pages say content reviewed May 2026 (20 of 30). No release record, so no three dated entries in 90 days; 84 dated blog posts from 29 March to 30 October 2026 are articles, not releases (0). Support is one address, support@dievio.com, with email support on Starter and priority support on Growth; no public changelog, community channel, forum or issue tracker, and the Fazier launch page's comments are from other makers (3 of 15). Not in the official MCP registry and no official SDKs (0). No packages to judge (5 of 10). 20+0+3+0+5 = 28.); Fuse MCP 35 (The tool reference is dated 7 October 2026 and the tool list was rebuilt in October 2026 (30). 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, with Docs and community on Free and email support on paid plans. We did not test it (5 of 15). Not in the official MCP registry. Searches for `fuse` and `tryfuse` returned none of the vendor's, and the `fuseai` search timed out twice. No official SDK found (0). No package to assess (0 of 10).)
- Agent ergonomics, Dievio +6: Dievio 63 (API reading. REST responses are sized with _per_page (default 25), max_results, include_emails, include_phones, _include_raw to drop the raw object and email_status; the MCP server lists 30 tools with no toolsets or read-only subset, previews mask contact fields and limit runs 1 to 500 (18 of 25). Page-based pagination with has_more and next_page over REST, offset and limit with next_offset over MCP, 20 filters, max_results caps and column selection on exports (20). Errors are 401, 402, 500 and 502 as status codes with one-line meanings and no error body, and a balance below the page size returns fewer rows with success true, which an agent must detect from count; MCP job errors are read from get_search_job (8 of 20). request_id on every MCP mutation with replay semantics, asynchronous searches polled by job id, save_search_results deduplicated by list, job and position, and only queued jobs cancellable; the REST search has no idempotency key and a repeat is charged, and readOnlyHint and destructiveHint are not documented (10 of 20). Every filter is optional with defaults for page size and max_results, and the MCP tools need only filters and a request_id; no official SDK or CLI, only a third-party MIT OpenClaw skill and an n8n template on GitHub (7 of 15). 18+20+8+10+7 = 63.); Fuse MCP 57 (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, which matters less for an MCP server, and most changes need an id looked up first (5 of 15).)