Aurocrypt Connect

org.goldenphysics.aurocrypt/connect

Aurocrypt Connect: AI access to your services, under approvals you set, without sharing passwords.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "connect": {
      "url": "https://vault.goldenphysics.org/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http connect https://vault.goldenphysics.org/mcp
VS Code
code --add-mcp '{"name":"connect","type":"http","url":"https://vault.goldenphysics.org/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Security & Identity
Version
0.5.2
Registry
active
Published
11/18/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Mostly fine: Aurocrypt Connect is hosted endpoint answering without a key.

Maintained
No commit data
The repository has not been read yet, so the last-commit date is unknown.
Official registry
Active
Published as org.goldenphysics.aurocrypt/connect in the official MCP registry, version 0.5.2.
Source
No licence found
Public repository, but GitHub reports no recognised licence. Check the README before shipping it in a product.
Runs
Hosted by the publisher
Your client talks to vault.goldenphysics.org: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 00:07 UTCStatus history & uptime →
● Working588 msprotocol 2025-06-18v0.5.0tools

The endpoint answered the MCP handshake as "Aurocrypt Connect" and listed 14 tools. Answering since Nov 18, 2026.

Context cost ≈ 4k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 14 tools.

Tools (14)

  • vault_profile

    Return the stable API Vault profile represented by this authenticated connection. No provider credentials or internal owner identifiers are returned.

  • vault_capabilities

    Describe API Vault's broker, autonomy modes, and credential boundary. Never returns stored credentials.

  • vault_connections

    List API-key/PAT connections authorized to this connector. Safe metadata only; raw keys are never returned.

  • vault_services

    List granular OAuth-connected service capabilities explicitly granted to this AI, including safe metadata for the user's bound repositories, projects, and other provider resources.

  • vault_autonomy

    Show this AI's authority mode, provider-wide grants, user-owned connected resources, available provider surfaces (including dynamic Google API origins), and delegated browser profiles. Metadata only; no cookies, tokens, passwords, or provider secrets are returned.

  • vault_models

    List AI models reachable through authorized API-key connections.

  • vault_invoke_read5 params

    Read data through an authorized API-key/PAT connection using a GET request. API Vault controls authentication and destination hosts and injects the stored credential server-side; credentials are never returned. Use vault_invoke_write for any operation that sends data or changes provider state.

    Show parameters
    • connection_idstringrequiredIdentifier of the authorized API-key/PAT connection to use, from vault_connections.
    • operationstringOperation name recorded for this request. Defaults to api.request.
    • pathstringrequiredProvider-relative request path, appended to the connection's controlled destination.
    • headersobjectExtra request headers as name/value pairs. Authentication is controlled by API Vault and cannot be set here.
    • credentialobjectFor owner-bound custom APIs only. API Vault chooses Bearer by default; set this only when the provider docs require a custom header or query parameter. The stor
  • vault_invoke_write7 params

    Execute a provider operation through an authorized API-key/PAT connection using a POST request, including AI model calls. Authentication and destination hosts are controlled by API Vault; the stored credential is injected server-side and never returned.

    Show parameters
    • connection_idstringrequiredIdentifier of the authorized API-key/PAT connection to use, from vault_connections.
    • operationstringOperation name recorded for this request. Defaults to api.request.
    • pathstringrequiredProvider-relative request path, appended to the connection's controlled destination.
    • model_idstringFor AI model calls, the identifier of the model to invoke.
    • bodyRequest body, sent as JSON.
    • headersobjectExtra request headers as name/value pairs. Authentication is controlled by API Vault and cannot be set here.
    • credentialobjectFor owner-bound custom APIs only. API Vault chooses Bearer by default; set this only when the provider docs require a custom header or query parameter. The stor
  • vault_execute4 params

    Execute one reviewed granular capability as the connected user, including approval-gated actions.

    Show parameters
    • account_idstringrequiredIdentifier of the connected provider account, from vault_services or vault_autonomy.
    • capability_idstringrequiredIdentifier of the granular capability to execute, from vault_services.
    • paramsobjectParameters for the capability, as defined by its schema in vault_services.
    • approval_idstringIdentifier of an owner approval already granted for this action, when the capability requires one.
  • vault_provider_read6 params

    Read data through a full-provider or owner-equivalent grant on a registered provider API surface using a GET request. API Vault pins or validates the destination origin, binds GitHub/Supabase requests to resources authorized by this user, and injects that user's OAuth credential server-side. For google.api.generic, supply the exact HTTPS Google API origin under *.googleapis.com. Use vault_provider_write for any operation that changes provider state.

    Show parameters
    • account_idstringrequiredIdentifier of the connected provider account, from vault_services or vault_autonomy.
    • surface_idstringrequiredIdentifier of the registered provider API surface, from vault_autonomy.
    • originstringRequired only for dynamic surfaces such as google.api.generic. Use an origin only (for example https://run.googleapis.com), never a path, query, credentials, or
    • pathstringrequiredProvider-relative path only; absolute and scheme-relative URLs are rejected.
    • headersobjectExtra request headers as name/value pairs. Authentication is controlled by API Vault and cannot be set here.
    • intent_lease_idstringOptional active task-scoped Intent Lease. When supplied, it further narrows this provider action and consumes one lease action.
  • vault_provider_write9 params

    Change provider state through a full-provider or owner-equivalent grant on a registered provider API surface. API Vault pins or validates the destination origin, binds GitHub/Supabase requests to resources authorized by this user, injects that user's OAuth credential server-side, classifies risk, and enforces the owner's financial/security/destructive/communication switches. For google.api.generic, supply the exact HTTPS Google API origin under *.googleapis.com.

    Show parameters
    • account_idstringrequiredIdentifier of the connected provider account, from vault_services or vault_autonomy.
    • surface_idstringrequiredIdentifier of the registered provider API surface, from vault_autonomy.
    • originstringRequired only for dynamic surfaces such as google.api.generic. Use an origin only (for example https://run.googleapis.com), never a path, query, credentials, or
    • methodstringrequiredHTTP method for the provider request.
    • pathstringrequiredProvider-relative path only; absolute and scheme-relative URLs are rejected.
    • bodyRequest body, sent as JSON.
    • headersobjectExtra request headers as name/value pairs. Authentication is controlled by API Vault and cannot be set here.
    • risk_hintstringOptional descriptive hint; it cannot lower server-classified risk.
    • intent_lease_idstringOptional active task-scoped Intent Lease. When supplied, it further narrows this provider action and consumes one lease action.
  • vault_browser_action5 params

    Queue one structured action in a user-controlled authenticated browser profile. Browser cookies/session storage remain on the worker. Returns a job_id; call vault_browser_result until complete.

    Show parameters
    • profile_idstringrequiredIdentifier of the delegated browser profile to act in, from vault_autonomy.
    • actionobjectrequiredThe browser action to queue in the profile.
    • human_approvedbooleanSet true only when the owner has approved this browser action in advance.
    • risk_hintstringOptional descriptive hint; it cannot lower server-classified risk.
    • intent_lease_idstringOptional active task-scoped Intent Lease. When supplied, it further narrows this browser action and consumes one lease action.
  • vault_browser_result1 param

    Read or consume the result of a previously queued API Vault browser job.

    Show parameters
    • job_idstringrequiredIdentifier of the queued browser job, returned by vault_browser_action.
  • vault_usage1 param

    Read metadata-only API-key gateway usage for this connector.

    Show parameters
    • limitintegerMaximum number of usage records to return.

Checked by Serverdex with a plain initialize + tools/list call to vault.goldenphysics.org/mcp, no credentials, about once a day. A failed check is never a removal.

Remotes

  • streamable-httphttps://vault.goldenphysics.org/mcp

The most-starred Security & Identity servers in the index, with their live-check result.

ServerStarsLast pushLive check
Handsy AI5,215Nov 2026Local / not checked
HOL Guard1,118Nov 2026Local / not checked
SonarQube MCP Server689Nov 2026Local / not checked
MCP Ssh Manager545Nov 2026Local / not checked
Security Detections529Nov 2026Local / not checked

Aurocrypt Connect: questions people ask

Is Aurocrypt Connect a remote or a local MCP server?
According to its entry in the official MCP registry, Aurocrypt Connect ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does Aurocrypt Connect need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is Aurocrypt Connect safe to use?
Mostly fine: Aurocrypt Connect is hosted endpoint answering without a key. In detail — maintained: No commit data; official registry: Active; source: No licence found; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
What tools does Aurocrypt Connect expose?
14 tools as listed by the server itself during the live check, including vault_profile, vault_capabilities, vault_connections, vault_services, vault_autonomy. The full list with parameters is in the Live check section above.
How do I add Aurocrypt Connect to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Security & Identity →

Add the badge to your site

Show visitors that Aurocrypt Connect is listed here — it’s also the link we check for a free listing.

Aurocrypt Connect — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/org-goldenphysics-aurocrypt-connect?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Aurocrypt Connect — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Aurocrypt Connect — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/org-goldenphysics-aurocrypt-connect?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/org-goldenphysics-aurocrypt-connect) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/org-goldenphysics-aurocrypt-connect) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/org-goldenphysics-aurocrypt-connect)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/org-goldenphysics-aurocrypt-connect"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/org-goldenphysics-aurocrypt-connect"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/org-goldenphysics-aurocrypt-connect"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).