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.

Blumira MCP

MCPB · BLUMIRA-MCP.MCPB

Cross-account Blumira findings, detections, and agents in one offline-searchable store.

Available components

+1 this week 50 Trust /100

Last scanned (23 hours ago)

Scores higher than 80% of MCPB servers

Category Security

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 Security0
  • 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 could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 12 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 20533 tokens (~336/item across 61 items; 61 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management99
  • Stability check failed: the tool surface changed between 0.1.3 and 0.1.6: 0 tool removals, 1 breaking changes, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "triage" implies "merge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 61 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 96.

  • 27 Oct 26 +1
    • Package version: 0.1.3 → 0.1.6 functional
  • 25 Oct 26 +2
    • Maintenance: unverified → pass ▲ functional
  • 23 Oct 26 −1
    • Stability: 0.73 → fail ▼ security
    • Maintenance: pass → unverified ▼ functional
    • Schema quality: excellent → good functional
    • Package version: 0.1.5 → 0.1.6 functional
  • 22 Oct 26 +1
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.70 → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.1.4 → 0.1.5 functional
  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 0
    • Package version: 0.1.3 → 0.1.4 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 4 Nov 2026 · Analysed mcpb/https://github.com/Servosity/msp-skills/releases/download/blumira-v0.1.6/blumira-mcp.mcpb@0.1.6

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 →

MCP tools · 61 exposed · ~20,533 tokens

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 →

Tool Tokens
analytics ~499

Analyze locally synced data with count, group-by, and summary operations. Data must be synced first with the sync command.

NameTypeReqDescription
agentboolean–Set all agent-friendly defaults (--json --compact --no-input --no-color --yes) (default: false)
allow-partial-failureboolean–Downgrade response-body partial-failure (e.g. partialFailureError) to a warning instead of a non-zero exit (default: false)
compactboolean–Return only key fields (id, name, status, timestamps) for minimal token usage (default: false)
csvboolean–Output as CSV (table and array responses) (default: false)
data-sourcestring–Data source for read commands: auto (live with local fallback), live (API only), local (synced data only) (default: auto)
dry-runboolean–Show request without sending (default: false)
group-bystring–Field to group by
human-friendlyboolean–Enable colored output and rich formatting (default: false)
idempotentboolean–Treat already-existing create results as a successful no-op (default: false)
jsonboolean–Output as JSON (default: false)
limitnumber–Max groups to show (default: 25)
max-agestring–Maximum acceptable age of local-store data before a stderr hint suggests sync; 0 disables (default: 30m0s)
no-cacheboolean–Bypass response cache (default: false)
no-colorboolean–Disable colored output (default: false)
no-inputboolean–Disable all interactive prompts (for CI/agents) (default: false)
plainboolean–Output as plain tab-separated text (default: false)
quietboolean–Bare output, one value per line (default: false)
rate-limitnumber–Max requests per second (0 to disable) (default: 0)
selectstring–Comma-separated fields to include in output (e.g. --select id,name,status)
timeoutstring–Request timeout (default: 1m0s)
typestring–Resource type to analyze
yesboolean–Skip confirmation prompts (for agents and scripts) (default: false)

No output schema declared.

No examples provided.

audit ~513

Scan the snapshot history for findings that were marked resolved in one sync and then appeared non-resolved in a later sync — a signal of premature or low-quality resolutions. Reads the local store's snapshot history (accrues as 'sync' runs).

NameTypeReqDescription
agentboolean–Set all agent-friendly defaults (--json --compact --no-input --no-color --yes) (default: false)
allow-partial-failureboolean–Downgrade response-body partial-failure (e.g. partialFailureError) to a warning instead of a non-zero exit (default: false)
compactboolean–Return only key fields (id, name, status, timestamps) for minimal token usage (default: false)
csvboolean–Output as CSV (table and array responses) (default: false)
data-sourcestring–Data source for read commands: auto (live with local fallback), live (API only), local (synced data only) (default: auto)
dry-runboolean–Show request without sending (default: false)
human-friendlyboolean–Enable colored output and rich formatting (default: false)
idempotentboolean–Treat already-existing create results as a successful no-op (default: false)
jsonboolean–Output as JSON (default: false)
max-agestring–Maximum acceptable age of local-store data before a stderr hint suggests sync; 0 disables (default: 30m0s)
min-reopensnumber–Only show findings re-fired at least this many times (default: 1)
no-cacheboolean–Bypass response cache (default: false)
no-colorboolean–Disable colored output (default: false)
no-inputboolean–Disable all interactive prompts (for CI/agents) (default: false)
plainboolean–Output as plain tab-separated text (default: false)
quietboolean–Bare output, one value per line (default: false)
rate-limitnumber–Max requests per second (0 to disable) (default: 0)
selectstring–Comma-separated fields to include in output (e.g. --select id,name,status)
timeoutstring–Request timeout (default: 1m0s)
yesboolean–Skip confirmation prompts (for agents and scripts) (default: false)

No output schema declared.

No examples provided.

context ~29

Get API domain context: resource taxonomy, auth requirements, query tips, and unique capabilities. Call this first.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

coverage ~518

Join the MSP basis detection rules against your org's deployed rules (matched by rule name) and report each basis rule that is missing or not enabled. Reads the local store; sync 'msp-basis-detection-rules' and 'org-detection-rules' first.

NameTypeReqDescription
againststring–Baseline to compare against (only 'basis' is supported) (default: basis)
agentboolean–Set all agent-friendly defaults (--json --compact --no-input --no-color --yes) (default: false)
allow-partial-failureboolean–Downgrade response-body partial-failure (e.g. partialFailureError) to a warning instead of a non-zero exit (default: false)
compactboolean–Return only key fields (id, name, status, timestamps) for minimal token usage (default: false)
csvboolean–Output as CSV (table and array responses) (default: false)
data-sourcestring–Data source for read commands: auto (live with local fallback), live (API only), local (synced data only) (default: auto)
dry-runboolean–Show request without sending (default: false)
human-friendlyboolean–Enable colored output and rich formatting (default: false)
idempotentboolean–Treat already-existing create results as a successful no-op (default: false)
jsonboolean–Output as JSON (default: false)
max-agestring–Maximum acceptable age of local-store data before a stderr hint suggests sync; 0 disables (default: 30m0s)
no-cacheboolean–Bypass response cache (default: false)
no-colorboolean–Disable colored output (default: false)
no-inputboolean–Disable all interactive prompts (for CI/agents) (default: false)
plainboolean–Output as plain tab-separated text (default: false)
quietboolean–Bare output, one value per line (default: false)
rate-limitnumber–Max requests per second (0 to disable) (default: 0)
selectstring–Comma-separated fields to include in output (e.g. --select id,name,status)
timeoutstring–Request timeout (default: 1m0s)
yesboolean–Skip confirmation prompts (for agents and scripts) (default: false)

No output schema declared.

No examples provided.

dc_roster ~537

Use this command for the plain inventory roster of all domain controllers and their agent check-in state (protected, stale, or never-checked-in). Do NOT use this command for the prioritized list of stale/unprotected DCs needing action; use 'exposure' instead. Reads the local store.

NameTypeReqDescription
agentboolean–Set all agent-friendly defaults (--json --compact --no-input --no-color --yes) (default: false)
allow-partial-failureboolean–Downgrade response-body partial-failure (e.g. partialFailureError) to a warning instead of a non-zero exit (default: false)
compactboolean–Return only key fields (id, name, status, timestamps) for minimal token usage (default: false)
csvboolean–Output as CSV (table and array responses) (default: false)
data-sourcestring–Data source for read commands: auto (live with local fallback), live (API only), local (synced data only) (default: auto)
dry-runboolean–Show request without sending (default: false)
human-friendlyboolean–Enable colored output and rich formatting (default: false)
idempotentboolean–Treat already-existing create results as a successful no-op (default: false)
jsonboolean–Output as JSON (default: false)
max-agestring–Maximum acceptable age of local-store data before a stderr hint suggests sync; 0 disables (default: 30m0s)
no-cacheboolean–Bypass response cache (default: false)
no-colorboolean–Disable colored output (default: false)
no-inputboolean–Disable all interactive prompts (for CI/agents) (default: false)
plainboolean–Output as plain tab-separated text (default: false)
quietboolean–Bare output, one value per line (default: false)
rate-limitnumber–Max requests per second (0 to disable) (default: 0)
selectstring–Comma-separated fields to include in output (e.g. --select id,name,status)
stale-afterstring–Treat a DC as stale if last seen longer ago than this (e.g. 12h, 1d) (default: 24h)
timeoutstring–Request timeout (default: 1m0s)
yesboolean–Skip confirmation prompts (for agents and scripts) (default: false)

No output schema declared.

No examples provided.

drift ~526

Compare the two most recent finding snapshots and report what changed: new findings, status changes, and newly-resolved findings. Each run records the current state as a snapshot, so drift becomes available after a second sync. Reads (and appends to) the local store's snapshot history.

NameTypeReqDescription
agentboolean–Set all agent-friendly defaults (--json --compact --no-input --no-color --yes) (default: false)
allow-partial-failureboolean–Downgrade response-body partial-failure (e.g. partialFailureError) to a warning instead of a non-zero exit (default: false)
compactboolean–Return only key fields (id, name, status, timestamps) for minimal token usage (default: false)
csvboolean–Output as CSV (table and array responses) (default: false)
data-sourcestring–Data source for read commands: auto (live with local fallback), live (API only), local (synced data only) (default: auto)
dry-runboolean–Show request without sending (default: false)
human-friendlyboolean–Enable colored output and rich formatting (default: false)
idempotentboolean–Treat already-existing create results as a successful no-op (default: false)
jsonboolean–Output as JSON (default: false)
max-agestring–Maximum acceptable age of local-store data before a stderr hint suggests sync; 0 disables (default: 30m0s)
no-cacheboolean–Bypass response cache (default: false)
no-colorboolean–Disable colored output (default: false)
no-inputboolean–Disable all interactive prompts (for CI/agents) (default: false)
plainboolean–Output as plain tab-separated text (default: false)
quietboolean–Bare output, one value per line (default: false)
rate-limitnumber–Max requests per second (0 to disable) (default: 0)
selectstring–Comma-separated fields to include in output (e.g. --select id,name,status)
sincestring–Hint window (e.g. 24h, 1d); drift compares the two most recent syncs regardless
timeoutstring–Request timeout (default: 1m0s)
yesboolean–Skip confirmation prompts (for agents and scripts) (default: false)

No output schema declared.

No examples provided.

evidence_search ~645

Use this command to find findings whose EVIDENCE rows contain a term (IOC, hostname, user) when you do NOT already know the finding ID. Do NOT use this command for searching finding names/categories; use 'search "term" --type findings' instead. Searches the local evidence cache plus the raw synced finding payloads. The API only returns evidence per known finding ID, so 'which findings mention this IP' is impossible upstream. Pass --fetch to populate the cache live: evidence is pulled for open synced findings (bounded by --max-fetch) before searching.

NameTypeReqDescription
agentboolean–Set all agent-friendly defaults (--json --compact --no-input --no-color --yes) (default: false)
allow-partial-failureboolean–Downgrade response-body partial-failure (e.g. partialFailureError) to a warning instead of a non-zero exit (default: false)
argsstring–Additional positional arguments or raw CLI flags to append to the command.
compactboolean–Return only key fields (id, name, status, timestamps) for minimal token usage (default: false)
csvboolean–Output as CSV (table and array responses) (default: false)
data-sourcestring–Data source for read commands: auto (live with local fallback), live (API only), local (synced data only) (default: auto)
dry-runboolean–Show request without sending (default: false)
fetchboolean–Fetch evidence live for open synced findings before searching (bounded by --max-fetch) (default: false)
human-friendlyboolean–Enable colored output and rich formatting (default: false)
idempotentboolean–Treat already-existing create results as a successful no-op (default: false)
jsonboolean–Output as JSON (default: false)
limitnumber–Maximum matches to return (default: 50)
max-agestring–Maximum acceptable age of local-store data before a stderr hint suggests sync; 0 disables (default: 30m0s)
max-fetchnumber–Maximum findings to fetch evidence for when --fetch is set (default: 25)
no-cacheboolean–Bypass response cache (default: false)
no-colorboolean–Disable colored output (default: false)
no-inputboolean–Disable all interactive prompts (for CI/agents) (default: false)
plainboolean–Output as plain tab-separated text (default: false)
quietboolean–Bare output, one value per line (default: false)
rate-limitnumber–Max requests per second (0 to disable) (default: 0)
selectstring–Comma-separated fields to include in output (e.g. --select id,name,status)
timeoutstring–Request timeout (default: 1m0s)
yesboolean–Skip confirmation prompts (for agents and scripts) (default: false)

No output schema declared.

No examples provided.

export ~542

Export paginated API data to a local file. Supports JSONL (one JSON object per line, streaming-friendly) and JSON (array). JSONL is recommended for large datasets as it has no memory pressure.

NameTypeReqDescription
agentboolean–Set all agent-friendly defaults (--json --compact --no-input --no-color --yes) (default: false)
allow-partial-failureboolean–Downgrade response-body partial-failure (e.g. partialFailureError) to a warning instead of a non-zero exit (default: false)
argsstring–Additional positional arguments or raw CLI flags to append to the command.
compactboolean–Return only key fields (id, name, status, timestamps) for minimal token usage (default: false)
csvboolean–Output as CSV (table and array responses) (default: false)
data-sourcestring–Data source for read commands: auto (live with local fallback), live (API only), local (synced data only) (default: auto)
dry-runboolean–Show request without sending (default: false)
formatstring–Output format: jsonl or json (default: jsonl)
human-friendlyboolean–Enable colored output and rich formatting (default: false)
idempotentboolean–Treat already-existing create results as a successful no-op (default: false)
jsonboolean–Output as JSON (default: false)
limitnumber–Maximum records to export (0 = unlimited) (default: 0)
max-agestring–Maximum acceptable age of local-store data before a stderr hint suggests sync; 0 disables (default: 30m0s)
no-cacheboolean–Bypass response cache for fresh data (default: false)
no-colorboolean–Disable colored output (default: false)
no-inputboolean–Disable all interactive prompts (for CI/agents) (default: false)
plainboolean–Output as plain tab-separated text (default: false)
quietboolean–Bare output, one value per line (default: false)
rate-limitnumber–Max requests per second (0 to disable) (default: 0)
selectstring–Comma-separated fields to include in output (e.g. --select id,name,status)
timeoutstring–Request timeout (default: 1m0s)
yesboolean–Skip confirmation prompts (for agents and scripts) (default: false)

No output schema declared.

No examples provided.

exposure ~554

Roll up synced agent devices and flag the concerning ones: stale check-in, never checked in, isolated, excluded, or sleeping. Domain controllers sort first. Use --flag-dc-stale to restrict to domain controllers. Reads the local store.

NameTypeReqDescription
agentboolean–Set all agent-friendly defaults (--json --compact --no-input --no-color --yes) (default: false)
allow-partial-failureboolean–Downgrade response-body partial-failure (e.g. partialFailureError) to a warning instead of a non-zero exit (default: false)
compactboolean–Return only key fields (id, name, status, timestamps) for minimal token usage (default: false)
csvboolean–Output as CSV (table and array responses) (default: false)
data-sourcestring–Data source for read commands: auto (live with local fallback), live (API only), local (synced data only) (default: auto)
dry-runboolean–Show request without sending (default: false)
flag-dc-staleboolean–Restrict to domain controllers (flag stale/unprotected DCs only) (default: false)
human-friendlyboolean–Enable colored output and rich formatting (default: false)
idempotentboolean–Treat already-existing create results as a successful no-op (default: false)
jsonboolean–Output as JSON (default: false)
max-agestring–Maximum acceptable age of local-store data before a stderr hint suggests sync; 0 disables (default: 30m0s)
no-cacheboolean–Bypass response cache (default: false)
no-colorboolean–Disable colored output (default: false)
no-inputboolean–Disable all interactive prompts (for CI/agents) (default: false)
plainboolean–Output as plain tab-separated text (default: false)
quietboolean–Bare output, one value per line (default: false)
rate-limitnumber–Max requests per second (0 to disable) (default: 0)
selectstring–Comma-separated fields to include in output (e.g. --select id,name,status)
stale-afterstring–Treat an agent as stale if last seen longer ago than this (e.g. 12h, 1d) (default: 24h)
timeoutstring–Request timeout (default: 1m0s)
yesboolean–Skip confirmation prompts (for agents and scripts) (default: false)

No output schema declared.

No examples provided.

find_unprotected_domain_controllers ~48

List domain controllers across all accounts whose agent check-in is stale or missing.

NameTypeReqDescription
flag_dc_staleboolean–Override the recipe's --flag-dc-stale value.

No output schema declared.

No examples provided.

health_search ~17

Get API health. Returns the ResponseHealth.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

import ~517

Import data from a JSONL file by issuing POST requests for each record. Each line must be a valid JSON object. Failed records are logged to stderr but do not stop the import.

NameTypeReqDescription
agentboolean–Set all agent-friendly defaults (--json --compact --no-input --no-color --yes) (default: false)
allow-partial-failureboolean–Downgrade response-body partial-failure (e.g. partialFailureError) to a warning instead of a non-zero exit (default: false)
argsstring–Additional positional arguments or raw CLI flags to append to the command.
batch-sizenumber–Records per batch (future: batch API support) (default: 1)
compactboolean–Return only key fields (id, name, status, timestamps) for minimal token usage (default: false)
csvboolean–Output as CSV (table and array responses) (default: false)
data-sourcestring–Data source for read commands: auto (live with local fallback), live (API only), local (synced data only) (default: auto)
dry-runboolean–Preview import without sending requests (default: false)
human-friendlyboolean–Enable colored output and rich formatting (default: false)
idempotentboolean–Treat already-existing create results as a successful no-op (default: false)
jsonboolean–Output as JSON (default: false)
max-agestring–Maximum acceptable age of local-store data before a stderr hint suggests sync; 0 disables (default: 30m0s)
no-cacheboolean–Bypass response cache (default: false)
no-colorboolean–Disable colored output (default: false)
no-inputboolean–Disable all interactive prompts (for CI/agents) (default: false)
plainboolean–Output as plain tab-separated text (default: false)
quietboolean–Bare output, one value per line (default: false)
rate-limitnumber–Max requests per second (0 to disable) (default: 0)
selectstring–Comma-separated fields to include in output (e.g. --select id,name,status)
timeoutstring–Request timeout (default: 1m0s)
yesboolean–Skip confirmation prompts (for agents and scripts) (default: false)

No output schema declared.

No examples provided.

msp_add-account-finding-comment ~167

Add a comment to a finding for your MSP sub-account. Required: account_id, finding_id, body, sender. Returns the new FindingsCommentsRecord.

NameTypeReqDescription
account_idstringyesAccount ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
bodystringyesComment body (required, non-empty). May contain HTML.
finding_idstringyesFinding ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
senderstringyesUUID of the person creating the comment. Use GET /org/users or GET /msp/accounts/{account_id}/users to obtain user IDs.

No output schema declared.

No examples provided.

msp_get ~67

Get a specific MSP sub-account by ID. Required: account_id. Returns the ResponseMspSubaccountRecord.

NameTypeReqDescription
account_idstringyesAccount ID of the object, e.g., '00110011-0000-0000-0000-000000000000'

No output schema declared.

No examples provided.

msp_get-account-agents-devices ~199

Get or search agents devices for your MSP sub-account. Required: account_id. Optional: page (default: 1), page_size (default: 50), limit (default: 200) (plus 1 more). Returns array of MspGetAccountAgentsDevicesItem.

NameTypeReqDescription
account_idstringyesAccount ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
limitnumber–Maximum number of records to return, e.g., '200'
order_bystring–Order records by field, e.g., 'created', 'created;asc', 'created;desc', 'name;desc,created;desc'
pagenumber–Page to return, e.g., '2'
page_sizenumber–Number of records per page to return, e.g., '3'

No output schema declared.

No examples provided.

msp_get-account-agents-keys ~199

Get or search agents keys for your MSP sub-account. Required: account_id. Optional: page (default: 1), page_size (default: 50), limit (default: 200) (plus 1 more). Returns array of MspGetAccountAgentsKeysItem.

NameTypeReqDescription
account_idstringyesAccount ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
limitnumber–Maximum number of records to return, e.g., '200'
order_bystring–Order records by field, e.g., 'created', 'created;asc', 'created;desc', 'name;desc,created;desc'
pagenumber–Page to return, e.g., '2'
page_sizenumber–Number of records per page to return, e.g., '3'

No output schema declared.

No examples provided.

msp_get-account-finding ~108

Get a specific finding by ID for your MSP sub-account. Required: account_id, finding_id. Returns the FindingDetailRecord.

NameTypeReqDescription
account_idstringyesAccount ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
finding_idstringyesFinding ID of the object, e.g., '00110011-0000-0000-0000-000000000000'

No output schema declared.

No examples provided.

msp_get-account-finding-comments ~110

Get comments for a specific finding for your MSP sub-account. Required: account_id, finding_id. Returns array of FindingsCommentsRecord.

NameTypeReqDescription
account_idstringyesAccount ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
finding_idstringyesFinding ID of the object, e.g., '00110011-0000-0000-0000-000000000000'

No output schema declared.

No examples provided.

msp_get-account-finding-evidence ~260

Returns evidence keys and a paginated first page of evidence rows for the finding in one call. Same contract as GET /org/findings/{finding_id}/evidence; finding must belong to the sub-account (account_id). Required: account_id, finding_id. Optional: page (default: 1), page_size (default: 50), limit (default: 200) (plus 1 more).

NameTypeReqDescription
account_idstringyesAccount ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
finding_idstringyesFinding ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
limitnumber–Maximum number of records to return, e.g., '200'
order_bystring–Order records by field, e.g., 'created', 'created;asc', 'created;desc', 'name;desc,created;desc'
pagenumber–Page to return, e.g., '2'
page_sizenumber–Number of records per page to return, e.g., '3'

No output schema declared.

No examples provided.

msp_get-account-findings ~1,508

Get or search findings for your MSP sub-account. Required: account_id. Optional: page (default: 1), page_size (default: 50), limit (default: 200) (plus 71 more). Returns array of FindingDetailRecord.

NameTypeReqDescription
account_idstringyesAccount ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
blockedboolean–If included, filter findings with blocked either True of False
blocked-eq-2boolean–If included, filter out findings with blocked either True of False
blocked.eqboolean–If included, filter findings with blocked either True of False
categorynumber–Category ID of finding
category-eq-2number–Category ID of finding to filter out
category-in-2string–Comma-separated list of category IDs of findings to filter out
category.eqnumber–Category ID of finding
category.instring–Comma-separated list of category IDs of findings to include
createdstring–Exact time object was created
created-eq-2string–Filter out findings with the given exact time of creation
created-gt-2string–End time of window for search (implied UTC) (inclusive)
created-lt-2string–Start time of window for search (implied UTC) (inclusive)
created.eqstring–Exact time object was created
created.gtstring–Start time of window for search (implied UTC) (exclusive)
created.ltstring–End time of window for search (implied UTC) (exclusive)
created_afterstring–Start time of window for search (implied UTC)
created_beforestring–End time of window for search (implied UTC)
created_bystring–If specified, limit search to findings created_by person with given UUID
limitnumber–Maximum number of records to return, e.g., '200'
modifiedstring–Exact time object was modified
modified-by-eq-2string–Filter out findings where person who last modified it has the given UUID
modified-by-in-2string–Filter out findings where person who last modified it in the given comma-separated list of UUIDs
modified-eq-2string–Filter out findings with the given exact time of modification
modified-gt-2string–End time of window for search (implied UTC) (inclusive)
modified-lt-2string–Start time of window for search (implied UTC) (inclusive)
modified.eqstring–Exact time object was modified
modified.gtstring–Start time of window for search (implied UTC) (exclusive)
modified.ltstring–End time of window for search (implied UTC) (exclusive)
modified_afterstring–Start time of window for search (implied UTC)
modified_beforestring–End time of window for search (implied UTC)
modified_bystring–UUID of person who last modified finding
modified_by.eqstring–UUID of person who last modified finding
modified_by.instring–Comma-separated list of UUIDs of persons who last modified finding
namestring–If specified, will limit search to findings with given name
name-contains-2string–If specified, will filter out findings with given name substring
name-eq-2string–If specified, will filter out findings with given name
name-in-2string–If specified, will filter out findings with any of the given comma-separated list of names
name-regex-2string–If specified, will filter out findings with name partially matching given regular expression
name.containsstring–If specified, will limit search to findings with given name substring
name.eqstring–If specified, will limit search to findings with given name
name.instring–If specified, will limit search to findings with one of the given comma-separated list of names
name.regexstring–If specified, will limit search to findings with name partially matching given regular expression
order_bystring–Order records by field, e.g., 'created', 'created;asc', 'created;desc', 'name;desc,created;desc'
pagenumber–Page to return, e.g., '2'
page_sizenumber–Number of records per page to return, e.g., '3'
prioritynumber–Priority number of finding
priority-eq-2number–Priority number of finding to filter out
priority-gt-2number–Maximum priority number of finding to include
priority-in-2string–Comma-separated list of priority numbers of findings to filter out
priority-lt-2number–Minimum priority number of finding to include
priority.eqnumber–Priority number of finding
priority.gtnumber–Maximum priority number of finding to exclude
priority.instring–Comma-separated list of priority numbers of findings to include
priority.ltnumber–Minimum priority number of finding to exclude
resolutionnumber–Resolution ID of finding
resolution-eq-2number–Resolution ID of finding to filter out
resolution-in-2number–Comma-separated list of resolution IDs of findings to filter out
resolution.eqnumber–Resolution ID of finding
resolution.innumber–Comma-separated list of Resolution IDs of findings to include
statusnumber–Status ID of finding
status-eq-2number–Status ID of finding to filter out
status-in-2string–Comma-separated list of status IDs of findings to filter out
status-modified-by-eq-2string–UUID of person who last modified finding status
status-modified-by-in-2string–Comma-separated list of UUIDs of persons who last modified finding status to be filtered out
status.eqnumber–Status ID of finding
status.instring–Comma-separated list of status IDs of findings to include
status_modified_bystring–UUID of person who last modified finding status
status_modified_by.eqstring–UUID of person who last modified finding status
status_modified_by.instring–Comma-separated list of UUIDs of persons who last modified finding status
typenumber–Integer type id
type-eq-2number–Integer type id to filter out
type-in-2string–Comma-separated list of integer type IDs to filter out
type.eqnumber–Integer type id
type.instring–Comma-separated list of integer type IDs to include

No output schema declared.

No examples provided.

msp_get-accounts ~153

Get or search sub-accounts for your MSP. Optional: page (default: 1), page_size (default: 50), limit (default: 200) (plus 1 more). Returns array of MspGetAccountsItem.

NameTypeReqDescription
limitnumber–Maximum number of records to return, e.g., '200'
order_bystring–Order records by field, e.g., 'created', 'created;asc', 'created;desc', 'name;desc,created;desc'
pagenumber–Page to return, e.g., '2'
page_sizenumber–Number of records per page to return, e.g., '3'

No output schema declared.

No examples provided.

msp_get-accounts-findings ~1,471

Get or search findings for all your MSP sub-accounts. Optional: page (default: 1), page_size (default: 50), limit (default: 200) (plus 71 more). Returns array of FindingDetailRecord.

NameTypeReqDescription
blockedboolean–If included, filter findings with blocked either True of False
blocked-eq-2boolean–If included, filter out findings with blocked either True of False
blocked.eqboolean–If included, filter findings with blocked either True of False
categorynumber–Category ID of finding
category-eq-2number–Category ID of finding to filter out
category-in-2string–Comma-separated list of category IDs of findings to filter out
category.eqnumber–Category ID of finding
category.instring–Comma-separated list of category IDs of findings to include
createdstring–Exact time object was created
created-eq-2string–Filter out findings with the given exact time of creation
created-gt-2string–End time of window for search (implied UTC) (inclusive)
created-lt-2string–Start time of window for search (implied UTC) (inclusive)
created.eqstring–Exact time object was created
created.gtstring–Start time of window for search (implied UTC) (exclusive)
created.ltstring–End time of window for search (implied UTC) (exclusive)
created_afterstring–Start time of window for search (implied UTC)
created_beforestring–End time of window for search (implied UTC)
created_bystring–If specified, limit search to findings created_by person with given UUID
limitnumber–Maximum number of records to return, e.g., '200'
modifiedstring–Exact time object was modified
modified-by-eq-2string–Filter out findings where person who last modified it has the given UUID
modified-by-in-2string–Filter out findings where person who last modified it in the given comma-separated list of UUIDs
modified-eq-2string–Filter out findings with the given exact time of modification
modified-gt-2string–End time of window for search (implied UTC) (inclusive)
modified-lt-2string–Start time of window for search (implied UTC) (inclusive)
modified.eqstring–Exact time object was modified
modified.gtstring–Start time of window for search (implied UTC) (exclusive)
modified.ltstring–End time of window for search (implied UTC) (exclusive)
modified_afterstring–Start time of window for search (implied UTC)
modified_beforestring–End time of window for search (implied UTC)
modified_bystring–UUID of person who last modified finding
modified_by.eqstring–UUID of person who last modified finding
modified_by.instring–Comma-separated list of UUIDs of persons who last modified finding
namestring–If specified, will limit search to findings with given name
name-contains-2string–If specified, will filter out findings with given name substring
name-eq-2string–If specified, will filter out findings with given name
name-in-2string–If specified, will filter out findings with any of the given comma-separated list of names
name-regex-2string–If specified, will filter out findings with name partially matching given regular expression
name.containsstring–If specified, will limit search to findings with given name substring
name.eqstring–If specified, will limit search to findings with given name
name.instring–If specified, will limit search to findings with one of the given comma-separated list of names
name.regexstring–If specified, will limit search to findings with name partially matching given regular expression
order_bystring–Order records by field, e.g., 'created', 'created;asc', 'created;desc', 'name;desc,created;desc'
pagenumber–Page to return, e.g., '2'
page_sizenumber–Number of records per page to return, e.g., '3'
prioritynumber–Priority number of finding
priority-eq-2number–Priority number of finding to filter out
priority-gt-2number–Maximum priority number of finding to include
priority-in-2string–Comma-separated list of priority numbers of findings to filter out
priority-lt-2number–Minimum priority number of finding to include
priority.eqnumber–Priority number of finding
priority.gtnumber–Maximum priority number of finding to exclude
priority.instring–Comma-separated list of priority numbers of findings to include
priority.ltnumber–Minimum priority number of finding to exclude
resolutionnumber–Resolution ID of finding
resolution-eq-2number–Resolution ID of finding to filter out
resolution-in-2number–Comma-separated list of resolution IDs of findings to filter out
resolution.eqnumber–Resolution ID of finding
resolution.innumber–Comma-separated list of Resolution IDs of findings to include
statusnumber–Status ID of finding
status-eq-2number–Status ID of finding to filter out
status-in-2string–Comma-separated list of status IDs of findings to filter out
status-modified-by-eq-2string–UUID of person who last modified finding status
status-modified-by-in-2string–Comma-separated list of UUIDs of persons who last modified finding status to be filtered out
status.eqnumber–Status ID of finding
status.instring–Comma-separated list of status IDs of findings to include
status_modified_bystring–UUID of person who last modified finding status
status_modified_by.eqstring–UUID of person who last modified finding status
status_modified_by.instring–Comma-separated list of UUIDs of persons who last modified finding status
typenumber–Integer type id
type-eq-2number–Integer type id to filter out
type-in-2string–Comma-separated list of integer type IDs to filter out
type.eqnumber–Integer type id
type.instring–Comma-separated list of integer type IDs to include

No output schema declared.

No examples provided.

msp_get-agents-device ~111

Get a specific agents device by ID for your MSP sub-account. Required: account_id, device_id. Returns the ResponseAgentsDeviceDetailRecord.

NameTypeReqDescription
account_idstringyesAccount ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
device_idstringyesDevice ID of the object, e.g., '00110011-0000-0000-0000-000000000000'

No output schema declared.

No examples provided.

msp_get-agents-key ~111

Get a specific agents key by ID for your MSP sub-account. Required: account_id, key_id. Returns the ResponseAgentsKeyDetailRecord.

NameTypeReqDescription
account_idstringyesAccount ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
key_idstringyesKey ID of the object, e.g., '00110011-0000-0000-0000-000000000000'

No output schema declared.

No examples provided.

msp_get-detection-rule-by-account ~109

Get a detection rule by ID for your MSP sub-account. Required: account_id, rule_id. Returns the ResponseDetectionRuleDetail.

NameTypeReqDescription
account_idstringyesAccount ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
rule_idstringyesDetection rule ID, e.g., '00110011-0000-0000-0000-000000000000'

No output schema declared.

No examples provided.

msp_get-detection-rules-by-account ~194

List detection rules for your MSP sub-account. Required: account_id. Optional: page (default: 1), page_size (default: 50), limit (default: 200) (plus 1 more). Returns array of DetectionRuleRecord.

NameTypeReqDescription
account_idstringyesAccount ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
limitnumber–Maximum number of records to return, e.g., '200'
order_bystring–Order records by field, e.g., 'created', 'created;asc', 'created;desc', 'name;desc,created;desc'
pagenumber–Page to return, e.g., '2'
page_sizenumber–Number of records per page to return, e.g., '3'

No output schema declared.

No examples provided.

msp_get-msp-detection-rule ~72

Get a basis detection rule by ID (for MSP bulk detail). Required: rule_id. Returns the ResponseDetectionRuleDetail.

NameTypeReqDescription
rule_idstringyesDetection rule ID, e.g., '00110011-0000-0000-0000-000000000000'

No output schema declared.

No examples provided.

msp_get-msp-detection-rules ~156

List basis detection rules (catalog) for MSP bulk. Optional: page (default: 1), page_size (default: 50), limit (default: 200) (plus 1 more). Returns array of DetectionRuleRecord.

NameTypeReqDescription
limitnumber–Maximum number of records to return, e.g., '200'
order_bystring–Order records by field, e.g., 'created', 'created;asc', 'created;desc', 'name;desc,created;desc'
pagenumber–Page to return, e.g., '2'
page_sizenumber–Number of records per page to return, e.g., '3'

No output schema declared.

No examples provided.

msp_list-users ~149

Get or search users for your MSP sub-account. Required: account_id. Optional: page (default: 1), page_size (default: 50), limit (default: 200). Returns array of MspListUsersItem.

NameTypeReqDescription
account_idstringyesAccount ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
limitnumber–Maximum number of records to return, e.g., '200'
pagenumber–Page to return, e.g., '2'
page_sizenumber–Number of records per page to return, e.g., '3'

No output schema declared.

No examples provided.

msp_resolve-finding ~162

Resolve a finding for your MSP sub-account. Required: account_id, finding_id, resolution. Optional: resolution_notes. Returns the new FindingDetailRecord.

NameTypeReqDescription
account_idstringyesAccount ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
finding_idstringyesFinding ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
resolutionnumberyesResolution ID (e.g., 10=Valid, 20=False Positive, 30=No Action Needed, 40=Risk Accepted)
resolution_notesstring–Optional notes related to the resolution

No output schema declared.

No examples provided.

msp_set-finding-owners ~164

Assign owners to a finding for your MSP sub-account. Required: account_id, finding_id, owner_type, owners. Returns the new FindingDetailRecord.

NameTypeReqDescription
account_idstringyesAccount ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
finding_idstringyesFinding ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
owner_typestringyesType of owners to assign. Case-sensitive, must be lowercase.
ownersstringyesArray of person IDs (UUIDs) to assign as owners. Empty array clears all owners for the specified owner_type.

No output schema declared.

No examples provided.

org_controller-direct-add-comment ~125

Add a comment to a finding in the org. Required: finding_id, body, sender. Returns the new FindingsCommentsRecord.

NameTypeReqDescription
bodystringyesComment body (required, non-empty). May contain HTML.
finding_idstringyesFinding ID of the object, e.g., '00110011-0000-0000-0000-000000000000'
senderstringyesUUID of the person creating the comment. Use GET /org/users or GET /msp/accounts/{account_id}/users to obtain user IDs.

No output schema declared.

No examples provided.

org_controller-direct-get ~64

Get a specific finding by ID. Required: finding_id. Returns the ResponseFindingsRecord.

NameTypeReqDescription
finding_idstringyesFinding ID of the object, e.g., '00110011-0000-0000-0000-000000000000'

No output schema declared.

No examples provided.

org_controller-direct-get-agents-device ~69

Get a specific agents device by ID. Required: device_id. Returns the ResponseAgentsDeviceDetailRecord.

NameTypeReqDescription
device_idstringyesDevice ID of the object, e.g., '00110011-0000-0000-0000-000000000000'

No output schema declared.

No examples provided.

org_controller-direct-get-agents-devices ~154

Get or search agents devices. Optional: page (default: 1), page_size (default: 50), limit (default: 200) (plus 1 more). Returns array of OrgControllerDirectGetAgentsDevicesItem.

NameTypeReqDescription
limitnumber–Maximum number of records to return, e.g., '200'
order_bystring–Order records by field, e.g., 'created', 'created;asc', 'created;desc', 'name;desc,created;desc'
pagenumber–Page to return, e.g., '2'
page_sizenumber–Number of records per page to return, e.g., '3'

No output schema declared.

No examples provided.

org_controller-direct-get-agents-key ~69

Get a specific agents key by ID. Required: key_id. Returns the ResponseAgentsKeyDetailRecord.

NameTypeReqDescription
key_idstringyesKey ID of the object, e.g., '00110011-0000-0000-0000-000000000000'

No output schema declared.

No examples provided.

org_controller-direct-get-agents-keys ~154

Get or search agents keys. Optional: page (default: 1), page_size (default: 50), limit (default: 200) (plus 1 more). Returns array of OrgControllerDirectGetAgentsKeysItem.

NameTypeReqDescription
limitnumber–Maximum number of records to return, e.g., '200'
order_bystring–Order records by field, e.g., 'created', 'created;asc', 'created;desc', 'name;desc,created;desc'
pagenumber–Page to return, e.g., '2'
page_sizenumber–Number of records per page to return, e.g., '3'

No output schema declared.

No examples provided.

Install

How do I install the Blumira MCP server?

Blumira MCP 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, ebbd0ae1b3c7dfffba5811bc954fe130aaadb64de833d21e8b016dd78f081ae1; the commands to do that are on this page. If it does not match, do not open it.

mcpb · blumira-mcp.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

ebbd0ae1b3c7dfffba5811bc954fe130aaadb64de833d21e8b016dd78f081ae1

macOS / Linux

echo "ebbd0ae1b3c7dfffba5811bc954fe130aaadb64de833d21e8b016dd78f081ae1  blumira-mcp.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\blumira-mcp.mcpb).Hash -eq "ebbd0ae1b3c7dfffba5811bc954fe130aaadb64de833d21e8b016dd78f081ae1"

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 Blumira MCP server?

Blumira MCP is listed in the public MCP registry as io.github.Servosity/blumira-mcp. Cross-account Blumira findings, detections, and agents in one offline-searchable store. This page covers its MCPB bundle (https://github.com/Servosity/msp-skills/releases/download/blumira-v0.1.6/blumira-mcp.mcpb).

Is the Blumira MCP server safe to use?

Blumira MCP scores 50 out of 100 on VerifyMCP. 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 tools does the Blumira MCP server expose?

Blumira MCP exposes 61 tools: analytics, audit, context, coverage, dc_roster, and 56 more. Their descriptions and schemas cost roughly 20,533 tokens of context every time the server is loaded.

What licence is the Blumira MCP server under?

Blumira MCP declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.