Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

security_api_key_generator

Read-only

Generate cryptographically random API keys, bearer tokens, and signing secrets in nine formats with optional prefixes, separators, bulk generation, and built-in presets (Stripe, GitHub, OpenAI, Slack, etc.).

Instructions

Generate Random API Keys, Bearer Tokens and Signing Secrets. Generate cryptographically-random API keys, bearer tokens and signing secrets in nine formats (hex, base64, base64url, alphanumeric, alphanumeric-upper, alphanumeric-lower, urlsafe, uuid-v4, bearer) with an optional prefix and separator, plus a bulk mode and a set of issuer-shaped presets (Stripe, GitHub PAT, OpenAI, Slack, AWS, webhook secret). Randomness comes only from a CSPRNG (browser or Node WebCrypto), never Math.random. Use crypto_password_generator instead for human-typeable passwords, passphrases or PINs; use this tool for machine-to-machine secrets. Read-only, non-destructive, stores nothing, contacts no external service, and is rate-limited (20 requests/minute for anonymous callers). Each call returns fresh random keys, so results are never reproducible across calls. Returns the formatted key plus its alphabet, byte count and estimated bits of entropy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesAction to run: generate yields one key; generateMany yields up to count keys; presets lists the curated issuer-shaped presets (needs no other field).
formatNoRequired for generate and generateMany. Output encoding or shape. bearer is a fixed 256-bit base64url token; uuid-v4 is a 36-char RFC 4122 UUID; both ignore length and byteCount.
lengthNoCharacter count for character-based formats (hex, alphanumeric variants, urlsafe). Ignored by uuid-v4 and bearer.
byteCountNoRaw random-byte count for byte-based formats (base64, base64url). Takes precedence over length when both are given.
prefixNoOptional literal text prepended to the key body (for example sk_live_).
separatorNoOptional literal text inserted between prefix and body (only used when both prefix and body are non-empty).
countNoHow many keys to produce for generateMany (each is independently random). Ignored by generate and presets.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoAlways true on a 200 response.
operationNoThe operation that was run.
resultNoFor generate, a single key object (key, alphabet, byteCount, bitsOfEntropy, format, prefix, separator); for generateMany, an array of such objects; for presets, an object with a presets array.
Behavior5/5

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

Beyond annotations, the description discloses significant behavioral details: it is read-only, non-destructive, stores nothing, contacts no external service, uses only CSPRNG, is rate-limited, and each call returns fresh keys. This fully informs the agent of its behavior.

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?

The description is a single paragraph but efficiently packs key information. It is front-loaded with purpose, then details, guidelines, and behavioral notes. Slightly long but no unnecessary content; could be slightly more concise.

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?

Given the tool's complexity (7 parameters, multiple operations, presets) and the existence of output schema, the description covers all critical aspects: operations, formats, randomness source, rate limits, storage guarantees, and sibling differentiation. It is complete for an agent to select and invoke correctly.

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

Parameters5/5

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

While the input schema has 100% coverage with descriptions, the description adds crucial context: explains the purpose of each operation (generate, generateMany, presets), details that bearer and uuid-v4 ignore length/byteCount, and clarifies the randomness source. This enriches understanding beyond the 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 the tool generates random API keys, bearer tokens, and signing secrets, with specific verb and resource. It lists nine formats and presets, and explicitly distinguishes from crypto_password_generator, making it easy to differentiate from sibling tools.

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?

The description explicitly states when to use this tool (machine-to-machine secrets) and when to use alternatives (crypto_password_generator for human-typeable passwords). It also mentions bulk mode and presets, and notes rate limits, providing clear usage guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server