Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

security_openssl_command_builder

Read-onlyIdempotent

Generate ready-to-use OpenSSL commands for key generation, CSR creation, self-signed certificates, encryption, hashing, and more without executing anything.

Instructions

OpenSSL Command Builder. Build a copy-paste-ready openssl command line from structured form fields, covering 12 operations: keygen (RSA/EC/Ed25519/Ed448 private key via genpkey), csr (PKCS#10 certificate signing request), self-signed (key plus self-signed X.509 cert in one step), sign (detached dgst -sign signature), encrypt (symmetric enc encrypt/decrypt), hash (file digest), pkcs12 (bundle key+cert into a .p12/.pfx), inspect (x509/req/pkey/pkcs12 -text), connect (s_client TLS probe), random (rand bytes), verify (chain verification), and s-server (local TLS test server). This tool only GENERATES the command text with per-flag explanations, weak/deprecated-choice warnings, and the files each command reads or writes - it NEVER executes openssl, opens sockets, or touches the filesystem. For Linux CLI commands (find/grep/sed/rsync/tar/curl/ssh) use linux_command_builder; for Apache rewrite/redirect rules use security_htaccess_generator. Runs locally on the options you provide: read-only, non-destructive, contact

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoAPI action: build assembles a command from category+fields; categories returns the form-field catalogue; presets returns curated example field sets. Defaults to build.build
categoryNoWhich openssl command to build (required when operation is build). keygen=private key, csr=signing request, self-signed=key+cert, sign=detached signature, encrypt=symmetric enc, hash=file digest, pkcs12=PFX bundle, inspect=read cert/key/CSR, connect=s_client probe, random=rand bytes, verify=chain check, s-server=test TLS server.
fieldsNoPer-category options; every key is optional and falls back to a sensible default. keygen/self-signed: algorithm (rsa-2048/rsa-3072/rsa-4096/ec/ed25519/ed448, default rsa-4096), curve (prime256v1/secp384r1/secp521r1/secp256k1), encryptKey/noEncrypt, cipher, outFile/keyOut/certOut, days (default 365). csr/self-signed subject DN: country, state, locality, organization, organizationalUnit, commonName, emailAddress; sans. csr/self-signed/sign/hash: digest (sha256/sha384/sha512/sha1/md5, default sha256), keyFile, inFile, sigFile. encrypt: mode (encrypt/decrypt), base64, pbkdf2 (default true), iter (default 100000), password. pkcs12: certFile, caFile, alias, password. inspect: what (cert/csr/key/p12), inFile. connect/s-server: host, sni, starttls, tlsVersion, ciphers, port (default 443 connect / 4433 s-server), showCerts/www. random: length (default 32), format (base64/hex), outFile.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the request succeeded.
operationNoThe operation echoed back (build, categories, or presets).
resultNoOperation payload. For build this is the command object below; for categories/presets it wraps a categories/presets array of form definitions.
Behavior5/5

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

Annotations already mark readOnlyHint=true and destructiveHint=false; description reinforces non-execution, no filesystem access, and local read-only operation. It adds context about warnings and explanations, consistent with annotations. No contradiction.

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

Conciseness5/5

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

The description is front-loaded with the purpose and key exclusions. Uses bullet-style lists for operations and guidelines, making it scannable. Every sentence adds value—no filler, no repetition of schema info.

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 (12 operations, nested fields, multiple parameter schemas), the description covers all behavioral aspects: generation vs. execution, file side-effects, parameter defaults, and alternative tools. No gaps remain even without output schema in the input.

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?

Schema coverage is 100% and description enriches each parameter with defaults, examples (e.g., algorithm defaults to rsa-4096, digest to sha256), and per-category field lists. The description adds significant meaning beyond the enum names and property types.

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 builds copy-paste-ready openssl commands from form fields, lists 12 operations, and contrasts with sibling tools like linux_command_builder and security_htaccess_generator. The verb 'build' plus 'openssl command line' is specific and unambiguous.

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?

Explicitly states when to use (build openssl commands) and when not to (never executes, opens sockets, or touches filesystem). Provides alternative tools for Linux CLI commands and Apache rules, guiding the agent away from misuse.

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