Skip to main content
Toknbase

MCP · INTEGRATION

The AI SecOps agent your AI agent can call

MCP (Model Context Protocol) is an open standard that lets AI assistants like Claude securely connect to your tools and data — including your Toknbase vault — so they can read secrets, trigger rotations, and run security checks on your behalf.

Connect Toknbase to Cursor, Claude, or other AI tools so they can scan and fix exposed secrets without leaving your editor.

Add one config block. Ask your AI assistant to find and fix exposed secrets — automatically, every action logged on-chain.

Used by security-conscious developers on the Internet Computer

Generate your token — it's free

1. Copy the config

Live

Paste this into your AI client's MCP settings and replaceYOUR_TOKENwith your agent token. The endpoint athttps://4wj64-piaaa-aaaan-q5q7q-cai.icp0.io/mcpis hosted on the Internet Computer — no install needed.

mcp-config.json
{
"mcpServers": {
"toknbase": {
"url":"https://4wj64-piaaa-aaaan-q5q7q-cai.icp0.io/mcp",
"headers": {
"Authorization":"Bearer YOUR_TOKEN"
 }
 }
 }
}

Your AI agent will return an auth error without a Bearer token — that's intentional. Generate yours below and paste it in.

2. Generate your token

Takes 30 seconds. Free, no credit card.

Generate token →

Three steps to your first agent action

1

Copy the config above into your AI client

Claude Desktop, Cursor, Windsurf, VS Code — any MCP-compatible editor.

2

Generate your free token at /tokens

Takes 30 seconds. Your token is the credential your AI agent uses to authenticate — shown once, store it safely.

3

Ask your AI agent:"Are there any exposed secrets in this project?"

Toknbase scans, finds exposures, and offers to rotate and remove them — all inside your editor.

Try the commands

command demo

Click a command chip or type one below. Every response is instant and deterministic — no LLM, no async delays.

/scan

Checks your code or a repo URL for exposed secrets and tells you what it found

/rotate

Replaces an exposed key with a new one automatically, then logs the action

/audit

Shows a full history of every security action taken in your vault

/secrets list

Lists all secrets stored in your vault (values stay hidden)

/secrets get [name]

Retrieves the value of a specific secret by name

Toknbase · Command Demosimulated · no real data

Click a command above or type one below — results appear instantly, no LLM needed.

>

What your AI agent can do

A real conversation between Cursor and Toknbase — from detection to remediation in one session.

Cursor · Toknbase via MCP
>Are there any exposed secrets in this project?
Found 2 critical exposures.
• AWS_SECRET_KEY in .env — line 14
• STRIPE_SECRET_KEY in config/secrets.yml — line 8
Say 'fix these' to rotate and open a PR.
>Fix these.
Rotating AWS key… ✓ New key generated.
PR #47 opened — hardcoded key removed from .env.
New values delivered to your vault.
✓ Actions logged on-chain.

Editor Config

All configs below use thehosted HTTP endpoint— no npm install needed.

Paste the URL directly into your AI client's MCP server field. No config file or installation needed — the server runs on the Internet Computer.

No config file needed — paste URL directly into your agent

{
  "mcpServers": {
    "toknbase": {
      "type": "http",
      "url": "https://4wj64-piaaa-aaaan-q5q7q-cai.icp0.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_AGENT_TOKEN"
      }
    }
  }
}

Where to get YOUR_AGENT_TOKEN

Dashboard → Tokens → Service Identities → Create new token → select MCP scope

What scope the token needs

Token must havefull_accessor MCP-enabled scope. Limited scope tokens fail silently.

If you see"Unable to authenticate"

The Authorization header is missing, the token has wrong scope, or the token is expired/revoked.

Agent Activity

last 50 entries

AGENT ACTIVITY

No agent activity yet

Make a request from your AI editor to see MCP tool calls and secret access events here.

What this MCP can do

