io.github.theoddden/stamp
PYPI · STAMP-MCP · 2 COMPONENTS · SCANNED SEP 21
Concierge MCP for agentic workflows: verified time + drift, uuid, diff, calc, attest, verify.
Available components
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 native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 12 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 9 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 454 tokens (~75/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: the tool surface changed between 0.3.1 and 0.6.1: 1 tool removals, 0 breaking changes, 5 additions. See how to fix → Fail
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
pypi · stamp-mcp
claude mcp add theoddden-stamp -- uvx stamp-mcp
{
"mcpServers": {
"theoddden-stamp": {
"command": "uvx",
"args": [
"stamp-mcp"
]
}
}
} {
"servers": {
"theoddden-stamp": {
"command": "uvx",
"args": [
"stamp-mcp"
]
}
}
} codex mcp add theoddden-stamp -- uvx stamp-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theoddden-stamp": {
"type": "local",
"command": [
"uvx",
"stamp-mcp"
],
"enabled": true
}
}
} openclaw mcp add theoddden-stamp --command uvx --arg stamp-mcp
mcp_servers:
theoddden-stamp:
command: "uvx"
args: ["stamp-mcp"] {
"McpServers": {
"theoddden-stamp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"stamp-mcp"
]
}
}
} assistant mcp add theoddden-stamp -t stdio -c uvx -a stamp-mcp
{
"mcpServers": {
"theoddden-stamp": {
"command": "uvx",
"args": [
"stamp-mcp"
]
}
}
} 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.
- 17 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Sept 26 −5
- Source repository: pass → fail ▼ security
- Security disclosure: fail → unverified ▼ functional
- 12 Sept 26 −3
- Stability: 0.17 → fail ▼ security
- Package version: 0.5.8 → 0.6.1 functional
- 11 Sept 26 +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.
- 10 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.5.7 → 0.5.8 functional
- 9 Sept 26 +5
- Tool safety: pass → unverified ▼ security
- 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. security
- Schema quality: 53 → 70 ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- 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 functional
- 7 Sept 26 +15
- Malware scan: unverified → pass ▲ security
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 21 Sept 2026 · Analysed pypi/stamp-mcp@0.6.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
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 12 packages
| Packages resolved | 12 |
|---|---|
| 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 →
attest ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| payload | – | yes | Any JSON value to attest |
| server | string | – | NTP server for the verified timestamp |
No output schema declared.
No examples provided.
calculate ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expression | string | yes | e.g. "(1500 * 0.23) + 47" |
No output schema declared.
No examples provided.
diff ~64
Unified diff between two texts, with added/removed line counts. For reviewing edits, comparing outputs, or validating transformations.
| Name | Type | Req | Description |
|---|---|---|---|
| context | integer | – | Lines of context around each change |
| text_a | string | yes | Original text |
| text_b | string | yes | Revised text |
No output schema declared.
No examples provided.
generate_uuid ~43
Generate one or more random UUIDv4 identifiers -- for records, sessions, and IDs created in agent pipelines.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many UUIDs to generate |
No output schema declared.
No examples provided.
get_time ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
verify ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attested | object | yes | The record returned by attest |
No output schema declared.
No examples provided.
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.