Skip to content
MCPBytes

Create a secret.Keep it out of the conversation.

Let your agent create secret keys and tokens it never sees. They are saved on your computer; your agent only gets a name to pass along.

1 credit per job300 free credits to start

Available
  • API
  • MCP
MCP tool: get_random_bytes

Before

label · n · operation_idAsk for the amount your application needs

After

The bytes stay local
  • Private file or vault reference
D3Create a secretThe owner chooses storage and generation policy. A new operation ID creates a new version.

A secret your agent never sees.

Ask your agent for a new secret and it lands in your computer's own vault (Keychain, Credential Manager or Secret Service) or in a private file. Your agent only gets a reference to pass along, so the secret never appears in the chat. By default, each one mixes hardware randomness from MCPBytes with your computer's own, and a small helper you install keeps everything local. The helper is open source.

Size
1–64 bytes per operation
Generation
Hardware contribution + local OS randomness
Saved locally
Private file or native credential store
Agent receives
Reference, size and version; no secret bytes
Retry
Reuse the operation ID to recover its completed receipt
Source
Open source (AGPL-3.0); its public build is local-only

Out of the chat.

Your agent gets a reference, never the secret, and passes it to the app that needs it.

Your vault, your choice.

Keychain, Credential Manager, Secret Service or a private file.

Your rules.

Require the hardware contribution, allow a clearly marked local fallback, or stay fully offline.

Pay by the job.

1 credit per job. Local-only generation makes no API call. Failed API jobs are refunded; a completed remote contribution is charged even if local verification or saving later fails.

Pricing details

Start free

Available now

300free credits when you sign up

  • Every MCPBytes tool, one credit balance
  • Sign in with GitHub or email, no card required
  • Each tool states its price before you run it
  • Failed API jobs cost nothing

Price per job

Create a secret

Per job
1 credit

Limits

Most values per job
64
Results
Encrypted: 5 minutes · Local: owner-managed

One local tool. A saved-secret reference.

Install MCPBytes Vault and connect it as a local MCP server. The owner sets the API key, trusted public pins and storage policy; the agent supplies only these arguments.

Local MCP tool: get_random_bytes

labelOwner-approved prefix
A name for the secret, using letters, digits, underscores or hyphens.
n1–64
Number of bytes your application needs.
operation_idStable ID
Reuse after an uncertain reply. Use a new ID to create a new immutable version.

A successful response contains the reference, label, version, byte count, storage backend, stored format and generation mode. A second tool, list_secrets, lists labels and versions. Neither returns secret bytes: you reveal, delete or enroll secrets yourself with the helper’s terminal commands.

Building your own local client?

The hosted endpoint accepts a fresh recipient public key and its bound request identity. A custom local client must authenticate and decrypt the response, mix it with local OS randomness, and save it privately. Encrypted responses expire five minutes after admission and are removed by the scheduled cleanup; billing metadata remains. Never send a private key to the API or chat.

Encrypted API schema

Set up the local helper.

Install MCPBytes Vault and connect it as a local MCP server. The owner sets the API key, trusted public pins and storage policy; the agent supplies only these arguments.