# io.github.theoddden/stamp (pypi · stamp-mcp)

Concierge MCP for agentic workflows: verified time + drift, uuid, diff, calc, attest, verify.

- Trust score: 51/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `stamp-mcp.terradev.cloud`: 65/100, [markdown](https://verifymcp.io/servers/theoddden-stamp/stamp-mcp-2.md), [page](https://verifymcp.io/servers/theoddden-stamp/stamp-mcp-2)
- pypi · `stamp-mcp`: 51/100 (this document), [markdown](https://verifymcp.io/servers/theoddden-stamp/stamp-mcp.md), [page](https://verifymcp.io/servers/theoddden-stamp/stamp-mcp)

## Channel facts

- Registry: `pypi`
- Package: `stamp-mcp`
- Version: `0.6.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-09-21.

- **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 native-build step with no shell scripting around it.
  - 0 of 12 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 9 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 454 tokens (~75/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: the tool surface changed between 0.3.1 and 0.6.1: 1 tool removals, 0 breaking changes, 5 additions.
- **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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.theoddden/stamp MCP server?

io.github.theoddden/stamp runs locally as a PyPI package, launched with uvx stamp-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 theoddden-stamp -- uvx stamp-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "theoddden-stamp": {
      "command": "uvx",
      "args": [
        "stamp-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theoddden-stamp": {
      "command": "uvx",
      "args": [
        "stamp-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add theoddden-stamp -- uvx stamp-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add theoddden-stamp --command uvx --arg stamp-mcp
```

### Hermes

```yaml
mcp_servers:
  theoddden-stamp:
    command: "uvx"
    args: ["stamp-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "theoddden-stamp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "stamp-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add theoddden-stamp -t stdio -c uvx -a stamp-mcp
```

### Other

```json
{
  "mcpServers": {
    "theoddden-stamp": {
      "command": "uvx",
      "args": [
        "stamp-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-09-17 (score 51, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-15 (score 66, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-13 (score 51, −5)

- [security regression] Source repository: pass → fail
- [functional regression] Security disclosure: fail → unverified

### 2026-09-12 (score 56, −3)

- [security regression] Stability: 0.17 → fail
- [functional] Package version: 0.5.8 → 0.6.1

### 2026-09-11 (score 59, +1)

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

### 2026-09-10 (score 58, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.5.7 → 0.5.8

### 2026-09-09 (score 73, +5)

- [security regression] Tool safety: pass → unverified
- [security regression] Malware scan: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Schema quality: 53 → 70
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional improvement] MCP protocol: fail → pass
- [functional] First check of Schema quality: unverified
- [functional] Dependency health: pass → 1.00
- [functional] Licence: MIT → Apache-2.0
- [functional] Package version: 0.3.1 → 0.5.7
- [functional] Package version: 0.3.1 → 0.5.5
- [functional] Package version: 0.3.1 → 0.5.2
- [functional] Package version: 0.3.1 → 0.5.1

### 2026-09-07 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

## MCP tools (6)

### `get_time` (~108 tokens)

Query an NTP server for current UTC time and this clock's offset. Appends the sample to the drift log and returns the trend inline: current offset, drift rate (ms/day), and whether the clock is stable, drifting, or accelerating.

Input parameters:

- `server` (string): NTP server to query
- `timezone` (string): IANA timezone for a 'local' field, e.g. America/New_York. Optional -- the HTTP transport also takes ?tz= in the URL.

### `generate_uuid` (~43 tokens)

Generate one or more random UUIDv4 identifiers -- for records, sessions, and IDs created in agent pipelines.

Input parameters:

- `count` (integer): How many UUIDs to generate

### `diff` (~64 tokens)

Unified diff between two texts, with added/removed line counts. For reviewing edits, comparing outputs, or validating transformations.

Input parameters:

- `context` (integer): Lines of context around each change
- `text_a` (string, required): Original text
- `text_b` (string, required): Revised text

### `calculate` (~93 tokens)

Evaluate a math expression safely: + - * / // % **, parentheses, functions (abs round min max sqrt floor ceil exp log log2 log10 pow sin cos tan), constants pi e tau inf. Parsed to an AST and only whitelisted nodes are computed -- no eval(), no names, no arbitrary code.

Input parameters:

- `expression` (string, required): e.g. "(1500 * 0.23) + 47"

### `attest` (~88 tokens)

Wrap any payload in a tamper-evident record: a UUID, a timestamp (NTP-verified when reachable, local clock otherwise -- the record says which), and a sha256 over the canonical record. One call, the record is complete and tamper-evident.

Input parameters:

- `payload` (required): Any JSON value to attest
- `server` (string): NTP server for the verified timestamp

### `verify` (~58 tokens)

Check a record produced by attest: recompute the sha256 over the record and compare. Pass/fail -- did this payload produce this hash at this timestamp. Any modified field breaks it.

Input parameters:

- `attested` (object, required): The record returned by attest

## Diagnostics

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

## Score history

- 2026-09-21: 51
- 2026-09-20: 51
- 2026-09-19: 51
- 2026-09-18: 51
- 2026-09-17: 51
- 2026-09-16: 66
- 2026-09-15: 66
- 2026-09-14: 51
- 2026-09-13: 51
- 2026-09-12: 56
- 2026-09-11: 59
- 2026-09-10: 58
- 2026-09-09: 73
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 53

## Common questions

### What is the io.github.theoddden/stamp MCP server?

io.github.theoddden/stamp is an MCP server listed in the public MCP registry as io.github.theoddden/stamp. Concierge MCP for agentic workflows: verified time + drift, uuid, diff, calc, attest, verify. This page covers its PyPI package (stamp-mcp).

### Is the io.github.theoddden/stamp MCP server safe to use?

io.github.theoddden/stamp scores 51 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 io.github.theoddden/stamp MCP server expose?

io.github.theoddden/stamp exposes 6 tools: get_time, generate_uuid, diff, calculate, attest, verify. Their descriptions and schemas cost roughly 454 tokens of context every time the server is loaded.

### Is the io.github.theoddden/stamp MCP server still maintained?

io.github.theoddden/stamp is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.theoddden/stamp MCP server under?

io.github.theoddden/stamp declares the Apache-2.0 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/stamp-mcp/
- Socket report: https://socket.dev/pypi/package/stamp-mcp
- Changelog RSS feed: https://verifymcp.io/servers/theoddden-stamp/stamp-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/theoddden-stamp/stamp-mcp.json
- HTML version of this page: https://verifymcp.io/servers/theoddden-stamp/stamp-mcp