Dievio vs FullContact

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.

FullContact 62

Graded with the hosted lines on the MCP server and the REST API behind it. A public status page at status.fullcontact.com on Pulsetic (20). It renders with JavaScript, so components and history weren't readable (5). A default limit of 6,000 queries a minute is published (15). The MCP server returns rate_limit_exceeded with retry_after_seconds and marks retryable codes, and the REST API delays rather than rejects requests over the limit. All calls are lookups, so retries are safe (12 of 15). No SLA found (0). The MCP server reports version 1.0.0 and the API is v3, neither labelled beta (10).

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.

FullContact 61

Closed service under terms dated 21 March 2025 that name J2 Martech Corp. (15). The privacy policy, updated 1 October 2026, names data brokers, data partners, public sources and trackers and has an opt-out portal, but gives no fixed retention period and doesn't say whether customer inputs feed the graph. The MCP docs say inputs aren't persisted (15 of 30). A dated sunset of the v2 Company APIs on 30 June 2022 (8 of 20). No sub-processor list found (0).

Dievio 35

No x402, MPP or L402 in the docs, the pricing pages or the terms (0). Prices published without a login as dollars per 1,000 API credits ($4.50 at 5,000 down to $2.92 at 60,000), per plan ($29.99, $79.99 and $149.99 a month for 10,000, 50,000 and 150,000 credits, 20 per cent less annually) and in a machine-readable pricing.md, with one credit per returned lead and previews, counts and exports free (20). Free plan of 100 one-time credits with no card, usable from the dashboard and over MCP; the REST API's separate balance starts empty on every plan, so the first API call needs a $22.50 top-up (15 of 20). A person signs up in a browser, and the OAuth consent and API key creation both need the dashboard (0). 0+20+15+0 = 35.

FullContact 10

No x402, MPP or L402 (0). No prices published. The pricing page asks visitors to talk to an expert (0). A free Platform account and sandbox keys for evaluation, but whether production lookups need a contract or a card wasn't stated (10 of 20). A person signs up in a browser and generates a key (0).

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.

FullContact 70

No OpenAPI for the REST API was found, and docs.fullcontact.com/reference returned 404. The MCP tool has a typed JSON Schema for its inputs (20 of 25). llms.txt and Markdown copies of every page (10). The tool description says what it does but not when to use it, and the docs explain which identifier combinations match best (13 of 20). Typed inputs, but no required fields or enums, and the rule that location needs a name is only in text (8 of 15). Examples for every input combination and an error table with codes, HTTP analogues and a retryable flag (14 of 15). v3 in the path and a changelog whose newest entries date from 2022 and earlier, while the MCP docs went up in 2026 without a changelog entry (5 of 15).

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.

FullContact 43

One Bearer API key per integration, revocable with a rotation procedure, scoped by product entitlement rather than by scope. No OAuth on the MCP server (20). Every call is a read and nothing writes, but there is no read-only key mode beyond entitlements (12 of 20). Responses carry bios and social data from third parties, and no prompt-injection guidance was found (3 of 15). Every MCP response carries a request_id, and no per-call log for the customer was found (3 of 15). The MCP docs say the server runs inside FullContact's SOC 2 boundary, but the security page, dated 1 January 2020, lists no certification or reporting channel, and there is no security.txt (5 of 20).

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.

FullContact 75

One tool, so the context cost is small (25). No paging is needed for single lookups, the response is a normalised profile, and Insight Bundles are fixed per account rather than per call (10 of 20). Stable error codes with retryable flags, request IDs and retry_after_seconds, and not_found documented as a normal miss (20). Lookups are safe to retry, but the tool carries no readOnlyHint, and misses are billed as calls (10 of 20). One identifier is enough, but the Python client was last released in July 2022 (10 of 15).