Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

enclave

NPM · ENCLAVE-LINK

Your agent asks for a password by one-time link, not in chat, and uses it without seeing it.

Available components

71 Trust /100

Last scanned (1 hour ago)

Scores higher than 40% of npm servers

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 581 tokens (~116/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 56

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/enclave-link@0.2.13

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~512 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
list_secrets ~51

List what's saved in the vault: names and their fields, not their values. Check here before asking the person for something.

NameTypeReqDescription
searchstring–A name or website to match, like "github"

No output schema declared.

No examples provided.

request_secret ~132

Use this whenever you need a password, API key, 2FA key or other secret from the person, instead of asking in chat. It returns a one-time link; what they type there is locked in their browser for this vault. Then call wait_for_secret.

NameTypeReqDescription
fieldsarray–What to ask for, like ["email", "password"]. Defaults to ["password"]. A field named "totp" asks for a 2FA setup key.
namestringyesWhat the secret is for. The person sees it as the title, like "Netflix" or "OpenAI API key"

No output schema declared.

No examples provided.

run_with_secrets ~164

Run a program with saved secrets in its environment. Their values are replaced with [hidden VAR] in the output, so you can use a secret without seeing it. A "totp" field gives its current 2FA code. Example: {"command": ["sh", "-c", "curl -H \"Authorization: Bearer $KEY\" https://api.example.com/me"], "secrets": {"KEY": "Example/api key"}}

NameTypeReqDescription
commandarrayyesThe program and its arguments. Use ["sh", "-c", "…"] for shell syntax, and refer to secrets as $VAR inside it.
secretsobjectyesEnvironment variables to set, each from "<name>/<field>", like {"STRIPE_KEY": "Stripe/key"}

No output schema declared.

No examples provided.

sign_in_with_passkey ~94

Let the browser sign in once with a saved passkey, in the next 5 minutes. Call it, then click the site's passkey sign-in: enclave's browser extension asks the vault to sign, and the passkey's key stays in the vault.

NameTypeReqDescription
fieldstring–The field holding it. Defaults to "passkey".
namestringyesThe saved item with the passkey

No output schema declared.

No examples provided.

wait_for_secret ~71

Wait until the person sends the secret from request_secret, then save it to the vault. It returns the moment they tap Send. After 25 minutes it returns so you can call it again, and the link stays open for 24 hours.

NameTypeReqDescription
namestringyesThe name given to request_secret

No output schema declared.

No examples provided.

Install

How do I install the enclave MCP server?

enclave runs locally as an npm package, launched with npx -y enclave-link. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · enclave-link

# add to Claude Code
claude mcp add avgvstvs96-enclave -- npx -y enclave-link
Common questions

What is the enclave MCP server?

enclave is an MCP server listed in the public MCP registry as io.github.AVGVSTVS96/enclave. Your agent asks for a password by one-time link, not in chat, and uses it without seeing it. This page covers its npm package (enclave-link).

Is the enclave MCP server safe to use?

enclave scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the enclave MCP server expose?

enclave exposes 5 tools: request_secret, wait_for_secret, run_with_secrets, sign_in_with_passkey, list_secrets. Their descriptions and schemas cost roughly 512 tokens of context every time the server is loaded.

Is the enclave MCP server still maintained?

enclave is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the enclave MCP server under?

enclave declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.