Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.neus.network/llms.txt

Use this file to discover all available pages before exploring further.

Three public MCP tools manage encrypted secrets tied to your NEUS Profile. Values are sealed with AES-256-GCM and never returned in plaintext through MCP. Sign in first — OAuth or a Profile access key (Auth). Call neus_me to confirm the session wallet before create or revoke.
ToolPurpose
neus_secret_createStore a named secret as an encrypted proof
neus_secret_listList secret metadata (alias, qHash, type) — no values
neus_secret_revokeRevoke a secret proof by qHash

​
Create (neus_secret_create)

{
  "walletAddress": "0x...",
  "alias": "OPENAI_API_KEY",
  "secretType": "single",
  "content": "sk-..."
}
FieldNotes
walletAddressMust match your authenticated Profile wallet
aliasLetters, numbers, underscore; must start with a letter
secretTypesingle (default) or bundle (JSON object string in content)
contentPlaintext input — encrypted at rest; never echoed back via MCP

​
List (neus_secret_list)

{
  "walletAddress": "0x...",
  "limit": 50,
  "offset": 0
}
Without Bearer auth, the tool returns an empty list and authRequired: true — it does not leak metadata.

​
Revoke (neus_secret_revoke)

{
  "walletAddress": "0x...",
  "qHash": "..."
}
Requires authenticated ownership of the secret proof.

​
Security

  • Never paste secret values into chat logs or public issues.
  • Prefer OAuth or Profile keys in MCP config only — not in app browser bundles.
  • Rotate or revoke through neus_secret_revoke and re-create if a value is exposed.

Auth

Current user