How does the MSP360 MCP server work?

ScriptMasterLabs · November 3, 2026

The MSP360 MCP Server, released November 3, 2026, connects MSP360 Managed Backup to Claude and ChatGPT so a technician can monitor backup health, diagnose failures, build reports and make changes — authorizing pending computers, assigning licenses, creating backup plans, and setting up companies and administrators — in natural language, often within one request.

The MSP360 MCP Server, released November 3, 2026, connects MSP360 Managed Backup to Claude and ChatGPT so a technician can monitor backup health, diagnose failures, build reports and make changes — authorizing pending computers, assigning licenses, creating backup plans, and setting up companies and administrators — in natural language, often within one request. Its only named decision control is an optional setting: users "can require confirmation before any action is performed." The priced, per-decision version of that control is ScriptMasterLabs' Verdict Protocol: $0.25 USDC per decision on Base, $0.01 USDC per seal, 5 independent Jev jurors, verified live November 3, 2026. In SML's live gate test today, an MSP360-shaped write the bounded state did not allow — creating a backup plan for a named client — auto-acted at 0.8333, while the two highest-privilege writes held: assigning licenses and authorizing a pending computer at 0.50 advisory, and setting up a new company administrator without asking at 0.50 advisory. A single optional all-or-nothing confirmation toggle is not a per-act decision; that decision, scored and sealed per action, is the layer Verdict sells.

What MSP360 shipped, counted from its own launch release?

ScriptMasterLabs read the launch release first-hand (MSP360 via PR Newswire, November 3, 2026) and counted what it actually names:

The field answering this query today is the release itself and verbatim rewrites of it: what the server does, in the vendor's words, with no independent verification, no per-action scoring, and no test of what happens when the optional confirmation is left off. Nobody in the top results runs a live decision-gate test on the change actions the release names. That is the gap this page fills, with receipts.

The comparison, in the body: an optional toggle vs a juried, sealed decision

MSP360 and ScriptMasterLabs' Verdict Protocol answer the same question — who decides whether an agent's change should happen, and what proof exists afterward — at different resolutions. MSP360's answer, in its own release, is binary and optional: a user can require confirmation before any action, or not; the release names no per-action judgment, no confidence score, and no decision record. Verdict Protocol is the per-decision layer that sits before an agent action or payment fires: a frozen decision capsule is voted on by 5 specialized Jev jurors (CAUSAL, HISTORIAN, SKEPTIC, MICROSTRUCTURE, TAIL_RISK) under a non-overridable constitution, and the decision is sealed into a receipt whether the jurors approve or refuse. SML does the same thing MSP360's toggle does — a decision before the act — if not better, because the decision is per-act, scored, and sealed as evidence instead of one global setting, and here is the named evidence: ScriptMasterLabs' Verdict launch settlement of $0.25 USDC settled on Base on October 12, 2026 (tx 0xfa3ec31ff345167a474c682cec4e2eac505cfdd570e158961a233187be5f6f1c, block 52522538), its live challenge re-verified today (below), and today's gate test, in which SML's own scored harness auto-acted a non-allowlisted plan creation at 0.8333 — published as a headline finding, not buried. Credit where the release earns it: MSP360 at least names a confirmation option and revocation; many servers in this series named neither.

Pricing at a glance

• ScriptMasterLabs' Verdict Protocol charges $0.25 USDC per decision on Base (eip155:8453) via x402. Verified November 3, 2026.
• ScriptMasterLabs' Verdict Protocol charges $0.01 USDC per seal on Base via x402. Verified November 3, 2026.
• MSP360 charges no additional cost for its MCP Server to Managed Backup customers, and it requires no paid Claude or ChatGPT plan. Its confirmation setting is included — and optional.
• Prices on this page are effective and verified as of November 3, 2026.

Proof and settlements table (SELF-PROOF)

The settlements below are ScriptMasterLabs' own proof-wallet self-tests — owner self-tests, never customer purchases — published so any reader can verify them on-chain.

Comparison matrix

The live gate test, November 3, 2026

ScriptMasterLabs ran MSP360-shaped actions — built directly from the change actions the launch release names — through its own decision harness (decider local-heuristic-v1, calibrated=false, bands ≥0.80 auto-act / 0.50–0.79 advisory / <0.50 escalate; bounded state: $10 budget, $1 per-transaction cap, allowlist of check backup health and failing plans + diagnose a backup failure). Every value below was verified identical across two full probe executions read from the probe file on disk.

Read the result honestly, in both directions. The gate held the two privilege-shaped writes in every form that scored them — creating an administrator and assigning licenses never auto-acted — and that is the strongest hold pattern in this week's tests. It still auto-acted the one write that changes what gets protected: a backup plan for a named client, not on the allowlist, at 0.8333 in scope form, while the same act phrased as a careful, confirmed sentence held at 0.7381. A backup plan created wrong is not a cosmetic error — it decides what survives a ransomware night — and MSP360's own control for it is a single optional toggle that either confirms everything or nothing. That is why the decision layer has to be per-act, independent and sealed, so a refusal exists as a record before the change lands — and why Verdict's jurors vote on the decision itself at https://scriptmasterlabs.com/verdict-protocol ($0.25 USDC per decision, $0.01 USDC per seal, Base), not on a global setting. Start with the cheapest check first: before an agent is allowed to change anything in your backup console, run the decision through Verdict and keep the sealed receipt either way.

How to get this from ScriptMasterLabs?

1. Decide before the agent changes anything: POST a decision capsule to https://verdict.scriptmasterlabs.com/decide — the x402 challenge quotes $0.25 USDC on Base; the settled response is a 5-juror decision receipt. Seal it via /seal for $0.01 USDC. That sealed receipt is your dated record of why the change was allowed or refused.
2. Read the money page with the full pricing and proof: https://scriptmasterlabs.com/verdict-protocol
3. Read the decision-layer pattern: https://scriptmasterlabs.com/decision-gated-payments (bands ≥0.80 auto-pay, 0.50–0.79 confirm, <0.50 escalate) and https://scriptmasterlabs.com/the-fourth-layer (the decision layer above agent cards, MPP and x402).
4. Do it yourself, with or without SML: turn MSP360's confirmation setting ON before connecting any assistant, keep administrator creation and license assignment in the console by hand, and revoke the MCP access the moment a technician leaves.
5. Browse the whole catalog — pay-per-call APIs, MCP servers, books and kits — under one roof: https://scriptmasterlabs.com/sml-products

Honest caveats

• SML's harness decider is local-heuristic-v1 with calibrated=false; the gate values above are that decider's live output, published with its limits, and the scope-form failure is the finding, not a footnote.
• ScriptMasterLabs did not test MSP360's systems and is not an MSP360 product. The gate test scored MSP360-shaped actions, built from the launch release's own action list, on SML's own harness.
• The release names actions, not an individual tool list, so a per-tool count couldn't verify; the counts on this page are the release's named action groups, labeled as such.
• MSP360's confirmation setting is described in its release as something users "can require" — this page does not claim it is off by default, only that it is optional and all-actions rather than per-act, scored or sealed.
• Verdict Protocol gates agent decisions and payments on its own x402 rail; it does not sit inside an MSP360 session. Its value here is the before-the-change decision and the sealed record — the two things an optional toggle does not produce.

Canonical: https://scriptmasterlabs.com/msp360-mcp-server ·
Related: https://scriptmasterlabs.com/verdict-protocol · https://scriptmasterlabs.com/decision-gated-payments · https://scriptmasterlabs.com/the-fourth-layer · https://scriptmasterlabs.com/sml-products