seekrit — secrets for agents
OnlineEncrypted store for API keys and database URLs your code needs. Use them without reading them.
What it can do: 40 tools
signupCreate a seekrit workspace and your own machine credential — one call, no human, no browser. Binds the credential to this session, so every other tool works on your next call with no config change and no reconnect. Returget_startedread-onlyRead the recommended first-project recipe end to end: which steps run here and which need the local crypto plane. Takes no arguments and returns a prose walkthrough. Call this before provisioning anything — it is cheapersetup_local_cryptoread-onlyGet the exact commands for running the local crypto plane (the `@seekrit/mcp` npm server, the `@seekrit/cli` CLI, seekrit-run, seekrit-proxy), including a copy-paste .mcp.json that reuses this session's credential. Takeslocal_tool_forread-onlyLook up how to perform one crypto-plane operation locally — the targeted answer for "the tool I expected is not on this server". Returns { operation, where, how } for a known operation, or a note explaining the plane bouwhoamiread-onlyShow the authenticated machine client and the org it can access. Call this first: it confirms the credential works and tells you which org slug to pass (or that you can omit `org` entirely). Returns { kind, clientId, orglist_orgsread-onlyList the organizations this credential can access. Use it to find the `org` slug every other tool takes; prefer whoami if you also want to confirm which client you are. Returns [{ id, name, slug, role, createdAt }].list_appsread-onlyList the applications in an organization — an application is the top-level container that owns environments, which in turn own secrets. Start here when you know the org but not the app slug the other tools need. Returnslist_envsread-onlyList the environments an application owns (production, staging, …). Names and slugs only — never values. Use this to find the `env` slug that list_secrets and the delete/restore tools take. Returns [{ id, name, slug, applist_branchesread-onlyList ephemeral branch configs (per-PR / preview environments) across an application, or just those forked from one environment. Names, parents, and expiry only — never values. Use it before delete_branch to find a branchlist_groupsread-onlyList the shared groups in an organization — a group is a reusable bag of secrets (a shared datastore, a vendor account) that many application environments can compose in rather than duplicating. Use it to find the `grouplist_group_envsread-onlyList the environments belonging to one shared GROUP — a group holds a separate value set per slug, so its `production` differs from its `staging`. Use this when you already have a group and want its own environments; uselist_env_groupsread-onlyList the shared groups composed INTO one application environment, in precedence order (higher position wins a name clash). Read this to explain where a secret name actually comes from, or to pick the next `position` forlist_membersread-onlyList organization members with their public keys. The public keys are what you pass to `grant_env` on the LOCAL crypto plane to give a human the ability to decrypt — so call this when handing a project off to a person. Rlist_secretsread-onlyList the secret NAMES and versions in an environment. NEVER returns values: this server cannot decrypt. Use it to discover which names exist before referencing them; to read a value, run the local crypto plane (see setuplist_secret_versionsread-onlyList one secret's version history: who wrote each version, when, and which ones were restores. Metadata only — never values. Pair with restore_secret to undo a bad write: read the history here, then pass the version numblist_tokensread-onlyList an organization's service tokens — the long-lived credentials that let a deployed workload fetch secrets. Metadata only: the token strings are shown once at creation (on the local crypto plane) and are never retrievlist_invitesread-onlyList invitations to the organization that have been sent but not yet accepted. Use it to confirm an invite_member call landed, or to find an `inviteId` for revoke_invite. Accepted invitations become members — see list_mekms_list_keysread-onlyList the managed KMS keys the caller can see — symmetric and signing keys seekrit stores wrapped, for encrypting data outside the secret store. Metadata only: key material is fetched and used on the local crypto plane (klist_lease_targetsread-onlyList the registered temporary-access targets — the databases (Postgres, MySQL, …) against which short-lived credentials can be minted on demand instead of storing a standing password. Use it to see what can be leased beflist_leasesread-onlyList temporary-access leases that have been issued — the ledger of who got a short-lived credential against which target and until when. Never includes the credential itself. Use it to find a `leaseId` for revoke_lease,auditread-onlyRead the organization's append-only audit trail, most recent first — every mutation across apps, environments, secrets, members, and tokens. Use it to answer "what changed and who did it"; for one secret's history specifbillingread-onlyShow the org's plan, effective entitlements, current usage, and which upgrade actions are available. Read this if a create action was refused with a plan limit — it names the limit you hit and how to lift it. Returns { pcreate_appCreate an application — the container that will own environments and secrets. This step needs no key material, so it runs here. Creating its environments does NOT: create_env mints a data key and lives on the local cryptcreate_groupCreate a shared group — a reusable bag of secrets (a shared datastore, a vendor account) that many application environments compose in rather than each keeping a copy. Use create_app instead for a deployable service. Nocompose_groupCompose a shared group into an application environment, so that environment resolves the group's secrets as well as its own. Safe to repeat — composing an already-composed group just updates its position. Use uncompose_guncompose_groupRemove a composed group from an application environment. The group and its secrets are untouched — only the link is dropped — but the environment stops resolving every name it inherited from that group, which will breakinvite_memberInvite a human to the organization by email (admin only). They join at the given role once they sign in. Use this to hand a project off to a person — then grant them decryption with `grant_env` on the LOCAL crypto plane,rename_appChange an application's display name. The slug is immutable — every other tool refers to the app by slug, so a rename breaks nothing. Use delete_app + create_app only if the slug itself must change. Returns the updated {rename_groupChange a shared group's display name. The slug is immutable — references from composed environments are by slug, so a rename breaks nothing. Returns the updated { id, orgId, name, slug, createdAt }.restore_secretRoll a secret back to an earlier version — the undo for a bad write. The stored ciphertext is replayed as a NEW version, so history is append-only and nothing is overwritten. Read list_secret_versions first to choose thedelete_secretDelete a secret from an environment, discarding its ciphertext and every version. Irreversible — restore_secret CANNOT bring it back (that only rolls back within a surviving secret's history), and re-creating it means serevoke_tokenRevoke a service token by id. Future key fetches by that token stop immediately, so any workload still using it loses access on its next read. If the holder may have cached the key already, also rotate the environment onrevoke_inviteCancel a pending organization invitation before it is accepted. Use this for an invite sent in error; once someone has accepted, they are a member and this no longer applies. Find the id with list_invites. Returns { ok,revoke_leaseRevoke a temporary-access lease now instead of waiting for it to expire — the leased database credential is dropped at the target immediately, so anything still holding it fails on its next connection. Irreversible: a nekms_disable_keyDisable a managed KMS key: new encrypt/sign operations are blocked, while data already encrypted under it stays decryptable locally by existing grantees. Reversible only by an operator re-enabling the key — there is no ekms_revoke_grantRevoke one principal's grant on a managed KMS key, across all its versions — that user or service token can no longer use the key, while everyone else keeps working. Use kms_disable_key instead to stop the key entirely.delete_appDelete an application together with all of its environments and their secrets, discarding the ciphertext. Irreversible — there is no undo and no export. This is the widest-blast-radius tool here; prefer delete_env for adelete_groupDelete a shared group together with its environments and their secrets, discarding the ciphertext. Irreversible. Every application environment that composed this group loses those names — check list_env_groups (or use undelete_envDelete one application environment and the secrets it owns, discarding the ciphertext. Irreversible, and the environment's data key goes with it — recreating the environment means setting every value again on the local cdelete_branchTear down an ephemeral branch config and every value it overrode. The parent environment is untouched — only the branch's own overrides go — which makes this the routine cleanup when a PR merges. Irreversible; creating a
Connect it
claude mcp add --transport http seekrit-secrets-for-agents https://mcp.seekrit.dev/mcpSettings → Connectors → Add custom connector
URL: https://mcp.seekrit.dev/mcp{
"mcpServers": {
"seekrit-secrets-for-agents": {
"url": "https://mcp.seekrit.dev/mcp"
}
}
}{
"servers": {
"seekrit-secrets-for-agents": {
"type": "http",
"url": "https://mcp.seekrit.dev/mcp"
}
}
}Questions
What does seekrit — secrets for agents do?
Encrypted store for API keys and database URLs your code needs. Use them without reading them. It exposes 40 tools to AI assistants.
What tools does seekrit — secrets for agents provide?
40 tools, including signup, get_started, setup_local_crypto, local_tool_for, whoami, list_orgs, list_apps, list_envs, list_branches, list_groups, list_group_envs, list_env_groups….
How do I connect seekrit — secrets for agents to Claude, ChatGPT or Cursor?
Add the remote MCP endpoint https://mcp.seekrit.dev/mcp as a custom connector or MCP server. Copy-paste setup is on this page.
Does seekrit — secrets for agents require an account or API key?
No sign-in was needed to list its tools. Individual tools may still need an account or API key.
Is seekrit — secrets for agents online?
As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.
Who publishes seekrit — secrets for agents?
seekrit.dev. The official MCP Registry verified that the publisher controls this domain before accepting the listing.
Similar in Crypto & Web3
-
ScorpTech x402 APIOnlineOfficialPopularNew
1,014 x402 pay-per-call tools, USDC on Solana or Base: web, security/OSINT, SEC data, Solana/EVM
-
CoinMarketCapOnline · sign-in requiredOfficialPopular
Official CoinMarketCap MCP server: real-time crypto prices, market cap, rankings and exchange data.
-
Diamond Bitcoin IntelligenceOnlineOfficialPopular
Free Bitcoin sanctions screen; paid address risk checks, market pulse, whale reports and alerts.
-
DMCA.com CasesOnlineOfficialPopular
DMCA.com cases. Your own token via Authorization: Bearer. No function key, no shared token.
-
EtherscanOnlineOfficialPopular
Read-only Etherscan V2 blockchain data: balances, transactions, transfers, tokens, contracts, logs.
-
Alchemy MCP ServerOnline · sign-in requiredOfficialPopular
Blockchain data across 100+ chains: token prices, NFTs, transfers, simulation, traces, Solana DAS