- Reliability 8/20
- This is a Microsoft-owned MCP server built on the official MCP C# SDK, with a manifest declaring stdio transport and NuGet distribution, and a README that consistently enumerates the tool set (auth, gateways, connections, workspaces, dataflows, pipelines, copy jobs, Airflow jobs, capacities). However, this is a static, source-only review: no CI workflow files, committed tests, or execution logs are present, so the MCP init handshake and the claim that declared tools match real behavior cannot be verified. The manifest's version field is left as the literal build placeholder "$(PackageVersion)", a concrete packaging defect that could break install resolution. Error handling, timeouts, dependency failures, and edge cases are essentially undocumented, so the score is capped well below the static ceiling at 8.
- Security and permissions 10/20
- No malware, credential theft, covert exfiltration, or unconfirmed irreversible delete/deploy/remote-command defaults were found; Azure AD interactive and service-principal authentication is a standard pattern. Deductions: the README openly exposes a get_access_token tool that surfaces access tokens into the model context with no described scoping, redaction, or lifetime guidance, a real token-leakage boundary risk; the server ships write tools including create/update/run and delete_airflow_job, with no description of a least-privilege Azure role set or confirmation prompts for dangerous operations; connection creation can target on-premises and virtual-network gateways, expanding the access surface into private networks. Risks are visible but permissions and confirmation are incomplete, and no red line is triggered, so 10.
- Maintenance 12/20
- Ownership is credible (microsoft org on GitHub) and the MIT license is explicit; the README documents contribution flow, extension points, and an architecture guide, indicating intent to maintain. Against that, no release history, commit cadence, dependency-update policy, or security-response channel (e.g. SECURITY.md) is visible in the supplied material, and 19 open issues with no visible response time suggest triage gaps. Not archived, but governance and versioning evidence is thin, so 12.
- Documentation 13/20
- Documentation is layered: README covers installation via NuGet/dnx plus a development config, lists all tools and the ui:// resource, links nine topic guides, states prerequisites, and documents optional Claude/ChatGPT skill packs, with Preview features labeled. Deductions: there is no per-tool parameter documentation, no rate-limit/quota/cost discussion, no troubleshooting section, and no explanation of access-token handling or revocation; the unreplaced version placeholders ("$(PackageVersion)" in the manifest, #{VERSION}# in README) create an undocumented substitution step. Usable but with hidden assumptions, so 13.
- Setup experience 11/20
- The install path is clear: the Microsoft.DataFactory.MCP NuGet package launched via dnx, with concrete client config examples for VS Code (.vscode/mcp.json) and Visual Studio (.mcp.json), plus a dotnet run development mode over stdio. Deductions: prerequisites are heavy (.NET 10.0 plus an Azure AD tenant and app registration with appropriate permissions), authentication setup is delegated to an external doc rather than spelled out, and both the manifest and README still contain version placeholders the user must resolve before the snippet works as copied. Manual runtime and credential preparation keeps this below the static ceiling of 15, at 11.