C
Limited view
67/100
2 months ago

ms-fabric-mcp-server

Enables AI agents to interact with Microsoft Fabric by exposing tools for managing workspaces, notebooks, SQL queries, pipelines, and Livy Spark sessions. It provides a comprehensive set of operations for data engineering and analytics tasks using standard Azure authentication.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

bablulawrence

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configFABRIC_API_CALL_TIMEOUT30 API timeout (seconds)
configFABRIC_MAX_RETRIES3 Max retry attempts
configFABRIC_RETRY_BACKOFF2.0 Backoff factor
configLIVY_API_CALL_TIMEOUT120 Livy timeout (seconds)
configLIVY_POLL_INTERVAL2.0 Livy polling interval
configLIVY_STATEMENT_WAIT_TIMEOUT10 Livy statement wait timeout
configLIVY_SESSION_WAIT_TIMEOUT240 Livy session wait timeout
configPOWERBI_API_CALL_TIMEOUTPower BI tuning: POWERBI_BASE_URL, POWERBI_SCOPES, , POWERBI_REFRESH_POLL_INTERVAL, POWERBI_REFRESH_WAIT_TIMEOUT
configPOWERBI_REFRESH_POLL_INTERVALPower BI tuning: POWERBI_BASE_URL, POWERBI_SCOPES, POWERBI_API_CALL_TIMEOUT, , POWERBI_REFRESH_WAIT_TIMEOUT
configPOWERBI_REFRESH_WAIT_TIMEOUTPower BI tuning: POWERBI_BASE_URL, POWERBI_SCOPES, POWERBI_API_CALL_TIMEOUT, POWERBI_REFRESH_POLL_INTERVAL,
configMCP_LOG_LEVELYou can also set AZURE_LOG_LEVEL (Azure SDK) and (server) to control verbosity.
configMCP_SERVER_NAMEms-fabric-mcp-server Server name for MCP
configFABRIC_ODBC_DRIVERSQL tools require pyodbc and the Microsoft ODBC Driver for SQL Server (Driver 18 or 17 — the service auto-detects which is installed and prefers Driver 18; set to override):
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

61/61 tools missing one or more hints — create_dataflow (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_dataflow_definition (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); run_dataflow (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +58 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

60/61 tool handlers declare input schemas (98%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 9/61 tool handlers wrap calls in try/catch (15%)

Wrap each tool handler body in try/catch and return a structured error response.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/bablulawrence-ms-fabric-mcp-server-16mj47)](https://m8ven.ai/mcp/bablulawrence-ms-fabric-mcp-server-16mj47)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 3c2352bfea6b40561622f3508aadb1ec3b6a0e0c
code hash: 0d08d40be8b6e3c7b854af1d9c6b47f5e5e2be169d6b7a2343bbb908344244c3
verified: 6/17/2026, 12:12:21 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client