fabric-mcp@1.6.0
CAUTIONPublisher claims: "Microsoft Fabric MCP Server - Model Context Protocol implementation for Fabric" Observed in sandbox: static analysis only — behavior not yet observed.
Registry npm (MCP server)Publisher microsoft · joined 5 days agoInstalls 4,771Last detonated 49 min ago
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-10-26 and scored it 65/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Authorization escalation language; Coercive compliance language; False authorization claim. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyt+CategoryObserved action
This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
HIGH
Authorization escalation languageREADME.md:552 · Authorization escalation languageFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01HIGH
Coercive compliance languageREADME.md:738 · Coercive compliance languageFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01HIGH
False authorization claimREADME.md:158 · False authorization claim — impersonating privileged roleFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01HIGH
Authorization escalation languageREADME.md:303 · Authorization escalation languageFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01MEDIUM
npx invocation of non-well-known packageindex.js:278 · npx invocation of non-well-known package — may execute untrusted codeFix: Pin versions and sources; vendor anything fetched at install time.
AST06HIGH
False authorization claimREADME.md:143 · False authorization claim — impersonating privileged roleFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01MEDIUM
npx invocation of non-well-known packageindex.js:279 · npx invocation of non-well-known package — may execute untrusted codeFix: Pin versions and sources; vendor anything fetched at install time.
AST06HIGH
Authorization escalation languageREADME.md:314 · Authorization escalation languageFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01MEDIUM
npx invocation of non-well-known packageindex.js:280 · npx invocation of non-well-known package — may execute untrusted codeFix: Pin versions and sources; vendor anything fetched at install time.
AST06What would make this Verified
15 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim microsoft: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim microsoft