PFC - ITASCA Discrete Element Simulation
PYPI · PFC-MCP · SCANNED SEP 20
Give AI agents full access to ITASCA PFC - documentation, simulation, and plot capture.
Available components
Deprecated
This server is marked deprecated in the MCP registry.
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 Security50
- Malware scan not yet available for this package.Unverified
- 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 & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- 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 84 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 run of this package 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 →
How do I install the PFC - ITASCA Discrete Element Simulation MCP server?
PFC - ITASCA Discrete Element Simulation runs locally as a PyPI package, launched with uvx pfc-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 · pfc-mcp
claude mcp add yusong652-pfc -- uvx pfc-mcp
{
"mcpServers": {
"yusong652-pfc": {
"command": "uvx",
"args": [
"pfc-mcp"
]
}
}
} {
"servers": {
"yusong652-pfc": {
"command": "uvx",
"args": [
"pfc-mcp"
]
}
}
} codex mcp add yusong652-pfc -- uvx pfc-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yusong652-pfc": {
"type": "local",
"command": [
"uvx",
"pfc-mcp"
],
"enabled": true
}
}
} openclaw mcp add yusong652-pfc --command uvx --arg pfc-mcp
mcp_servers:
yusong652-pfc:
command: "uvx"
args: ["pfc-mcp"] {
"McpServers": {
"yusong652-pfc": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"pfc-mcp"
]
}
}
} assistant mcp add yusong652-pfc -t stdio -c uvx -a pfc-mcp
{
"mcpServers": {
"yusong652-pfc": {
"command": "uvx",
"args": [
"pfc-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.
- 9 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 8 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- 4 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Sept 26 −24
- Stability: 0.87 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- 31 Aug 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 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 20 Sept 2026 · Analysed pypi/pfc-mcp@0.2.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 →
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.
What is the PFC - ITASCA Discrete Element Simulation MCP server?
PFC - ITASCA Discrete Element Simulation is an MCP server listed in the public MCP registry as io.github.yusong652/pfc. Give AI agents full access to ITASCA PFC - documentation, simulation, and plot capture. This page covers its PyPI package (pfc-mcp).
Is the PFC - ITASCA Discrete Element Simulation MCP server safe to use?
PFC - ITASCA Discrete Element Simulation scores 19 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.
Is the PFC - ITASCA Discrete Element Simulation MCP server still maintained?
PFC - ITASCA Discrete Element Simulation is marked deprecated 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 PFC - ITASCA Discrete Element Simulation MCP server under?
PFC - ITASCA Discrete Element Simulation declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.