io.github.rcgiri-physics/physverify
PYPI · PHYSVERIFY
Runs physverify checks on physics code. It runs the code it checks: use on trusted code only.
Available components
Last scanned (22 hours ago)
Scores higher than 63% of PyPI servers
Category Testing and QA
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 setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to rcgiri-physics/physverify). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 163 tokens (~163/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
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.
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.
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Security disclosure: unverified → pass ▲ functional
- 29 Oct 26 +14
- Malware scan: unverified → pass ▲ security
- Security disclosure: pass → unverified ▼ functional
- 28 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 25 Oct 26 67
First indexed and scored.
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 pypi/physverify@0.5.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | rcgiri-physics/physverify |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/rcgiri-physics/physverify/.github/workflows/publish.yml@refs/tags/v0.5.1 |
| Rekor log index | 3457025063 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:10ce50069880871e389fd44dae4de48940c4b7c3e9ab337281281882a80a1428 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 1 package
| Packages resolved | 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 →
run_checks ~123
Run physverify verification checks (manufactured solutions, order of convergence, invariants, limits, exactness) on physics simulation code. Takes spec files that define checks(); with no specs given, finds verify_*.py files under `project`. Returns a JSON report: per check family, label, status (PASS, EXACT, FAIL, INCONCLUSIVE, ERROR, SKIP), message, observed and expected order, step sizes and errors.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | – | project folder to search for verify_*.py |
| specs | array | – | spec file paths |
No output schema declared.
No examples provided.
How do I install the io.github.rcgiri-physics/physverify MCP server?
io.github.rcgiri-physics/physverify runs locally as a PyPI package, launched with uvx physverify. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · physverify
claude mcp add rcgiri-physics-physverify -- uvx physverify
What is the io.github.rcgiri-physics/physverify MCP server?
io.github.rcgiri-physics/physverify is an MCP server listed in the public MCP registry as io.github.rcgiri-physics/physverify. Runs physverify checks on physics code. It runs the code it checks: use on trusted code only. This page covers its PyPI package (physverify).
Is the io.github.rcgiri-physics/physverify MCP server safe to use?
io.github.rcgiri-physics/physverify scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 io.github.rcgiri-physics/physverify MCP server expose?
io.github.rcgiri-physics/physverify exposes 1 tool: run_checks. Their descriptions and schemas cost roughly 123 tokens of context every time the server is loaded.
Is the io.github.rcgiri-physics/physverify MCP server still maintained?
io.github.rcgiri-physics/physverify is still listed as active in the MCP registry. We last reached this channel on 4 November 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 io.github.rcgiri-physics/physverify MCP server under?
io.github.rcgiri-physics/physverify declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.