# Databar vs FullEnrich API + MCP (slim)

> FullEnrich scores 62.2 (B) to Databar's 53.8 (D) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.

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

FullEnrich API + MCP scores 62.2 (B) on agent readiness against Databar's 53.8 (D), and leads in 4 of 7 scored categories. Databar leads on schema & documentation and maintenance & community. Both do lead enrichment.

- Databar: D 53.8, rank #933 of 1486 · https://www.anchorterminal.com/tools/databar.min.md
- FullEnrich API + MCP: B 62.2, rank #565 of 1486 · https://www.anchorterminal.com/tools/fullenrich.min.md
- Databar, good for Waterfall enrichment across many providers for GTM agents, close to clay and fullenrich. Ahead on Schema & documentation, 84 against 76; Maintenance & community, 73 against 48.
- FullEnrich API + MCP, good for Maximising find rate on known contacts, especially mobiles, without a long-term contract. Ahead on Reliability, 70 against 28; Security & auth, 57 against 47; Payments & pricing, 40 against 35; Transparency & trust, 68 against 55.

| Category | Databar | FullEnrich API + MCP |
| --- | --- | --- |
| Reliability (16%) | 28 | 70 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 84 | 76 |
| Agent ergonomics (13%) | 66 | 66 |
| Security & auth (14%) | 47 | 57 |
| Payments & pricing (10%) | 35 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 73 | 48 |
| Transparency & trust (7%) | 55 | 68 |

