MATLAB MCP Server
MCPB · MATLAB-MCP-SERVER.MCPB
Connect AI coding agents to MATLAB. Run code, tests, and analysis via MCP.
Available components
Last scanned (16 hours ago)
Scores higher than 88% of MCPB servers
Category Developer Tools
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 & Transparency35
- 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
- License check failed: the license (See license at https://github.com/matlab/matlab-mcp-server/blob/main/LICENSE.md) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1002 tokens (~143/item across 7 items; 5 tools + 2 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (40% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 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.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)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.
- Known CVEs in Supply Chain Security (scores 0 for this)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).
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)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).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 3 Nov 26 0
- Package version: 0.13.1 → 0.16.0 functional
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 −1
- Stability: pass → 0.93 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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/matlab/matlab-mcp-server/releases/download/v0.16.0/matlab-mcp-server.mcpb@0.16.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 →
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 →
check_matlab_code Check MATLAB Code ~153
Perform static code analysis on a MATLAB script (`script_path`) using MATLAB's built-in Code Analyzer function in an existing MATLAB session. Returns warnings about coding style, potential errors, deprecated functions, performance issues, and best practice violations. It also includes information about where each issue occurs and how it can be fixed in MATLAB. This is a non-destructive, read-only operation that helps identify code quality issues without executing the script.
| Name | Type | Req | Description |
|---|---|---|---|
| script_path | string | yes | The full absolute path to the MATLAB script file to analyze. Must be a .m file that exists. File is not modified during analysis. Example: C:\Users\username\matlab\myFunction.m or /home/user/scripts/… |
| Name | Type | Req | Description |
|---|---|---|---|
| code_issues | null|array | yes | Detailed information about each code issue including location, severity, and fixability. |
No examples provided.
detect_matlab_toolboxes Detect MATLAB Toolboxes ~24
Returns information about installed MATLAB and toolboxes, including version numbers.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| installation_info | string | yes | MATLAB installation information including MATLAB version and installed toolboxes with their versions. |
No examples provided.
evaluate_matlab_code Evaluate MATLAB Code ~157
Evaluate a string of MATLAB code (`code`) in an existing MATLAB session. Optionally specify a project folder (`project_path`) to set as the current working folder before execution. Returns the command window output from code execution. WARNING: Do not use `restoredefaultpath` as it will remove the MCP server functions from the path and break this tool's ability to communicate with MATLAB.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The MATLAB code to evaluate. |
| project_path | string | – | (Optional) Absolute path to the project folder. When provided, MATLAB sets this as the current working folder. If omitted, code runs in MATLAB's current working folder. Example: C:\Users\username\mat… |
No output schema declared.
No examples provided.
run_matlab_file Run MATLAB File ~175
Execute a MATLAB script file (`script_path`) in an existing MATLAB session and capture its command window output. The script runs with the working folder automatically set to the script's location. The script must exist and be a valid MATLAB source file (.m) or P-code file (.p). If a MATLAB source file (.m) and a P-code file (.p) have the same name and are in the same folder, MATLAB runs the .p file. Returns the command window output or a success message if no output is generated.
| Name | Type | Req | Description |
|---|---|---|---|
| script_path | string | yes | The full absolute path to the MATLAB script file to execute. Must be an existing MATLAB source file (.m) or P-code file (.p). Example: C:\Users\username\projects\analysis.m or /home/user/matlab/simul… |
No output schema declared.
No examples provided.
run_matlab_test_file Run MATLAB test file ~114
Execute a MATLAB test script (`script_path`) using MATLAB's built-in runtests function and return comprehensive test results. Designed specifically for MATLAB unit test files that follow MATLAB's testing framework conventions.
| Name | Type | Req | Description |
|---|---|---|---|
| script_path | string | yes | The full absolute path to the MATLAB test script file. Must be a MATLAB source file (.m) or P-code file (.p) containing MATLAB unit tests. Example: C:\Users\username\tests\testMyFunction.m or /home/u… |
No output schema declared.
No examples provided.
How do I install the MATLAB MCP Server server?
MATLAB MCP Server 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, b0f5a51bb602a355f3f09164db61f11899346908f00b26c99a7577ed786bff5b; the commands to do that are on this page. If it does not match, do not open it.
mcpb · matlab-mcp-server.mcpb
Download bundleCheck 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
b0f5a51bb602a355f3f09164db61f11899346908f00b26c99a7577ed786bff5b
macOS / Linux
echo "b0f5a51bb602a355f3f09164db61f11899346908f00b26c99a7577ed786bff5b matlab-mcp-server.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\matlab-mcp-server.mcpb).Hash -eq "b0f5a51bb602a355f3f09164db61f11899346908f00b26c99a7577ed786bff5b"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the MATLAB MCP Server server?
MATLAB MCP Server is listed in the public MCP registry as io.github.matlab/matlab-mcp-server. Connect AI coding agents to MATLAB. Run code, tests, and analysis via MCP. This page covers its MCPB bundle (https://github.com/matlab/matlab-mcp-server/releases/download/v0.16.0/matlab-mcp-server.mcpb).
Is the MATLAB MCP Server server safe to use?
MATLAB MCP Server scores 54 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 MATLAB MCP Server server expose?
MATLAB MCP Server exposes 5 tools: check_matlab_code, detect_matlab_toolboxes, evaluate_matlab_code, run_matlab_file, run_matlab_test_file. Their descriptions and schemas cost roughly 623 tokens of context every time the server is loaded.
What did VerifyMCP test on the MATLAB MCP Server server?
VerifyMCP ran 12 checks on MATLAB MCP Server, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about MATLAB MCP Server: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.