io.github.rog0x/crypto
NPM · @ROG0X/MCP-CRYPTO-TOOLS
Hash, encode, UUID, password analysis for AI agents
Available components
Last scanned (9 hours ago)
Scores higher than 75% of npm servers
Category Security
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
- 30 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 228 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 673 tokens (~134/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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −2
- Stability: pass → 0.90 functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.93 functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.83 → pass security
- 15 Oct 26 −3
- Stability: pass → 0.80 functional
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 6 Nov 2026 · Analysed npm/@rog0x/mcp-crypto-tools@1.0.2
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 | 30 |
| 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 →
encode_decode ~67
Encode or decode text using Base64, URL encoding, HTML entities, hex, or binary. Can also auto-detect the encoding format of input.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Encoding/decoding action to perform |
| text | string | yes | Text to encode, decode, or detect |
No output schema declared.
No examples provided.
generate_id ~134
Generate unique identifiers: UUID v4, nanoid, ULID, CUID, or random strings with configurable length and charset.
| Name | Type | Req | Description |
|---|---|---|---|
| charset | string | – | Charset for random strings: alphanumeric, alpha, numeric, hex, lowercase, uppercase, symbols, all, or a custom string of characters. Default: alphanumeric |
| count | number | – | Number of IDs to generate (max 100). Default: 1 |
| length | number | – | Length for nanoid or random string. Default: 21 for nanoid, 16 for random |
| type | string | yes | Type of ID to generate |
No output schema declared.
No examples provided.
hash ~175
Hash text using MD5, SHA-1, SHA-256, SHA-512, or HMAC. Can also compare two hash values or compute all hash algorithms at once.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform: hash (single algorithm), hmac (keyed hash), compare (compare two hashes), hash_all (all algorithms at once) |
| algorithm | string | – | Hash algorithm (for hash and hmac actions). Default: sha256 |
| encoding | string | – | Output encoding. Default: hex |
| hash1 | string | – | First hash (for compare action) |
| hash2 | string | – | Second hash (for compare action) |
| key | string | – | Secret key (for hmac action) |
| text | string | – | Text to hash (for hash, hmac, hash_all actions) |
No output schema declared.
No examples provided.
jwt ~116
Decode JWT tokens to inspect header and payload, check expiry status, or create unsigned JWTs for testing purposes. Not for production authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action: decode (full decode), check_expiry (just expiry info), create_unsigned (create test token) |
| expires_in_seconds | number | – | Expiration time in seconds from now (for create_unsigned) |
| payload | object | – | Payload object for creating unsigned JWT (for create_unsigned) |
| token | string | – | JWT token string (for decode and check_expiry) |
No output schema declared.
No examples provided.
password ~181
Generate secure passwords with configurable options, or check password strength with entropy calculation and crack time estimation.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action: generate a password or check strength of an existing one |
| count | number | – | Number of passwords to generate (max 100). Default: 1 |
| digits | boolean | – | Include digits. Default: true |
| exclude_ambiguous | boolean | – | Exclude ambiguous characters (0, O, l, I, 1). Default: false |
| length | number | – | Password length (for generate). Default: 16 |
| lowercase | boolean | – | Include lowercase letters. Default: true |
| password | string | – | Password to check (for check_strength action) |
| symbols | boolean | – | Include symbols. Default: true |
| uppercase | boolean | – | Include uppercase letters. Default: true |
No output schema declared.
No examples provided.
How do I install the io.github.rog0x/crypto MCP server?
io.github.rog0x/crypto runs locally as an npm package, launched with npx -y @rog0x/mcp-crypto-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-crypto-tools
claude mcp add rog0x-crypto -- npx -y @rog0x/mcp-crypto-tools
What is the io.github.rog0x/crypto MCP server?
io.github.rog0x/crypto is an MCP server listed in the public MCP registry as io.github.rog0x/crypto. Hash, encode, UUID, password analysis for AI agents. This page covers its npm package (@rog0x/mcp-crypto-tools).
Is the io.github.rog0x/crypto MCP server safe to use?
io.github.rog0x/crypto scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 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.rog0x/crypto MCP server expose?
io.github.rog0x/crypto exposes 5 tools: hash, encode_decode, generate_id, password, jwt. Their descriptions and schemas cost roughly 673 tokens of context every time the server is loaded.
Is the io.github.rog0x/crypto MCP server still maintained?
io.github.rog0x/crypto is still listed as active in the MCP registry. We last reached this channel on 6 November 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.rog0x/crypto MCP server under?
io.github.rog0x/crypto declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.rog0x/crypto MCP server?
VerifyMCP ran 16 checks on io.github.rog0x/crypto, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.