Basedash MCP vs Collibra

Basedash MCP 32

No x402, MPP or L402 (0). Plan prices are public, $1,000 a month for Startup with $1,000 of AI credits included, but the cost of an MCP question in AI usage isn't published (10). A 14-day trial needs no card, includes up to $250 of AI usage and has the MCP server, since it's on every plan and the trial has full feature access (20). A person signs up in a browser and approves the OAuth connection; clients can register themselves with the authorisation server, which earns 2 (2 of 20). Total 32.

Collibra 0

Hosted service, so the hosted rubric applies. No x402, MPP or L402 (0). No published prices. www.collibra.com/pricing returns 404 and the site links a demo request and a product tour (0). No free tier or self-serve trial was found. The Collibra Units included in a contract are an allowance inside a paid subscription (0). An agent needs a customer's administrator to register an OAuth application after a sales contract (0).

Basedash MCP 57

The served tool definitions can be read only in a signed-in MCP session, which this run doesn't open. The docs and feature page list all ten tools with their inputs, which are required or optional, their scopes, what each returns and which one is annotated destructive, and the REST API counterpart has a public OpenAPI 3.1.0 file (50 paths, 91 operations). Judgement call, 10 of 25 for documented inputs without published JSON Schemas. llms.txt and Markdown copies of every docs page are served (10). Each tool's purpose is stated, with when to use MCP over the REST API and get_data_sources described as the call to make before asking; when not to call a build tool isn't stated (12 of 20). Inputs are a free-text question or instructions plus ids, with no enums or constraints documented (5 of 15). Example questions on the feature page and the launch posts, and troubleshooting for Forbidden or not-a-member, usage blocked and not-found errors, but no error payload shapes (10 of 15). A public dated changelog with MCP entries on 5 June, 14 August, 4 and 25 September and 7 and 9 October 2026, and a server.json version (1.1.0), but the registry entry is still 1.0.0 and the llms.txt of 7 October 2026 still describes two tools (10 of 15). Total 57.

Collibra 83

Each REST API has an OpenAPI 3.0 definition, printed in the Markdown copy of every reference page and served by each instance at /docs/index.html, and the GraphQL schema is open to introspection. MCP tools take typed inputs and declare an output schema. We found no single public file to download (22 of 25). developer.collibra.com publishes llms.txt, a Markdown copy of each page and an MCP server for the documentation (10). MCP tool descriptions state purpose, required permissions and the tool to call next, and the server ships an instructions file. REST operations carry a one-line summary (15 of 20). Request schemas use enums, defaults, minimum and maximum values and required fields. The Output Module takes a query document of its own (13 of 15). Tutorials cover authentication, pagination and import with examples. Error responses are generic descriptions for 400, 401, 403, 404 and 500, plus a table of four JWT error codes (10 of 15). Paths carry a version (/rest/2.0, /v1), release notes appear monthly and the Output Module guide keeps a dated list of changes. The API compatibility page showed our reader no content (13 of 15).

Basedash MCP 55

Ten tools, grouped by the vendor into ask, build and look up. Their definitions' size couldn't be measured without a session, so 20 of 25 rather than 25. No paging, filters or size controls are documented for list_dashboards or list_charts; ask_question returns tables as CSV files rather than inline rows, and the client can page through the tool list, per the changelog of 14 August 2026 (5 of 20). The troubleshooting section names Forbidden or not-a-member, usage blocked and not-found or archived artifacts with what to do, and ask_question and get_data_sources return typed structured payloads since 5 June 2026 (10 of 20). edit_dashboard is annotated destructive and a failed dashboard or chart build is cleaned up, but no readOnlyHint on the look-up tools or idempotency on the create tools is documented (10 of 20). One or two required inputs per tool and nothing to install; the only official SDK is the React embedding SDK, which isn't for MCP (10 of 15). Total 55.

Collibra 75

The local MCP server registers 31 tools by default since get_user_id_by_name arrived in v0.0.64 (9 October 2026), and keeps 18 data quality tools behind a flag, with allow and deny lists for tool names. The line is read mainly on the APIs, where GraphQL queries select fields and REST lists take limit, so the one tool over 30 doesn't move it (21 of 25). REST paging is by offset and limit or by cursor with nextCursor, with filters on most list operations and a countLimit switch to skip the total. GraphQL takes where, order, limit and offset (19 of 20). Errors are standard HTTP codes with short descriptions, and the MCP source returns messages that list the valid options when a name does not resolve. No catalogue of API error codes was found (13 of 20). Every MCP tool declares readOnlyHint, destructiveHint and idempotentHint, and the destructive data quality tools return a preview until called with confirm=true. The Import API matches resources by identifier, so a repeated import updates in place. No idempotency keys on the REST APIs (15 of 20). Defaults are sensible (20 search results, 10 GraphQL items). We found no official SDK. The portal has a tutorial on generating a client from the OpenAPI definition, and a CLI binary with two command groups (7 of 15).

Basedash MCP 74

The editorial half. A closed service under dated terms (14 October 2026) naming Basedash Inc. and Delaware law, with 30 days' notice of material adverse changes to the agreement (15). The privacy policy (1 June 2026), the data processing addendum (6 October 2026) and the security docs agree that customer data isn't used for training by Basedash or its AI providers, and the security docs say table and column names and query results go to AI providers. Retention periods differ by document. The privacy policy says a reasonable period, the terms 60 days after a deletion request, the security docs complete removal on request, and audit events are kept 90 days. Locations differ in wording (San Francisco servers in the security docs, DigitalOcean in the United States in the privacy policy) (18 of 30). No deprecation policy for the MCP server; the REST API is unversioned and breaking changes are communicated in advance when possible, and the dashboard scopes were granted to existing connections without re-authorising (8 of 20). The DPA names ten subprocessors (OpenAI, Sentry, Stripe, DigitalOcean, Anthropic, Amazon Web Services, Microsoft Azure, Fivetran, MotherDuck, Betterstack) in the United States and the Czech Republic (16 of 20). Total 57.

Collibra 85

Closed service under the published Master Collibra Agreement and Developer Terms. The local MCP server is Apache-2.0 and the CLI ships under a Binary Code Licence Agreement (15 of 30). The agreement allows export for 30 days after the term and then deletion on Collibra's standard schedule, and the Data Processing Addendum of 1 October 2026 sets deletion within 120 days of termination and breach notice without undue delay. The agreement bars sending customer data to a third party to train generative AI without written consent. The Privacy Policy says it does not cover data processed for customers. No retention period for a live subscription was found (24 of 30). An announcements page gives end-of-life dates, an 18-month deprecation period for retired REST properties and removal of the Metric capability in 2027.01. The API tutorial says breaks happen only in a major release after a deprecation message, and a supported versions policy is published (17 of 20). The subprocessor list of 8 September 2026 names each processor with its purpose and hosting location, and the addendum gives 30 days' notice of additions (19 of 20).