Atlan vs Basedash MCP

Atlan 0

Hosted service with nothing to self-host, so the hosted rubric applies. No x402, MPP or L402 (0). No published prices, and atlan.com/pricing is a contact form for sales (0). No free tier, trial or self-serve sign-up found (0). An agent needs a person at a customer company to sign in by OAuth, or an admin to create an API token, after a sales contract (0).

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.

Atlan 74

41 tools on one endpoint on 2 November 2026, across Read, Write and Admin access levels, which puts it in the over-30 band (5). We added 7 back because a tenant can ask for read-only mode, which leaves the read tools, and tool exposure is a per-tenant allowlist, though neither is something an agent or a user can switch on (12 of 25). Search returns 20 results by default and up to 100 per call, or only a count, takes filters for type, certificate, tags, domains, terms and dates, and takes a list of attributes to return. SQL results stop at 100 rows (20). Ten coded errors, each with a category and a recovery step, such as ATLAN-MCP-1006 for a qualifiedName passed where a GUID belongs (17 of 20). Write tools return a preview and wait for approval, and the SQL tool refuses anything but SELECT, WITH, SHOW, DESCRIBE and EXPLAIN. We couldn't see readOnlyHint or destructiveHint on the closed server, and there are no idempotency keys (10 of 20). One URL and an OAuth sign-in with no key for Claude Code, Codex or Cursor, and official SDKs for Python, Java and Go (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.

Atlan 65

We found no public OpenAPI file for the REST API. MCP tools carry JSON Schema by protocol, but the hosted server is closed and lists its tools only after a sign-in, so we couldn't read the schemas (15 of 25). llms.txt at docs.atlan.com with about 180 links and Markdown copies of pages, plus a separate docs MCP server at docs.atlan.com/mcp (10). The tools reference gives each of the 41 tools (2 November 2026) a one-line purpose and an access level, and the atlan-search skill (8,358 characters plus six reference files) says which tool fits which ask and when not to use one, such as sending row values to query_assets rather than search (13 of 20). Input types are unverified on the hosted server, and the deprecated local server took untyped rule dicts for its data quality tools (6 of 15). An error catalogue of 10 coded errors, each with a category and a recovery step, and filter examples in the skill (12 of 15). A product changelog with absolute dates now sits at docs.atlan.com (newest entry 26 October 2026) beside shipped.atlan.com, and pyatlan's HISTORY.md has breaking-change sections per release, but the hosted MCP server has no version or changelog of its own, and the agent-toolkit CHANGELOG stops at 0.3.3 on 17 February 2026 (9 of 15).

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.

Atlan 75

OAuth with PKCE per user, so each MCP call runs as that user under the personas, roles and domain policies that govern the Atlan UI, with tokens checked against Keycloak's JWKS. Or an API token as a Bearer header, which runs as one service identity, and tokens with more than one persona are refused. OAuth scopes aren't documented and we didn't check API token expiry. No secret travels in a query string (25 of 30). Read-only mode removes write, admin and lifecycle tools, but only on request to Atlan. The allowlist fails closed, writes preview and wait for approval, and a write needs the user's own edit permission (16 of 20). Tools return asset descriptions, READMEs, knowledge files and up to 100 rows of warehouse data. The security page says prompt-injection and PII guardrails run at the Atlan AI gateway without saying what they do (7 of 15). Every tool call is logged with the tool, client name and version, model, tenant, request ID, duration and status, with arguments redacted, and metadata changes land in the asset's activity history. We didn't confirm a customer can read the call log itself (11 of 15). security.txt valid until 14 January 2027, a disclosure programme with safe harbour and triage within 7 business days that rewards with gift cards or swag at Atlan's discretion, and ISO 27001, ISO 27701, SOC 2 Type II and HIPAA badges on the security page. The trust centre holding the reports renders only with JavaScript, so we couldn't read it (16 of 20).

Basedash MCP 68

OAuth on Basedash's own authorisation server, with the authorisation code grant and PKCE S256 only, refresh tokens, public clients, dynamic client registration, client ID metadata documents and a revocation endpoint. Three scopes separate asking, reading dashboards and writing them, and the token goes in the header only (30). Building needs mcp:dashboards:write on top of mcp:chat:ask, edit_dashboard is annotated destructive, no tool deletes, and Basedash's AI can change database rows only from the web app with an approval card, per the accuracy page. No server-side confirmation is documented for dashboard edits, and the consent screen on the feature page shows all three scopes together (15 of 20). Answers are drawn from connected company data, which can include text written by outsiders (tickets, CRM records synced by Fivetran), and no prompt-injection guidance was found. Hidden columns and row-level security narrow what reaches the model (5 of 15). The MCP server is a named audit log source, but AI tool calls and queries are recorded on Enterprise only; AI usage per person and feature is shown on every plan (10 of 15). No security.txt on www or charts, and no bug bounty or disclosure policy found. Basedash says it holds SOC 2 Type II, with the report under NDA, and runs third-party penetration tests (8 of 20). Total 68.

Atlan 80

pyatlan 11.6.0 tagged on 26 October 2026, 11.5.0 and atlan-java v7.5.0 on 22 October (30). pyatlan tags 10.0.0, 11.0.0, 11.0.1, 11.1.0, 11.2.0, 11.3.0, 11.4.0, 11.4.1, 11.5.0 and 11.6.0 and atlan-java v7.4.1 and v7.5.0 in the 90 days from 4 August, and the docs changelog has dated entries to 26 October (20). Closed service, scored on the 15-point scale. A public changelog, and 24x7 support with response times by severity for customers. On GitHub, agent-toolkit's open issues go back to May 2025 and include requests the hosted server has since met, such as OAuth support (#86), still open per the 3 October check (10 of 15). Current official SDKs for Python and Java, Go last tagged on 27 January 2026 with a last commit on 16 February 2026, and no entry in the official MCP registry on 2 November 2026 (12 of 15). pyatlan runs pull request, scheduled test and Trivy scan workflows, and agent-toolkit has Dependabot. We couldn't see run results, and agent-toolkit's own CI is pre-commit checks only (8 of 10).

Basedash MCP 75

Read as a closed hosted service. The changelog's latest entry is 30 October 2026, and the latest MCP-specific entries are 7 and 9 October 2026 (chart placement on a dashboard tab, restyled MCP sign-in pages), all within 30 days (30). Weekly dated changelog entries, with MCP changes on 14 August, 4 and 25 September and 7 and 9 October 2026 (20). Support by email and by Slack on paid plans, with response times not tested (10 of 15). Active in the official MCP registry as com.basedash/mcp under the reverse-DNS namespace for basedash.com, though its description still names two tools (15). No package to judge; the registry entry lags the repository's server.json (0 of 10). Total 75.