Toknbase is zero-trust by design. Admin operations and plaintext value access are excluded from the MCP surface.

List secret names and metadata by folder
List all secrets and folders
Create and update secrets
Manage folders (full_access scope)
Rotate secrets (read_write or full_access scope)
Scoped read-only or read-write access
Delete secrets (read_write or full_access scope)
Manage team members
Access billing or plan settings
View audit log entries (all scopes)
Create or revoke agent tokens
Access other users' data

Setup

Test your connection

Verify your agent token works before configuring your editor

Sign in to test your connection.

Where to get your agent token

  1. 1.Dashboard → Tokens → Service Identities
  2. 2.Click Create new token
  3. 3.Select MCP scope (or full_access for all tools)
  4. 4.Copy the agt_ token — shown only once

Verify Setup

After saving your MCP config and restarting your editor, confirm the connection is live by asking your AI assistant:

List my Toknbase secrets

Expected: secret names only, never values — zero-trust by design.

Note

Not working? Check that your agent token has at leastread_only scope and that your editor picked up the updated config (most editors require a restart or full window reload).

HTTP REST API

HTTP mode
Base URLhttps://4wj64-piaaa-aaaan-q5q7q-cai.icp0.io
Auth
Authorization: Bearer YOUR_AGENT_TOKEN

Pass your agent token in theAuthorizationheader on every request.

MethodPathMin scope
GET/api/secretsread_only
GET/api/foldersread_only
POST/api/secretsread_write
PUT/api/secretsread_write
POST/api/folders/assignfull_access
Example: list secrets
curl -X GET \
"https://4wj64-piaaa-aaaan-q5q7q-cai.icp0.io/api/secrets" \
 -H"Authorization: Bearer YOUR_AGENT_TOKEN" \
 -H"Content-Type: application/json"
Example: create a secret
curl -X POST \
"https://4wj64-piaaa-aaaan-q5q7q-cai.icp0.io/api/secrets" \
 -H"Authorization: Bearer YOUR_AGENT_TOKEN" \
 -H"Content-Type: application/json" \
 -d '{"name":"STRIPE_KEY","value":"sk_live_..."}'

HTTP REST is thedefault transport — all calls route through these REST endpoints automatically.

Troubleshooting

Editor isn't picking up the MCP server

Fully restart your editor after adding the config — most editors only load MCP servers at startup.

Getting 'Unable to authenticate'

The Authorization header is missing, the token has the wrong scope, or the token is expired/revoked. Token needs full_access or MCP scope.

Getting a 403 Forbidden error

Your agent token exists but lacks the required scope. Check the 'Min scope' column in the tools table, then re-generate a token with the correct scope.

Canister appears offline or requests time out

ICP canisters occasionally have brief latency spikes. Retry after a few seconds. Canister ID: 4wj64-piaaa-aaaan-q5q7q-cai.

MCP tools not appearing in Cursor

Use Cmd+Shift+P → 'Reload Window'. The MCP server needs a full window reload to re-initialize.

Claude Desktop config not found

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json — Windows: %APPDATA%\Claude\claude_desktop_config.json

Available Tools

15 tools

Toknbase is zero-trust by design. Secrets with agent access enabled are returned as plaintext values — only secrets with agent access enabled are accessible.

ToolMin scope
toknbase_list_secretsread_only
toknbase_create_secretread_write
toknbase_update_secretread_write
toknbase_delete_secretread_write
toknbase_get_secretread_only
toknbase_search_secretsread_only
toknbase_list_foldersread_only
toknbase_create_folderfull_access
toknbase_assign_folderfull_access
toknbase_rotate_secretread_write
toknbase_batch_create_secretsread_write
toknbase_list_team_secretsread_only
toknbase_get_audit_logread_only
toknbase_get_agent_token_inforead_only
toknbase_get_secret_by_environmentread_only

@toknbase/mcp-server is live on npm.View on npm

Was this page helpful?