| Fact (where they differ) | Databar | FullEnrich API + MCP |
| --- | --- | --- |
| Vendor | Databar, Inc. | FullEnrich |
| Hosted endpoint | `https://mcp.databar.ai/mcp` | `https://app.fullenrich.com/api/v2` |
| Transports | HTTP, Streamable HTTP, SSE (legacy) | HTTP, Streamable HTTP |
| Pricing | Paid | Freemium |
| Licence | Proprietary, under Databar, Inc.'s terms of service | none |
| Tools exposed | 69 | 13 |
| MCP registry | not listed | `io.github.FullEnrich/fullenrich` |
| Last release | 2026-10-30 | 2026-08-27 |
| Terms last updated | 2026-10-01 | 2026-08-20 |
| Privacy policy last updated | 2026-10-01 | 2026-08-20 |
| Terms restrict benchmarking | not found in the text | yes |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Reliability, FullEnrich API + MCP +42: Databar 28 (Hosted lines. No status page linked from the site or docs (0). No incident history to read (5). The 20 August changelog says rate limits return 429, but no numbers were found in the docs read (5 of 15). The SDK backs off on 429 per the 28 September entry, tasks can be cancelled with a refund, and no Retry-After or idempotency key is documented (8 of 15). No SLA found (0). The MCP server left beta on 15 July 2026 and the API is generally available (10). 0+5+5+8+0+10 = 28.); FullEnrich API + MCP 70 (Better Stack status page, but with one component (app.fullenrich.com/app) and none for the API or MCP (15 of 20). Its incident history, read on 4 November month by month from December 2025 to November 2026, says "No incidents reported" for every month, so the page has never posted an incident in the history we read (20, this run's value for a never-posted page; was 15 with the history unread). The monitor bar shows uptime figures of 100 and 99.983 per cent across its 30 to 90 day views, with no incident posted. 60 calls a minute on every endpoint, 100 contacts a bulk and 100 concurrent enrichments per workspace (15). The v2 OpenAPI documents a 429 on six operations with code `error.rate.limit` and the message "Too many requests. Try again in 1m", and identical re-submissions within 3 months aren't charged again, but there is no safe-retry guidance for writes (10 of 15; was 5). No SLA found (0). Generally available, no beta label on the API or MCP (10). 15+20+15+10+0+10 = 70.)
- Maintenance & community, Databar +25: Databar 73 (Closed service. Python SDK 2.9.0 on 30 October 2026, 7 days before this check (30). SDK 2.7.0 and 2.8.0 on 6 October and changelog entries on 23, 24, 27, 28, 29 and 30 September and 1 October (20). A public changelog, roadmap and feedback portal, an email address, and a Slack channel on Scale (10 of 15). An official Python SDK and CLI, no other languages (10 of 15). Package health not checked (3 of 10). 30+20+10+10+3 = 73.); FullEnrich API + MCP 48 (Every dated source of the vendor's own was looked for, in the MCP and skills repository (tags and CHANGELOG), the product changelog (answered 400 on 4 November; newest entry 30 November 2024 per the 1 October check), the docs (no changelog page; the OpenAPI file's Last-Modified date records no listed change). 1.0.4 on 27 August 2026 only links the repository from `server.json` and corrects the README, a packaging release that counts half and can't set recency. 1.0.2 (10 August) rewrote the full-crm skill's description and steps as well as adding the portable package, and 1.0.3 on 11 August changed skill behaviour (opt-out signals, a confirmation before sequencer changes), so both count in full. The newest of them, 1.0.3, is 85 days back (20). From 6 August, 1.0.2 and 1.0.3 in full and 1.0.4 at half make 2.5, under three (0; was 20). Support by email and help centre (6 of 15). Listed in the official MCP registry as io.github.FullEnrich/fullenrich, a GitHub-verified namespace (15). The skills repo has tests and a version-locked publish workflow (7 of 10). 20+0+6+15+7 = 48.)
- Transparency & trust, FullEnrich API + MCP +13: Databar 55 (Closed service with terms effective 1 October 2026 naming Databar, Inc. of Delaware (15 of 30). The privacy policy keeps data 'for as long as needed' with no periods; the docs give 24 hours for task results; a DPA is part of the agreement but was not read (15 of 30). The changelog flagged breaking API and SDK changes on 20 August 2026, and the terms let Databar retire any form of programmatic access; no notice period stated (8 of 20). Sub-processors are disclosed under the DPA, which was not read; data is processed in the United States (5 of 20). 15+15+8+5 = 43.); FullEnrich API + MCP 68 (Closed service with terms naming FullEnrich Corp. The skills and registry repo is MIT (15). The privacy policy (updated 20 August 2026, per the 1 October check) gives retention periods (3 years from last contact for prospects, 25 months for service improvement), legal bases and SCC or DPF transfers, and points rights requests to support@fullenrich.com. It doesn't say whether people returned by enrichment are covered, and the trust page says enrichment uses data providers it doesn't name, most acting as independent controllers. An opt-out page exists at fullenrich.com/optout (18 of 30). v1 and v2 APIs run side by side with no dated deprecation found (3 of 20). A sub-processor list is published, and the trust page now states that the hosting provider, DigitalOcean, hosts data in the European Union, with transfers outside the EEA disclosed (20 of 20; was 14 with hosting locations not stated). 15+18+3+20 = 56.)
- Security & auth, FullEnrich API + MCP +10: Databar 47 (A workspace API key in a header, never in the URL, and OAuth on the MCP with a Connected apps page to revoke access. No scopes found (20 of 30). No read-only key; MCP balance checks and confirmation above 50 credits, a 30-day trash for workbooks and tables, but row, column and table deletes through the tools (12 of 20). Enrichment results include web-scraped and AI researcher text, with no prompt-injection guidance (3 of 15). Credit usage charts, transaction logs and per-request data logs (12 of 15). No security.txt, disclosure policy, bug bounty or certification found (0 of 20). 20+12+3+12+0 = 47.); FullEnrich API + MCP 57 (Bearer API key for REST, no scopes found. The MCP signs in with OAuth and holds no static secret in the client. Webhooks are signed with HMAC-SHA1 keyed with the API key itself (20 of 30). The MCP isn't read-only, and confirmation before enrichment is recommended but left to the client. Workspace admins can set monthly credit limits per member, which block further credit-consuming MCP actions, and the skills add a confirmation before any sequencer change and honour opt-out and do-not-contact signals (10 of 20). Results are mostly structured contact fields (8 of 15). A free credits endpoint, and per-member usage views that include MCP activity, no per-call log found (7 of 15; was 5, aligned with people-data-labs' usage view). SOC 2 Type 2 per the trust page, with the report on request, vulnerability reports to support@fullenrich.com per the repository's SECURITY.md, security.txt 404 on 4 November, no bug bounty (12 of 20, as people-data-labs). 20+10+8+7+12 = 57.)
- Schema & documentation, Databar +8: Databar 84 (Each API reference page embeds its OpenAPI 3.1 operation (spec version 0.1.2), with no downloadable file found (20 of 25). llms.txt with 79 API entries and Markdown twins (10). Descriptions say when to use each endpoint, such as headless runs against table runs, and what a delete leaves behind (16 of 20). Typed request bodies with required fields (12 of 15). An error envelope with stable codes and examples for 400, 406 and 422 (14 of 15). v1 paths and a dated changelog, though the API's own versioning isn't described (12 of 15). 20+10+16+12+14+12 = 84.); FullEnrich API + MCP 76 (OpenAPI file for v2 at docs.fullenrich.com/api/v2/reference/openapi.yaml (version 2.0.0, eight paths, Last-Modified 3 November 2026), with a v1 file alongside (25). llms.txt with 34 links and Markdown twins (10). The MCP keeps tool descriptions short on purpose and moves workflow guidance into separate skills, so a client without skills gets less of it (12 of 20). Typed inputs, with helper tools that list valid industry, seniority and function codes (12 of 15). Test contacts that cost 0 credits and signed webhook examples. The OpenAPI file gives 400, 401, 402, 404 and 429 responses with a `code` and `message` schema and named examples such as `error.enrichment.first_name.empty` and `error.rate.limit`, though the docs have no separate error page (12 of 15; was 8, the 1 October check found no error reference). v1 and v2 paths. The public product changelog stopped at 30 November 2024 per the 1 October check and answered 400 "Invalid page" on 4 November, and only the MCP package has a current CHANGELOG (5 of 15). 25+10+12+12+12+5 = 76.)
- Payments & pricing, FullEnrich API + MCP +5: Databar 35 (No x402, MPP or L402 (0). Plan prices and credits are public, and each connector's credit cost is shown before a run and in the enrichment's pricing field; credits aren't sold per call outside a plan (15 of 20). A 14-day premium trial with no card, per the pricing FAQ (20). A person signs up in a browser, and API access needs a paid plan (0). 0+15+20+0 = 35.); FullEnrich API + MCP 40 (No x402, MPP or L402 (0). Per-unit credit costs and plan prices are public, on the pricing page and its Markdown twin, 1 credit a work email, 3 a personal email, 10 a mobile, 0.25 a search result, Pro from $29 a month for 500 credits ($55 for 1,000) (20). 50 trial credits with no card, API and MCP included (20). A person signs up in a browser (0). 0+20+20+0 = 40.)