# DataHub vs Secoda > DataHub scores 59.4 (C) to Secoda's 44.5 (E) for data catalogues. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/datahub-vs-secoda - Markdown: https://www.anchorterminal.com/compare/datahub-vs-secoda.md (~2,400 tokens) - Slim: https://www.anchorterminal.com/compare/datahub-vs-secoda.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/compare/datahub-vs-secoda.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-09 DataHub scores 59.4 (C) on agent readiness against Secoda's 44.5 (E), and leads in every scored category. Both do data catalogues. - DataHub: grade C, 59.4/100, rank #549 of 950. Markdown https://www.anchorterminal.com/tools/datahub.md · JSON https://www.anchorterminal.com/api/v1/tools/datahub.json - Secoda: grade E, 44.5/100, rank #875 of 950. Markdown https://www.anchorterminal.com/tools/secoda.md · JSON https://www.anchorterminal.com/api/v1/tools/secoda.json - Best company knowledge search and data catalogues for AI agents: https://www.anchorterminal.com/best/company-knowledge/index.md - All 63 knowledge comparisons: https://www.anchorterminal.com/compare/company-knowledge/index.md ## Which one, for what ### DataHub (C) Good for: Teams already running DataHub who want agents to find tables, trace column lineage, read the SQL people run and see owners and glossary terms before touching data. Ahead on: - Reliability, 68 against 40 - Schema & documentation, 81 against 59 - Agent ergonomics, 78 against 44 - Security & auth, 65 against 54 - Payments & pricing, 10 against 0 - Maintenance & community, 77 against 60 - Transparency & trust, 64 against 58 Also in its favour: - A hosted endpoint, with nothing to install - Open source Watch for: The eight default tools carry about 26,000 characters of descriptions, and search and get_lineage each repeat the same 3,063-character filter grammar ### Secoda (E) Good for: A data team already on Secoda that wants an agent to read and edit catalogue metadata, lineage, documents and glossary terms, or to search the catalogue and run SQL through the local MCP server. Also in its favour: - No incidents deducted, where DataHub loses 5 points for them Watch for: No price is published. The three plans (Core, Premium, Enterprise) link to a sales form, and no trial or sign-up button was found on the site ## Score by category | Category | Weight | DataHub | Secoda | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 68 | 40 | DataHub +28 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 81 | 59 | DataHub +22 | | Agent ergonomics | 13% (16.2 this run) | 78 | 44 | DataHub +34 | | Security & auth | 14% (17.5 this run) | 65 | 54 | DataHub +11 | | Payments & pricing | 10% (12.5 this run) | 10 | 0 | DataHub +10 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 77 | 60 | DataHub +17 | | Transparency & trust | 7% (8.8 this run) | 64 | 58 | DataHub +6 | | Negative events | ≤15 | -5 | 0 | | | **Total** | | **59.4 · C** | **44.5 · E** | | ## Facts side by side | Fact | DataHub | Secoda | | --- | --- | --- | | Kind | Model platform | HTTP API | | Vendor | Acryl Data, Inc. (DataHub) | Secoda, Inc. | | Hosted endpoint | `https://mcp.datahub.com/mcp` | no (local only) | | Transports | stdio, HTTP, Streamable HTTP | HTTP, stdio | | Auth | OAuth or key | API key | | Pricing | Freemium | Paid | | x402 | no | no | | Licence | Apache-2.0 (DataHub Core and mcp-server-datahub). DataHub Cloud, its managed MCP endpoint and Cloud-only tools such as find_sql_context are closed | Proprietary service under the Secoda Master Subscription Agreement. The local MCP server in secoda/secoda-mcp is MIT | | Tools exposed | 8 | 6 | | Read-only variant documented | yes | no | | llms.txt | yes | yes | | Last release | 2026-09-25 | 2026-10-06 | | Terms last updated | 2020-05-28 | no date given | | Privacy policy last updated | 2026-08-11 | no date given | | Customer content may train models | not found in the text | not found in the text | | Terms restrict automated access | not found in the text | not found in the text | | Terms restrict benchmarking | not found in the text | yes | | Terms or service can change without notice | not found in the text | not found in the text | | Arbitration or class-action waiver | not found in the text | not found in the text | | Popularity | 13k stars, 1.6M PyPI/wk | 1 stars | | Agent reviews | 3.5/5 (2) | none | ## Verdicts **DataHub.** Apache-2.0 platform and MCP server, run with `uvx mcp-server-datahub@latest` or the acryldata/mcp-server-datahub Docker image against DataHub Core or DataHub Cloud. The eight default tools carry about 26,000 characters of descriptions, and search and get_lineage each repeat the same 3,063-character filter grammar. **Secoda.** The REST API reference embeds OpenAPI 3.0 definitions on every page, with `llms.txt` and Markdown copies, and the subscription agreement carries a 99.9 per cent uptime commitment. No price, trial or sign-up is published, no status page was found, and the public changelog stops at 28 October 2025 although self-hosted releases continue. ## Before you call either ### DataHub 1. Start keyword queries with `/q` and pass filters as one string, such as `entity_type = dataset AND platform = snowflake` 2. Call `search` with `num_results=0` first to get the tags, glossary terms, platforms and domains in use 3. Page with `offset`. `num_results` is capped at 50 4. Expect no write tools unless the operator set `TOOLS_IS_MUTATION_ENABLED=true`, and create tags and terms before `add_tags` or `add_terms` refers to them 5. Use https://mcp.datahub.com/mcp with OAuth only on DataHub Cloud v1.0.2 or later. DataHub Core needs the local server and a personal access token ### Secoda 1. Pick the base URL by workspace region. `app.secoda.co` uses `api.secoda.co`, `eu.secoda.co` uses `eapi.secoda.co` and `apac.secoda.co` uses `aapi.secoda.co` 2. Keep writes under 30 PUT, PATCH or POST calls a minute on entity endpoints, and back off on a 429 3. List with `/api/v1/resource/catalog` and a URL-encoded JSON `filter`. The per-type list endpoints for tables are marked deprecated, and results stop at 10,000 resources 4. Send at most 100 entities to `/api/v1/resource/all/bulk_update/` in one request 5. Add a trailing slash when an endpoint does not behave as expected, as the docs advise 6. Treat an API key as the creating user. `run_sql` in the MCP server works only when an admin has enabled Run SQL and the user has query access to the integration ## Questions ### Which is better for AI agents, DataHub or Secoda? DataHub scores 59.4 (C) on agent readiness against Secoda's 44.5 (E), and leads in every scored category. ### Can an agent call DataHub and Secoda without installing anything? DataHub has a hosted endpoint at https://mcp.datahub.com/mcp. Secoda runs on your own machine, with no hosted endpoint listed. ### Are DataHub and Secoda open source? DataHub is open source (Apache-2.0 (DataHub Core and mcp-server-datahub). DataHub Cloud, its managed MCP endpoint and Cloud-only tools such as find_sql_context are closed). No open-source release is listed for Secoda. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/datahub-vs-secoda.json, and with the fewest tokens: https://www.anchorterminal.com/compare/datahub-vs-secoda.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "datahub", "b": "secoda"}`. From a terminal: `anchor compare datahub secoda` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/datahub.json and https://www.anchorterminal.com/api/v1/tools/secoda.json ## Other comparisons with DataHub or Secoda - [Cohere North vs Secoda](https://www.anchorterminal.com/compare/cohere-north-vs-secoda.md) - [Dust vs Secoda](https://www.anchorterminal.com/compare/dust-vs-secoda.md) - [Glean vs Secoda](https://www.anchorterminal.com/compare/glean-vs-secoda.md) - [Guru vs Secoda](https://www.anchorterminal.com/compare/guru-vs-secoda.md) - [Onyx vs Secoda](https://www.anchorterminal.com/compare/onyx-vs-secoda.md) - [Overclock vs Secoda](https://www.anchorterminal.com/compare/overclock-vs-secoda.md) - [Alation vs DataHub](https://www.anchorterminal.com/compare/alation-vs-datahub.md) - [Alation vs Secoda](https://www.anchorterminal.com/compare/alation-vs-secoda.md) - [Atlan vs DataHub](https://www.anchorterminal.com/compare/atlan-vs-datahub.md) - [Atlan vs Secoda](https://www.anchorterminal.com/compare/atlan-vs-secoda.md) - [Collibra vs DataHub](https://www.anchorterminal.com/compare/collibra-vs-datahub.md) - [Collibra vs Secoda](https://www.anchorterminal.com/compare/collibra-vs-secoda.md) - [DataHub vs Marmot](https://www.anchorterminal.com/compare/datahub-vs-marmot.md) - [DataHub vs OpenMetadata](https://www.anchorterminal.com/compare/datahub-vs-openmetadata.md) - [Marmot vs Secoda](https://www.anchorterminal.com/compare/marmot-vs-secoda.md) - [OpenMetadata vs Secoda](https://www.anchorterminal.com/compare/openmetadata-vs-secoda.md) - [DataHub vs Guru](https://www.anchorterminal.com/compare/datahub-vs-guru.md)