# io.github.rcgiri-physics/physverify (pypi · physverify)

Runs physverify checks on physics code. It runs the code it checks: use on trusted code only.

- Trust score: 82/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `physverify`: 82/100 (this document), [markdown](https://verifymcp.io/servers/rcgiri-physics-physverify/physverify.md), [page](https://verifymcp.io/servers/rcgiri-physics-physverify/physverify)

## Channel facts

- Registry: `pypi`
- Package: `physverify`
- Version: `0.5.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 0 of 1 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to rcgiri-physics/physverify).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 163 tokens (~163/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## Install

### 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.

### Claude

```bash
claude mcp add rcgiri-physics-physverify -- uvx physverify
```

### Cursor

```json
{
  "mcpServers": {
    "rcgiri-physics-physverify": {
      "command": "uvx",
      "args": [
        "physverify"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "rcgiri-physics-physverify": {
      "command": "uvx",
      "args": [
        "physverify"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add rcgiri-physics-physverify -- uvx physverify
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rcgiri-physics-physverify": {
      "type": "local",
      "command": [
        "uvx",
        "physverify"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add rcgiri-physics-physverify --command uvx --arg physverify
```

### Hermes

```yaml
mcp_servers:
  rcgiri-physics-physverify:
    command: "uvx"
    args: ["physverify"]
```

### Netclaw

```json
{
  "McpServers": {
    "rcgiri-physics-physverify": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "physverify"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add rcgiri-physics-physverify -t stdio -c uvx -a physverify
```

### Other

```json
{
  "mcpServers": {
    "rcgiri-physics-physverify": {
      "command": "uvx",
      "args": [
        "physverify"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-04 (score 67, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-31 (score 82, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-30 (score 67, −14)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Security disclosure: unverified → pass

### 2026-10-29 (score 81, +14)

- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: pass → unverified

### 2026-10-28 (score 67, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-26 (score 82, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-25 (score 67)

First indexed and scored.

## MCP tools (1)

### `run_checks` (~123 tokens)

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.

Input parameters:

- `project` (string): project folder to search for verify_*.py
- `specs` (array): spec file paths

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/rcgiri-physics-physverify/physverify#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 67
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 67
- 2026-10-29: 81
- 2026-10-28: 67
- 2026-10-27: 82
- 2026-10-26: 82
- 2026-10-25: 67

## Common questions

### 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 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 5 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.

## Links

- PyPI project: https://pypi.org/project/physverify/
- Socket report: https://socket.dev/pypi/package/physverify
- Repository: https://github.com/rcgiri-physics/physverify
- Changelog RSS feed: https://verifymcp.io/servers/rcgiri-physics-physverify/physverify.xml
- Changelog JSON feed: https://verifymcp.io/servers/rcgiri-physics-physverify/physverify.json
- HTML version of this page: https://verifymcp.io/servers/rcgiri-physics-physverify/physverify