C
Emerging
74/100
9 days ago

SharePoint MCP Bridge

A local MCP server that uses a Chromium extension to capture SharePoint Online session tokens, enabling supervised SharePoint operations (lists, files, permissions, modern pages) through Microsoft Graph and SharePoint REST without cloud token uploads.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

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

icemage001

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.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// known CVEs in dependencies1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

lowesbuild@0.27.4GHSA-g7r4-m6w7-qqqr

esbuild allows arbitrary file read when running the development server on Windows

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configSHAREPOINT_MCP_BRIDGE_HOST
configSHAREPOINT_MCP_BRIDGE_PORT
configSHAREPOINT_MCP_DATA_DIR"": "C:\\path\\to\\sharepoint-mcp\\data"
configSHAREPOINT_MCP_LIST_IDGallery 测试还需要明确批准的 和 SHAREPOINT_MCP_VIEW_ID。持久化 JSON 不等于 UI 已正确渲染,必须同时做 API readback 和 SharePoint UI 检查。
configSHAREPOINT_MCP_REAL_SITE_SMOKE$env: = 'true'
configSHAREPOINT_MCP_VIEW_IDGallery 测试还需要明确批准的 SHAREPOINT_MCP_LIST_ID 和 。持久化 JSON 不等于 UI 已正确渲染,必须同时做 API readback 和 SharePoint UI 检查。
// 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

75/75 tools missing one or more hints — get_health (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_captured_sites (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +72 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

Only 8/75 tool handlers declare input schemas (11%)

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

Tool test coverage

Only 21/75 tools referenced in tests (28%)

Write tests that reference each tool by name so every tool has at least one test.

Domain consistency

npm scope @local doesn't match GitHub owner icemage001

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 5 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/icemage001-local-sharepoint-mcp-1rdqdj)](https://m8ven.ai/mcp/icemage001-local-sharepoint-mcp-1rdqdj)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 1cbe991e901c40efaba8bd3655b91e73b630aa0f
code hash: aaebb412ae1822f422b70e9123d6887c9e02f65aa1f9d20cb73a07626793e8cf
verified: 8/13/2026, 8:08:33 AM
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