Softeria/ms-365-mcp-server

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

14 of your 43 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.39s · analysis 22.6s · 1.1 MB · GitHub API rate-limit (preflight)

https://github.com/Softeria/ms-365-mcp-server · scanned 2026-06-05 21:54 UTC (1 week, 2 days ago) · 10 languages

143 raw signals (39 security + 104 graph) 73rd percentile · Typescript · small (2-20K LoC) System graph score 64 (higher by 17)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 2 days ago · v2 · 84 actionable findings from 2 signal sources. 7 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 51 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	72.9	0.25	18.23
`testing_score`	90.0	0.20	18.00
`documentation_score`	64.0	0.15	9.60
`practices_score`	84.0	0.15	12.60
`code_quality`	78.0	0.10	7.80
Overall		1.00	81.2

Severity distribution — click a segment to filter

Active filters: layer: api × excluding tests × Reset all

Severity: Critical 1 High 19 Medium 13 Low 43 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 33 System graph 51 Crowd 0 Layer: Quality 17 Security 3 Software 41 Cicd 5 Frontend 7 Hardware 4 Api 7

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Strongest security (92), testing (85); weakest documentation (48), practices (75).

Showing 7 of 84 actionable findings. 91 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.microsoft.com/v1.0/me/drive/root:${filePath}:/workbook/createSession (test/graph-api.test.ts:23)

`test/graph-api.test.ts:23` calls `POST https://graph.microsoft.com/v1.0/me/drive/root:${filePath}:/workbook/createSession` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.microsoft.com/v1.0/me/drive/roo…

Dangling fetchFetch

low System graph api Wiring conf 1.00 Unused endpoint: GET /

`src/server.ts` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /authorize

`src/server.ts` declares `GET /authorize` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /mcp

`src/server.ts` declares `GET /mcp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /mcp

`src/server.ts` declares `POST /mcp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /register

`src/server.ts` declares `POST /register` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /token

`src/server.ts` declares `POST /token` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/cf60e75b-602f-4bc7-a210-bb894994b861/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/cf60e75b-602f-4bc7-a210-bb894994b861/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.