Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.theluckystrike/office-suite

MCPB · OFFICE-SUITE.MCPB

Local office proxy for invoices, spreadsheets and supplier statement open-item checks.

Available components

−1 this week 15 Trust /100

Last scanned (2 hours ago)

Scores higher than 60% of MCPB servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security23
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs were checked across the 264 of 265 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 264 of 265 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency39
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 −1
    • Maintenance: pass → unverified ▼ functional
    • Package version: 0.22.0 → 0.25.0 functional
  • 4 Nov 26 0
    • Package version: 0.22.0 → 0.25.0 functional
  • 3 Nov 26 0
    • Package version: 0.22.0 → 0.25.0 functional
  • 2 Nov 26 0
    • Package version: 0.22.0 → 0.25.0 functional
  • 1 Nov 26 0
    • Package version: 0.22.0 → 0.25.0 functional
  • 30 Oct 26 0
    • Package version: 0.22.0 → 0.25.0 functional
  • 29 Oct 26 0
    • Package version: 0.22.0 → 0.25.0 functional
  • 27 Oct 26 0
    • Stability: Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess. functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.25.0/office-suite.mcpb@0.25.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 264 packages
Packages resolved 264
Deprecated 2
Stale 102
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the io.github.theluckystrike/office-suite MCP server?

io.github.theluckystrike/office-suite ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 4918b493051b5a2c067c73013d093a0da08c9a41f8ac8ecd8f538107c167fb1a; the commands to do that are on this page. If it does not match, do not open it.

mcpb · office-suite.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

4918b493051b5a2c067c73013d093a0da08c9a41f8ac8ecd8f538107c167fb1a

macOS / Linux

echo "4918b493051b5a2c067c73013d093a0da08c9a41f8ac8ecd8f538107c167fb1a  office-suite.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\office-suite.mcpb).Hash -eq "4918b493051b5a2c067c73013d093a0da08c9a41f8ac8ecd8f538107c167fb1a"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the io.github.theluckystrike/office-suite MCP server?

io.github.theluckystrike/office-suite is an MCP server listed in the public MCP registry as io.github.theluckystrike/office-suite. Local office proxy for invoices, spreadsheets and supplier statement open-item checks. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.25.0/office-suite.mcpb).

Is the io.github.theluckystrike/office-suite MCP server safe to use?

io.github.theluckystrike/office-suite scores 15 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What licence is the io.github.theluckystrike/office-suite MCP server under?

io.github.theluckystrike/office-suite declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.