registry / record
@softeria/ms-365-mcp-server
Does @softeria/ms-365-mcp-server MCP work in Claude Code and Cursor? Throne executed @softeria/ms-365-mcp-server mcp in a single-use Firecracker microVM and replayed both recorded client behaviours. Compatibility verdict: fit. Is @softeria/ms-365-mcp-server mcp safe? Static security scan: 2 finding(s) to review under security ruleset v1. The full per-step results, security findings, scan date, and evidence hash are below.
> throne registry @softeria/ms-365-mcp-server
sealed
- scan id
- 1183983b3d594630b21efe19719a9e1b
- target
- @softeria/ms-365-mcp-server
- sealed at
- 2026-06-16 18:21:55Z
- evidence hash
- sha256:8e8e834ab8cf933df2e5d219d9c0e980862b510225b153380768894fe60ee64a
initialize ok: server Microsoft365MCP 0.124.1, negotiated protocolVersion 2025-11-25, capabilities ['tools']
supported: tools/list (178 tools); method not found (tolerated): resources/list, prompts/list
all 178 tool inputSchemas are valid JSON Schema
called 10 of 10 tools (cap 10, strategy=serial): 4 ok, 6 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived, wrong_type_args: login:accepted (returned result); logout:accepted (returned result); verify-login:accepted (returned result); list-accounts:accepted (returned result); select-account:accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive; oversized_input: accepted (returned result); recovery: accepted (returned result); cancellation: accepted (returned result); old_version: accepted old version 2024-10-07, negotiated 2024-10-07, server may have stale protocol handling
no streaming-capable tool declared by this server
resources capability not declared
ladder 1 overlapping login calls: max_observed_stable_concurrency=1; all ids answered exactly once at every level
transport closed and relaunched; re-handshake ok (protocolVersion 2025-11-25, first session was 2025-11-25)
initialize ok: server Microsoft365MCP 0.124.1, negotiated protocolVersion 2025-11-25, capabilities ['tools'] [request_strategy=pipelined, connection_count=2, second connection established]
supported: tools/list (178 tools); method not found (tolerated): resources/list, prompts/list; notes: connection 2 confirms 178 tools
all 178 tool inputSchemas are valid JSON Schema
called 10 of 10 tools (cap 10, strategy=pipelined): 4 ok, 6 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived, wrong_type_args: login:accepted (returned result); logout:accepted (returned result); verify-login:accepted (returned result); list-accounts:accepted (returned result); select-account:accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive; oversized_input: accepted (returned result); recovery: accepted (returned result); cancellation: accepted (returned result); old_version: accepted old version 2024-10-07, negotiated 2024-10-07, server may have stale protocol handling
no streaming-capable tool declared by this server
resources capability not declared
ladder 1/2/4/6 overlapping login calls: max_observed_stable_concurrency=6; all ids answered exactly once at every level
transport closed and relaunched; re-handshake ok (protocolVersion 2025-11-25, first session was 2025-11-25)
execSync() called with a dynamically built command (heuristic, review): ''
package/bin/modules/generate-mcp-tools.mjs:1911 non-local endpoint host(s) referenced in code, verify each is expected for this server's purpose: docs.microsoft.com (package/dist/generated/client.js:6788), graph.microsoft.com (package/dist/cloud-config.js:4), learn.microsoft.com (package/examples/azure-container-apps/deploy.ps1:59), login.chinacloudapi.cn (package/dist/cloud-config.js:8), login.microsoftonline.com (package/dist/cloud-config.js:3), mcp.example.com (package/dist/cli.js:49), microsoftgraph.chinacloudapi.cn (package/dist/cloud-config.js:9), portal.azure.cn (package/dist/cloud-config.js:10), portal.azure.com (package/dist/cloud-config.js:5), schema.management.azure.com (package/examples/azure-container-apps/deploy.ps1:124), teams.microsoft.com (package/dist/lib/teams-url-parser.js:18)
package/dist/cli.js:49- target
- @softeria/ms-365-mcp-server npm
- engine
- sandboxed
- claude code
- calibration: partial recorded=9,spec=0,assumed=9
- cursor
- calibration: partial recorded=11,spec=0,assumed=7
- chatgpt desktop
- calibration: unavailable recorded=0,spec=2,assumed=16
- steps exercised
- 14 of 18
- test suite
- v1.0.0
- security ruleset
- v1.0.0
- sealed at
- 2026-06-16 18:21:55Z
- evidence hash
- sha256:8e8e834ab8cf933df2e5d219d9c0e980862b510225b153380768894fe60ee64a
- valid until
- 2026-09-14
paste this in your README. it renders the live verdict and links back to this record. if a release ever breaks the verdict, the badge says so on its own.
[](https://usethrone.dev/server/softeria-ms-365-mcp-server)maintainer of this server? challenge this record: hello@usethrone.dev. tell us what we got wrong and we re-run it in the open.
this page renders the stored record of a real run. nothing on it is asserted without the execution that proved it.