Basedash MCP vs Secoda

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.

Secoda 0

Hosted service sold by contract, so the hosted rubric applies. No x402, MPP or L402 (0). The pricing page names Core, Premium and Enterprise with no prices, and every plan button links to a sales form (0). No free tier or trial was found on the site. The API docs still say to sign up for free at app.secoda.co, which we did not confirm (0). An agent needs a user in a customer workspace to generate an API key (0).

Basedash MCP 70

Graded with the hosted lines, on the remote server at charts.basedash.com. Instatus status page at status.basedash.com with one component, App, and notices back to April 2021; the MCP server isn't a separate component (20). No notices since 14 March 2026 and 100.0 per cent shown for September, October and November 2026, so the last 90 days are clean (30). No rate limit is published for the MCP server. The public API allows 60 requests a minute by default, per the changelog of 7 August 2026, which we count in part since the MCP surface may differ (5 of 15). The OpenAPI file documents a 429 with RateLimitExceeded and retryAfterMs on all 91 operations and an Idempotency-Key on starting a chat, but nothing is documented for 429s or retries over MCP (5 of 15). No uptime SLA; the about page names priority support SLAs on Enterprise only (0). The server isn't labelled beta or preview and is on both paid plans (10). Total 70.

Secoda 40

Hosted service, read on the hosted lines and graded on the REST API, with the local MCP server as a second surface. No status page is linked from the home page, the pricing page or the documentation index, and we did not try guessed addresses (0 of 20). With no page there is no readable incident history (5 of 30). Writes are limited to 30 PUT, PATCH or POST calls a minute on entity endpoints. No limit for GET requests was found (10 of 15). A 429 is documented with advice to retry after a delay or back off. No Retry-After header or idempotency key was found (6 of 15). The Service Level Agreement attached to the subscription agreement commits to 99.9 per cent monthly availability with service credits (10). The REST API carries no beta label. The MCP server is at version 0.1.0, and the Secoda AI Terms still describe a private beta (9 of 10). 0 + 5 + 10 + 6 + 10 + 9 = 40.

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.

Secoda 60

The docker-compose and Terraform repositories for self-hosted Secoda were tagged v2026.3.1 on 6 October 2026 (30). Five self-hosted versions were tagged between 4 August and 6 October 2026 (20). Closed service, scored on the 15-point scale. The public changelog stops at 28 October 2025, and support is by email and a Slack community. The MCP repository has one open issue (5 of 15). No official API client libraries and no entry in the official MCP registry. The MCP repository's last commit is 26 January 2026 (3 of 15). The MCP repository has no CI, no tests and no tags, and its dependencies are unpinned (2 of 10). 30 + 20 + 5 + 3 + 2 = 60.

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.

Secoda 54

A workspace API key sent as a Bearer header, with the same access as the user who created it. No scopes or expiry were found, and we did not confirm how a key is revoked. No secret travels in a query string (18 of 30). A key follows its creator's role and team membership, and run_sql needs an admin toggle and query access to the integration. No read-only key and no confirmation step for deletes were found (8 of 20). The API and MCP tools return descriptions, documents and query results written by workspace users. No prompt-injection guidance was found (3 of 15). An audit log filterable by user, date, type and resource, an audit log endpoint in the API, and SIEM logging on Enterprise (12 of 15). A disclosure policy with a reply within 5 business days and safe harbour, a bug bounty by email with a reward for findings of CVSS 4 or higher, and SOC 2 stated with documentation on request. No security.txt and no public advisories (13 of 20). 18 + 8 + 3 + 12 + 13 = 54.

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.

Secoda 60

Closed service with a published Master Subscription Agreement. The MCP server is MIT (15 of 30). A privacy policy, a Data Processing Agreement with 10 days' notice of subprocessor changes and breach notice without undue delay, return of customer data within 30 days of termination, and AI terms that rule out training on customer data without permission. Some statements disagree. The AI security page says OpenAI and Anthropic process in the US while also naming Google, the Data Processing Agreement's security appendix refers to audio and video streams, and no legal document mentions Atlassian (17 of 30). Deprecated endpoints are flagged in the API definitions with a replacement and no date. The acquisition post promises technical plans and timelines in advance, and none were found on the pages read (6 of 20). 25 subprocessors with locations, and three AWS hosting regions (18 of 20). 15 + 17 + 6 + 18 = 56.

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.

Secoda 44

Graded on the REST API. The catalogue response carries more than 40 fields for each resource, and no field selection or page size parameter was found. The MCP server is small, six tools with short definitions (12 of 25). Lists take page and return links, meta and total_pages, with JSON filter and sort and a filter generator in the app's settings. Results stop at 10,000 resources (15 of 20). Errors are HTTP status codes with one-line descriptions, plus a troubleshooting note on trailing slashes (6 of 20). No idempotency keys. Updates use PATCH, bulk update takes 100 entities, and the MCP tools set no readOnlyHint or destructiveHint (4 of 20). Few required parameters. No official API client libraries were found, and the Secoda SDK is for building custom integrations that run inside Secoda (7 of 15). 12 + 15 + 6 + 4 + 7 = 44.