io.github.EverMint-app/evermint-mcp
NPM · EVERMINT-MCP · SCANNED SEP 29
Mint tamper-evident receipts for AI agent actions. The notary layer for agent-to-agent transactions.
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 145 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 615 tokens (~123/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.EverMint-app/evermint-mcp server?
io.github.EverMint-app/evermint-mcp runs locally as an npm package, launched with npx -y evermint-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · evermint-mcp
claude mcp add evermint-app-evermint-mcp -- npx -y evermint-mcp
{
"mcpServers": {
"evermint-app-evermint-mcp": {
"command": "npx",
"args": [
"-y",
"evermint-mcp"
]
}
}
} {
"servers": {
"evermint-app-evermint-mcp": {
"command": "npx",
"args": [
"-y",
"evermint-mcp"
]
}
}
} codex mcp add evermint-app-evermint-mcp -- npx -y evermint-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"evermint-app-evermint-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"evermint-mcp"
],
"enabled": true
}
}
} openclaw mcp add evermint-app-evermint-mcp --command npx --arg -y --arg evermint-mcp
mcp_servers:
evermint-app-evermint-mcp:
command: "npx"
args: ["-y", "evermint-mcp"] {
"McpServers": {
"evermint-app-evermint-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"evermint-mcp"
]
}
}
} assistant mcp add evermint-app-evermint-mcp -t stdio -c npx -a -y evermint-mcp
{
"mcpServers": {
"evermint-app-evermint-mcp": {
"command": "npx",
"args": [
"-y",
"evermint-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.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −2
- Stability: pass → 0.80 functional
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 29 Sept 2026 · Analysed npm/evermint-mcp@1.1.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| 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 →
evermint_get_record ~86
Fetch the full contents of a single EverMint record by Record ID, including the original payload that was minted. Requires authentication and the record must belong to the authenticated org. Use this when an agent needs to retrieve the actual content of a prior decision or action it recorded.
| Name | Type | Req | Description |
|---|---|---|---|
| record_id | string | yes | The EverMint Record ID to fetch (format: EVR-XXXXXXXX) |
No output schema declared.
No examples provided.
evermint_list_records ~159
List EverMint records belonging to the authenticated account. Supports filtering by agent_id, action_type, and date range. Returns record IDs, action types, timestamps, and agent IDs, not full payloads. Use this when an agent needs to audit its own past actions or build context from prior decisions.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | – | Filter to a specific action type |
| agent_id | string | – | Filter to records minted by a specific agent |
| limit | number | – | Max records to return (1-200, default 50) |
| since | string | – | ISO 8601: only return records on or after this time |
| until | string | – | ISO 8601: only return records on or before this time |
No output schema declared.
No examples provided.
evermint_mint ~160
Mint a tamper-evident, cryptographically timestamped record of an AI agent action, decision, or observation. Returns a Record ID and SHA-256 hash that can be used to prove what the agent did and when. Use this whenever an agent takes an action that may need to be audited, disputed, or verified later.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | yes | Short label for the action being recorded (e.g. transaction_approved, decision_made, data_accessed) |
| agent_id | string | – | Identifier for this agent or system |
| payload | object | – | The state, decision, or context to preserve. Any JSON object. |
| timestamp | string | – | ISO 8601 datetime or 'auto'. Defaults to auto. |
No output schema declared.
No examples provided.
evermint_verify ~66
Verify an existing EverMint record by Record ID. Confirms the record exists, has not been altered, and returns its metadata. No API key required, verification is public.
| Name | Type | Req | Description |
|---|---|---|---|
| record_id | string | yes | The EverMint Record ID to verify (format: EVR-XXXXXXXX) |
No output schema declared.
No examples provided.
evermint_verify_chain ~144
Verify the integrity of a sequence of hash-chained EverMint records. Confirms each record's hash matches its content, and that each record correctly references the prior record in the chain with no gaps or tampering. Use this to prove an entire sequence of agent decisions is intact, not just a single record. This is public, no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| length | number | – | Used with start_record_id. Max records to walk (1-100, default 10) |
| record_ids | array | – | Ordered list of Record IDs to verify as a chain, oldest first |
| start_record_id | string | – | Verify the chain starting from this record forward |
No output schema declared.
No examples provided.
What is the io.github.EverMint-app/evermint-mcp server?
io.github.EverMint-app/evermint-mcp is listed in the public MCP registry as io.github.EverMint-app/evermint-mcp. Mint tamper-evident receipts for AI agent actions. The notary layer for agent-to-agent transactions. This page covers its npm package (evermint-mcp).
Is the io.github.EverMint-app/evermint-mcp server safe to use?
io.github.EverMint-app/evermint-mcp scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 29 September 2026. It declares no install or post-install scripts. 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.EverMint-app/evermint-mcp server expose?
io.github.EverMint-app/evermint-mcp exposes 5 tools: evermint_mint, evermint_verify, evermint_list_records, evermint_get_record, evermint_verify_chain. Their descriptions and schemas cost roughly 615 tokens of context every time the server is loaded.
Is the io.github.EverMint-app/evermint-mcp server still maintained?
io.github.EverMint-app/evermint-mcp is still listed as active in the MCP registry. We last reached this channel on 29 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.EverMint-app/evermint-mcp server under?
io.github.EverMint-app/evermint-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.