# verify-atom (pypi · verify-atom-mcp)

Signed proof of web observations for AI agents: Ed25519 proof packets for any URL.

- Trust score: 64/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- pypi · `verify-atom-mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/asherengos-verify-atom/verify-atom-mcp.md), [page](https://verifymcp.io/servers/asherengos-verify-atom/verify-atom-mcp)

## Channel facts

- Registry: `pypi`
- Package: `verify-atom-mcp`
- Version: `0.1.0`
- 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-10-18.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - 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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 21 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 112 tokens (~112/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the verify-atom MCP server?

verify-atom runs locally as a PyPI package, launched with uvx verify-atom-mcp. 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 asherengos-verify-atom -- uvx verify-atom-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "asherengos-verify-atom": {
      "command": "uvx",
      "args": [
        "verify-atom-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "asherengos-verify-atom": {
      "command": "uvx",
      "args": [
        "verify-atom-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add asherengos-verify-atom -- uvx verify-atom-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add asherengos-verify-atom --command uvx --arg verify-atom-mcp
```

### Hermes

```yaml
mcp_servers:
  asherengos-verify-atom:
    command: "uvx"
    args: ["verify-atom-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "asherengos-verify-atom": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "verify-atom-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add asherengos-verify-atom -t stdio -c uvx -a verify-atom-mcp
```

### Other

```json
{
  "mcpServers": {
    "asherengos-verify-atom": {
      "command": "uvx",
      "args": [
        "verify-atom-mcp"
      ]
    }
  }
}
```

## 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-10-18 (score 64, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-17 (score 79, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-16 (score 63, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-15 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 76, +17)

- [security improvement] Malware scan: unverified → pass

### 2026-10-08 (score 59, −14)

- [security regression] Malware scan: pass → unverified

### 2026-10-04 (score 73, +4)

- [functional improvement] Stability: unverified → 0.27

## MCP tools (1)

### `verify_url` (~112 tokens)

Observe a public web page and return a cryptographically signed proof packet: HTTP status, page title, body SHA-256, DNS resolution, and TLS certificate details, timestamped and Ed25519-signed. Use when you need verifiable evidence of what a webpage contained — e.g. to back a claim with proof instead of asking to be trusted. Anyone can independently verify the packet's signature against the service's published public key.

Input parameters:

- `url` (string, required): The public http(s) URL to observe and prove.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/asherengos-verify-atom/verify-atom-mcp#diagnostics

## Score history

- 2026-10-18: 64
- 2026-10-17: 79
- 2026-10-16: 63
- 2026-10-15: 78
- 2026-10-14: 77
- 2026-10-13: 77
- 2026-10-12: 76
- 2026-10-08: 59
- 2026-10-04: 73
- 2026-10-03: 69
- 2026-10-02: 69
- 2026-10-01: 69
- 2026-09-30: 69
- 2026-09-29: 69
- 2026-09-28: 69
- 2026-09-27: 69
- 2026-09-26: 54

## Common questions

### What is the verify-atom MCP server?

verify-atom is an MCP server listed in the public MCP registry as io.github.asherengos/verify-atom. Signed proof of web observations for AI agents: Ed25519 proof packets for any URL. This page covers its PyPI package (verify-atom-mcp).

### Is the verify-atom MCP server safe to use?

verify-atom scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 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 verify-atom MCP server expose?

verify-atom exposes 1 tool: verify_url. Their descriptions and schemas cost roughly 112 tokens of context every time the server is loaded.

### Is the verify-atom MCP server still maintained?

verify-atom is still listed as active in the MCP registry. We last reached this channel on 18 October 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 verify-atom MCP server under?

verify-atom 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/verify-atom-mcp/
- Socket report: https://socket.dev/pypi/package/verify-atom-mcp
- Repository: https://github.com/asherengos/verify-atom
- Changelog RSS feed: https://verifymcp.io/servers/asherengos-verify-atom/verify-atom-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/asherengos-verify-atom/verify-atom-mcp.json
- HTML version of this page: https://verifymcp.io/servers/asherengos-verify-atom/verify-atom-mcp