# io.github.theoddden/stamp (remote · stamp-mcp.terradev.cloud)

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

- Trust score: 65/100 (medium)
- 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 (this document), [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, [markdown](https://verifymcp.io/servers/theoddden-stamp/stamp-mcp.md), [page](https://verifymcp.io/servers/theoddden-stamp/stamp-mcp)

## Channel facts

- Endpoint: `https://stamp-mcp.terradev.cloud/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.6.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **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: schema churn in the 14 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 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 is a hosted endpoint at https://stamp-mcp.terradev.cloud/mcp, so there is nothing to install locally. 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 --transport http theoddden-stamp 'https://stamp-mcp.terradev.cloud/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theoddden-stamp": {
      "url": "https://stamp-mcp.terradev.cloud/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theoddden-stamp": {
      "type": "http",
      "url": "https://stamp-mcp.terradev.cloud/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theoddden-stamp]
url = "https://stamp-mcp.terradev.cloud/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theoddden-stamp": {
      "type": "remote",
      "url": "https://stamp-mcp.terradev.cloud/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theoddden-stamp --url 'https://stamp-mcp.terradev.cloud/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theoddden-stamp:
    url: "https://stamp-mcp.terradev.cloud/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theoddden-stamp": {
      "Transport": "http",
      "Url": "https://stamp-mcp.terradev.cloud/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theoddden-stamp -t streamable-http -u 'https://stamp-mcp.terradev.cloud/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theoddden-stamp": {
      "type": "http",
      "url": "https://stamp-mcp.terradev.cloud/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-12 (score 65, −1)

- [security regression] Stability: 0.07 → fail
- [security regression] Tool “get_drift” was removed
- [security] Tool “get_time” rewrote its description, which is the text the model reads
- [functional] Server version: 0.5.3 → 0.6.1

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

- [functional] Server version: 0.5.1 → 0.5.3
- [functional] Server version: 0.5.0 → 0.5.1

### 2026-09-08 (score 65, 0)

- [functional regression] Schema quality: 145 → 491
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.3.1 → 0.5.0
- [functional] New tool “generate_uuid”
- [functional] New tool “verify”
- [functional] New tool “attest”
- [functional] New tool “calculate”
- [functional] New tool “diff”

### 2026-09-07 (score 65)

First indexed and scored.

## 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: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theoddden-stamp/stamp-mcp-2#diagnostics

## Score history

- 2026-09-21: 65
- 2026-09-20: 65
- 2026-09-19: 65
- 2026-09-18: 65
- 2026-09-17: 65
- 2026-09-16: 65
- 2026-09-15: 65
- 2026-09-14: 65
- 2026-09-13: 65
- 2026-09-12: 65
- 2026-09-09: 66
- 2026-09-08: 65
- 2026-09-07: 65

## 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 hosted endpoint (https://stamp-mcp.terradev.cloud/mcp).

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

io.github.theoddden/stamp scores 65 out of 100 on VerifyMCP. 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.

### Does the io.github.theoddden/stamp MCP server require authentication?

No. We connected to io.github.theoddden/stamp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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

## Links

- Remote endpoint: https://stamp-mcp.terradev.cloud/mcp
- Changelog RSS feed: https://verifymcp.io/servers/theoddden-stamp/stamp-mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/theoddden-stamp/stamp-mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/theoddden-stamp/stamp-mcp-2