YADE MCP Server
PYPI · YADE-MCP · SCANNED SEP 20
MCP server for YADE — open-source DEM engine. Browse API docs, run simulations, manage tasks.
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 16 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 (MIT).Pass
- Actively maintained (last published 24 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 915 tokens (~130/item across 7 items; 7 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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "yade_execute_task" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the YADE MCP Server server?
YADE MCP Server runs locally as a PyPI package, launched with uvx yade-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · yade-mcp
claude mcp add yusong652-yade-mcp -- uvx yade-mcp
{
"mcpServers": {
"yusong652-yade-mcp": {
"command": "uvx",
"args": [
"yade-mcp"
]
}
}
} {
"servers": {
"yusong652-yade-mcp": {
"command": "uvx",
"args": [
"yade-mcp"
]
}
}
} codex mcp add yusong652-yade-mcp -- uvx yade-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yusong652-yade-mcp": {
"type": "local",
"command": [
"uvx",
"yade-mcp"
],
"enabled": true
}
}
} openclaw mcp add yusong652-yade-mcp --command uvx --arg yade-mcp
mcp_servers:
yusong652-yade-mcp:
command: "uvx"
args: ["yade-mcp"] {
"McpServers": {
"yusong652-yade-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"yade-mcp"
]
}
}
} assistant mcp add yusong652-yade-mcp -t stdio -c uvx -a yade-mcp
{
"mcpServers": {
"yusong652-yade-mcp": {
"command": "uvx",
"args": [
"yade-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 14 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed pypi/yade-mcp@0.1.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 16 packages
| Packages resolved | 16 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
yade_browse_api Yade Browse Api ~193
Browse YADE Python API documentation hierarchically. Navigate category → class → details, like a filesystem: - Empty path: list categories (ls /) - Category: list classes (ls /engines) - Category.Class: full documentation (cat /engines/NewtonIntegrator)
| Name | Type | Req | Description |
|---|---|---|---|
| path | – | – | Dot-separated API path to browse. Progressive disclosure: - None or '': Root — list all categories - 'engines': List all engine classes - 'engines.NewtonIntegrator': Full docs for NewtonIntegrator -… |
Structured output declared, but exposes no named fields.
No examples provided.
yade_check_task_status Yade Check Task Status ~90
Check status and output for a submitted YADE task.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | – | – | Only keep output lines containing this text |
| limit | integer | – | Output lines per page |
| skip_newest | integer | – | Skip N newest output lines before pagination |
| task_id | string | yes | Task ID returned by yade_execute_task |
| wait_seconds | number | – | Wait time before querying status |
Structured output declared, but exposes no named fields.
No examples provided.
yade_execute_code Yade Execute Code ~191
Execute Python code synchronously in the running YADE process. Returns stdout immediately. Code runs in the YADE Python environment where yade modules are already imported; side effects persist. Typical uses: - Query simulation state: O.bodies count, current iteration - Create/modify bodies, engines, interactions - Read or set material properties - Development and REPL-style testing Unlike yade_execute_task, this tool is fire-and-return: the response contains the full output. It is NOT tracked by yade_list_tasks and cannot be interrupted or polled. WARNING: Avoid long-running calls (O.run with many iterations, heavy loops). They block until completion or timeout and cannot be cancelled. Use yade_execute_task for long simulations.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Python code to execute in YADE process |
| timeout | integer | – | Console execution timeout in seconds |
Structured output declared, but exposes no named fields.
No examples provided.
yade_execute_task Yade Execute Task ~146
Submit a Python script for asynchronous execution in YADE. Returns a task_id immediately; the script runs in the background. Use the companion tools to manage the task lifecycle: - yade_check_task_status: poll output, progress, and final status - yade_interrupt_task: cancel a running task - yade_list_tasks: browse task history Use this for production simulation runs, long O.run() cycles, and any operation that may take minutes or longer. For quick queries and REPL-style testing, use yade_execute_code.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Brief task purpose |
| entry_script | string | yes | Absolute path to entry Python script for YADE |
Structured output declared, but exposes no named fields.
No examples provided.
yade_interrupt_task Yade Interrupt Task ~36
Request graceful interruption of a running YADE task.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | Task ID returned by yade_execute_task |
Structured output declared, but exposes no named fields.
No examples provided.
yade_list_tasks Yade List Tasks ~45
List tracked YADE tasks with pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max tasks to return |
| skip_newest | integer | – | Skip N most recent tasks before listing |
Structured output declared, but exposes no named fields.
No examples provided.
yade_query_api Yade Query Api ~163
Search YADE API documentation by keywords (like grep). Returns matching class/function names with descriptions ranked by relevance. Use yade_browse_api for full documentation of a specific class. When to use: - You have keywords but don't know the exact class name - Examples: "friction material", "gravity engine", "contact force", "triaxial stress", "sphere create", "hertz mindlin" Related tools: - yade_browse_api: Get full documentation for a known class path
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results (1-20). |
| query | string | yes | Search keywords for YADE Python API. Examples: 'sphere body', 'triaxial compression', 'contact force'. Case-insensitive. |
Structured output declared, but exposes no named fields.
No examples provided.
What is the YADE MCP Server server?
YADE MCP Server is listed in the public MCP registry as io.github.yusong652/yade-mcp. MCP server for YADE, open-source DEM engine. Browse API docs, run simulations, manage tasks. This page covers its PyPI package (yade-mcp).
Is the YADE MCP Server server safe to use?
YADE MCP Server scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 YADE MCP Server server expose?
YADE MCP Server exposes 7 tools: yade_browse_api, yade_query_api, yade_execute_task, yade_check_task_status, yade_list_tasks, and 2 more. Their descriptions and schemas cost roughly 864 tokens of context every time the server is loaded.
Is the YADE MCP Server server still maintained?
YADE MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the YADE MCP Server server under?
YADE MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.