OnlineCyberTools MCP (280+ filterable tools)

crypto_password_generator_pin

Read-only

Generate cryptographically random numeric PINs (0-9 digits) for device or card PINs. Options to prevent repeating or sequential digits.

Instructions

Random PIN Generator. Generate one or more cryptographically random numeric PINs (digits 0-9 only). Use this for numeric-only codes such as device or card PINs; use crypto_password_generator for mixed-character passwords or crypto_password_generator_passphrase for word-based passphrases. Randomness comes from crypto.getRandomValues. Runs locally on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited (30 requests/min, 200/hour, 1000/day for anonymous callers). Returns the generated PINs with each PIN's length and the normalized options actually applied.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crypto_password_generator_pin"
  }
}

Input Schema

Name	Required	Description
`length`	No	Number of digits per PIN. Clamped to 4-20. When noRepeating is true, an effective length above 10 is rejected (only 10 unique digits exist).
`noRepeating`	No	When true, no digit repeats within a PIN; this caps the usable length at 10.
`noSequential`	No	When true, consecutive digits never differ by exactly 1 (e.g. avoids 12, 65), reducing easily-guessed runs.
`quantity`	No	How many PINs to generate. Clamped to 1-100.

Output Schema

Name	Required	Description	Default
`pins`	No	The generated PINs, one entry per requested quantity.
`options`	No	The normalized options actually used after clamping defaults.

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedv0.5.1Jun 3, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / excludeSimilar
```
Removed value: -{
-  "type": "boolean"
-}
```
removedInput schema / properties / includeLowercase
```
Removed value: -{
-  "type": "boolean"
-}
```
removedInput schema / properties / includeNumbers
```
Removed value: -{
-  "type": "boolean"
-}
```
removedInput schema / properties / includeSymbols
```
Removed value: -{
-  "type": "boolean"
-}
```
removedInput schema / properties / includeUppercase
```
Removed value: -{
-  "type": "boolean"
-}
```
addedInput schema / properties / length / default
```
Added value: +4
```

addedInput schema / properties / length / description

Added value: +"Number of digits per PIN. Clamped to 4-20. When noRepeating is true, an effective length above 10 is rejected (only 10 unique digits exist)."

addedInput schema / properties / length / maximum
```
Added value: +20
```
addedInput schema / properties / length / minimum
```
Added value: +4
```

addedInput schema / properties / noRepeating

Added value: +{
+  "default": false,
+  "description": "When true, no digit repeats within a PIN; this caps the usable length at 10.",
+  "type": "boolean"
+}

addedInput schema / properties / noSequential

Added value: +{
+  "default": false,
+  "description": "When true, consecutive digits never differ by exactly 1 (e.g. avoids 12, 65), reducing easily-guessed runs.",
+  "type": "boolean"
+}

addedInput schema / properties / quantity / default
```
Added value: +1
```

addedInput schema / properties / quantity / description

Added value: +"How many PINs to generate. Clamped to 1-100."

addedInput schema / properties / quantity / maximum
```
Added value: +100
```
addedInput schema / properties / quantity / minimum
```
Added value: +1
```

changedInput schema / required

Previous value: -[
-  "length",
-  "includeUppercase",
-  "includeLowercase",
-  "includeNumbers",
-  "includeSymbols",
-  "excludeSimilar",
-  "quantity"
-]New value: +[]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "options": {
+      "description": "The normalized options actually used after clamping defaults.",
+      "properties": {
+        "length": {
+          "description": "Effective digit length applied.",
+          "type": "integer"
+        },
+        "noRepeating": {
+          "description": "Whether repeated digits were disallowed.",
+          "type": "boolean"
+        },
+        "noSequential": {
+          "description": "Whether consecutive ±1 digits were disallowed.",
+          "type": "boolean"
+        },
+        "quantity": {
+          "description": "Number of PINs generated.",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "pins": {
+      "description": "The generated PINs, one entry per requested quantity.",
+      "items": {
+        "properties": {
+          "length": {
+            "description": "Number of digits in this PIN.",
+            "type": "integer"
+          },
+          "pin": {
+            "description": "The generated numeric PIN string (digits 0-9).",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses cryptographic randomness source (crypto.getRandomValues), local/non-destructive execution, and rate limits. No contradiction with annotations (readOnlyHint: true).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Mostly concise and front-loaded, though some redundancy (e.g., 'read-only, non-destructive' could be tighter). Still informative without being overly long.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Comprehensive given 4 parameters and output schema present. Covers purpose, use cases, behavior, and important parameter constraints.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds clamping ranges (4-20) and noRepeating length cap, providing context beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it generates numeric-only PINs and explicitly distinguishes from sibling tools crypto_password_generator and crypto_password_generator_passphrase.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when to use (numeric-only codes like device or card PINs) and when not to (mixed-character passwords or passphrases), plus mentions rate limits and local execution.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server