Head to head · Company knowledge search · October 2026 research run

Microsoft MCP Server for Enterprise vs Secoda

Microsoft MCP Server for Enterprise scores 54.1 (C) on agent readiness against Secoda's 40.3 (E), and leads in 5 of 7 scored categories. Secoda leads on schema & documentation. Both do company knowledge search.

Best company knowledge search and data catalogues for AI agents · All 152 knowledge comparisons

Which one, for what

Microsoft MCP Server for Enterprise C

Best for Admins and support agents who ask questions about users, groups, apps, devices and licences in an Entra tenant.

Ahead on

  • Reliability, 53 against 40
  • Agent ergonomics, 55 against 44
  • Security & auth, 85 against 54
  • Payments & pricing, 50 against 0
  • Maintenance & community, 43 against 10

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

An administrator has to provision it per tenant with PowerShell and grant each client

Secoda E

Best 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.

Ahead on

  • Schema & documentation, 59 against 29

Also in its favour

  • Runs on your own machine

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

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Microsoft MCP Server for Enterprise +50

Microsoft MCP Server for Enterprise 50

No payment protocol (0). The overview says there's no additional cost or separate licence to enable it, published without a login (30). It's free, but it needs a Microsoft Entra tenant, and some data needs Entra ID P2 or ID Governance licences (20 of 30). An administrator provisions it with PowerShell and grants each client in the tenant (0). 0 + 30 + 20 + 0 = 50.

Secoda 0

Hosted service sold by contract, so the hosted rubric applies, per the 9 October check, not re-read on 5 November because Secoda's Terms of Use bar bots that crawl or scrape Secoda or its site. 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 said 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). 0 + 0 + 0 + 0 = 0. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

Maintenance & community Microsoft MCP Server for Enterprise +33

Microsoft MCP Server for Enterprise 43

General availability announced on 17 November 2026 (30). No three dated changes in 90 days were found (0). Questions are answered on Microsoft Q&A, and support goes through Microsoft's channels (8 of 15). The GitHub MCP registry shows an entry under microsoft, seen in a search only, so not counted (0, unchecked). A hosted service with no package to keep current (5 of 10). 30 + 0 + 8 + 0 + 5 = 43.

Secoda 10

Closed service, read on the hosted lines. Its recency is the last published API change, and the public changelog stopped at v8.21.0 of 28 October 2025 per the 9 October check, not re-read on 5 November (0). The docker-compose and Terraform repositories for self-hosted Secoda, read from clones on 5 November, were tagged eight times from 9 September to 3 November 2026 (v2026.2.7 to v2026.3.6). Each tag is a GitHub Actions release that only moves the secoda/on-premise-frontend and secoda/on-premise-api image tags, with no release notes, and the self-hosted changelog stopped at v2025.4.4 of 29 October 2025. Those images sit outside packages and outside the hosted API, so they aren't counted, as an on-prem image takes no term on rime-tts (0). Support is by email and a Slack community, per the 9 October check. The MCP repository has one open issue (5 of 15). No official API client libraries, and no official MCP registry entry could be read. 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). 0 + 0 + 5 + 3 + 2 = 10.

Security & auth Microsoft MCP Server for Enterprise +31

Microsoft MCP Server for Enterprise 85

Microsoft Entra delegated OAuth: an administrator registers the server and grants each MCP client its scopes, and the server enforces the user's own privileges and those scopes (30). Read-only Graph calls only (20). It returns directory data, names and attributes that users and admins can edit, with no prompt-injection guidance found (5 of 15). Every request lands in Microsoft Graph activity logs, with a Kusto query to filter the server's app ID (15). Microsoft's security programme and certifications, but microsoft.com's security.txt had expired per the Copilot Studio MCP listing (15 of 20). 30 + 20 + 5 + 15 + 15 = 85.

Secoda 54

Every reading here is per the 9 October check, not re-read on 5 November because Secoda's Terms of Use bar bots that crawl or scrape Secoda or its site. 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 how a key is revoked wasn't confirmed. 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.

Schema & documentation Secoda +30

Microsoft MCP Server for Enterprise 29

The three tools (microsoft_graph_suggest_queries, microsoft_graph_get, microsoft_graph_list_properties) are described in prose on the overview. Their schemas need an Entra tenant to list, so no contract was read (0 of 25). learn.microsoft.com serves Markdown to agents, as for the other Microsoft listings (10). The overview says what each tool does and the workflow they follow, but not when not to use them (12 of 20). Input types weren't readable (0 of 15). A sample prompts page and a Kusto query for its logs, but no documented error responses (7 of 15). No version or changelog found (0). 0 + 10 + 12 + 0 + 7 + 0 = 29.

Secoda 59

Every reading here is per the 9 October check, not re-read on 5 November because Secoda's Terms of Use bar bots that crawl or scrape Secoda or its site. Each API reference page embeds OpenAPI 3.0 definitions at version 8.22.66, with request and response schemas. The full description behind the ReDoc page the reference links to, on api.secoda.co, answered 403 to our reader, so the fragments on six of 23 reference pages were read (20 of 25). llms.txt with 371 lines and a Markdown copy of every page (10). Operations carry one or two sentences of purpose, deprecated list endpoints name their replacement with a filter example, and List Resources states its 10,000 limit. Lineage parameters have no descriptions, and the six MCP tools have one-line descriptions with a server prompt on choosing between the two search tools (10 of 20). Response fields are typed and described, but filter and sort are URL-encoded JSON passed as strings, and few enums were seen (7 of 15). An examples page with five workflows and authentication samples in curl, JavaScript and Python. Errors are status codes with a one-line description and no body format (7 of 15). Paths carry /api/v1 and the definitions carry a version, but the public changelog stopped at 28 October 2025 and has no API entries (5 of 15). 20 + 10 + 10 + 7 + 7 + 5 = 59.

Reliability Microsoft MCP Server for Enterprise +13

Microsoft MCP Server for Enterprise 53

Hosted MCP lines. Microsoft's cloud status page at status.cloud.microsoft, as for the Copilot Studio MCP listing (20). No incident history for this service could be read, so 5 of 30 and said so. Rate limit published, 100 calls a minute per user (15). The overview says calls honour Graph throttling limits but gives no 429 or Retry-After guidance of its own (8 of 15). No SLA found for it (0). Microsoft's Book of News of 17 November 2026 lists it as generally available, but the overview page read on 18 November still says preview, so half (5 of 10, a judgement call). 20 + 5 + 15 + 8 + 0 + 5 = 53.

Secoda 40

Hosted service, read on the hosted lines and graded on the REST API, with the local MCP server as a second surface. Every reading here is per the 9 October check, not re-read on 5 November because Secoda's Terms of Use bar bots that crawl or scrape Secoda or its site. No status page is linked from the home page, the pricing page or the documentation index (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 described a private beta (9 of 10). 0 + 5 + 10 + 6 + 10 + 9 = 40.

Agent ergonomics Microsoft MCP Server for Enterprise +11

Microsoft MCP Server for Enterprise 55

Three tools, a search over Graph examples, a read-only Graph call and an entity-schema lookup, so a small list, sizes not read (20 of 25). Graph's own query options pass through microsoft_graph_get, but no page or size control is documented for the server (10 of 20). No documented error codes (5 of 20). Read-only by design, per the overview; annotations not readable (12 of 20). No SDK needed, but provisioning is a PowerShell step per tenant and required parameters weren't readable (8 of 15). 20 + 10 + 5 + 12 + 8 = 55.

Secoda 44

Graded on the REST API, per the 9 October check, not re-read on 5 November because Secoda's Terms of Use bar bots that crawl or scrape Secoda or its site. 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, which the repository clone still shows on 5 November (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.

Score by category

CategoryWeightMicrosoft MCP Server for EnterpriseSecodaEdge
Reliability16%5340Microsoft MCP Server for Enterprise +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%2959Secoda +30
Agent ergonomics13%5544Microsoft MCP Server for Enterprise +11
Security & auth14%8554Microsoft MCP Server for Enterprise +31
Payments & pricing10%500Microsoft MCP Server for Enterprise +50
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4310Microsoft MCP Server for Enterprise +33
Transparency & trust7%5760Secoda +3
Negative events≤1500
TotalC 54.1/100E 40.3/100

Facts side by side

FactMicrosoft MCP Server for EnterpriseSecoda
KindMCP serverHTTP API
VendorMicrosoftSecoda, Inc.
Hosted endpointhttps://mcp.svc.cloud.microsoft/enterpriseno (local only)
TransportsStreamable HTTPHTTP, stdio
AuthOAuthAPI key
PricingFreePaid
x402nono
LicenceClosed service under the Microsoft APIs Terms of UseProprietary service under the Secoda Master Subscription Agreement. The local MCP server in secoda/secoda-mcp is MIT
Tools exposed36
Read-only variant documentedyesno
llms.txtnoyes
Last release2026-11-172025-10-28
Terms last updated2025-10-01no date given
Privacy policy last updated2026-09-01no date given
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviewsnone2.5/5 (4)

How the scores have moved

Verdicts

Microsoft MCP Server for Enterprise

A free, read-only MCP server over a Microsoft Entra tenant's directory, with Entra-scoped access and every call in Graph's activity logs. It needs an administrator to provision it per tenant, and its tool schemas, errors and changelog aren't public.

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 stopped at 28 October 2025 although self-hosted releases continue.

Before you call either

Microsoft MCP Server for Enterprise

  1. Connect to https://mcp.svc.cloud.microsoft/enterprise with an Entra token for a client your administrator has granted
  2. Call microsoft_graph_suggest_queries first to find the Graph call, then microsoft_graph_get to run it
  3. Expect only reads; it can't change anything in the tenant
  4. Stay under 100 calls a minute per user

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, Microsoft MCP Server for Enterprise or Secoda?

Microsoft MCP Server for Enterprise scores 54.1 (C) on agent readiness against Secoda's 40.3 (E), and leads in 5 of 7 scored categories. Secoda leads on schema & documentation.

Do Microsoft MCP Server for Enterprise and Secoda need an API key?

Microsoft MCP Server for Enterprise uses an OAuth sign-in. Secoda needs an API key.

Can an agent call Microsoft MCP Server for Enterprise and Secoda without installing anything?

Microsoft MCP Server for Enterprise has a hosted endpoint at https://mcp.svc.cloud.microsoft/enterprise. Secoda runs on your own machine, with no hosted endpoint listed.

Other comparisons with Microsoft MCP Server for Enterprise or Secoda

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.