Aurocrypt Connect
https://vault.goldenphysics.org
Registry code: ac7174823e75be0b
Aurocrypt Connect: AI access to your services, under approvals you set, without sharing passwords.
from a public catalogue that lists it, not from the operator
- endpoint
- https://vault.goldenphysics.org/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is Aurocrypt Connect live?
- Yes — it answered the hub's last check (checked 9h ago). It answered 100% of checks over the last 30 days.
- Is Aurocrypt Connect free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does Aurocrypt Connect have?
- 14 tools: vault_connections, vault_invoke_read, vault_invoke_write, vault_provider_read, vault_services, vault_models, vault_capabilities, vault_autonomy, ….
- Is Aurocrypt Connect safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 14 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
vault_connections auth-required 2d ago
List API-key/PAT connections authorized to this connector. Safe metadata only; raw keys are never returned.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesvault_invoke_read auth-required never probed
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.
{ "type": "object", "required": [ "connection_id", "path" ], "properties": { "path": { "type": "string", "description": "Provider-relative request path, appended to the connection's controlled destination." }, "headers": { "type": "object", "description": "Extra request headers as name/value pairs. Authentication is controlled by API Vault and cannot be set here.", "additionalProperties": { "type": "string" } }, "operation": { "type": "string", "default": "api.request", "description": "Operation name recorded for this request. Defaults to api.request." }, "credential": { "type": "object", "properties": { "mode": { "enum": [ "bearer", "header", "query" ], "type": "string", "description": "How the stored credential is presented: a bearer Authorization header, a custom header, or a query parameter." }, "name": { "type": "string", "description": "Header or query parameter name, required when mode is header or query." }, "scheme": { "type": "string", "description": "Authentication scheme prefix for the credential value, when the provider requires one." } }, "description": "For 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 stored key is still injected server-side and never returned.", "additionalProperties": false }, "connection_id": { "type": "string", "description": "Identifier of the authorized API-key/PAT connection to use, from vault_connections." } }, "additionalProperties": false }arguments 54 linesvault_invoke_write auth-required never probed
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.
{ "type": "object", "required": [ "connection_id", "path" ], "properties": { "body": { "description": "Request body, sent as JSON." }, "path": { "type": "string", "description": "Provider-relative request path, appended to the connection's controlled destination." }, "headers": { "type": "object", "description": "Extra request headers as name/value pairs. Authentication is controlled by API Vault and cannot be set here.", "additionalProperties": { "type": "string" } }, "model_id": { "type": "string", "description": "For AI model calls, the identifier of the model to invoke." }, "operation": { "type": "string", "default": "api.request", "description": "Operation name recorded for this request. Defaults to api.request." }, "credential": { "type": "object", "properties": { "mode": { "enum": [ "bearer", "header", "query" ], "type": "string", "description": "How the stored credential is presented: a bearer Authorization header, a custom header, or a query parameter." }, "name": { "type": "string", "description": "Header or query parameter name, required when mode is header or query." }, "scheme": { "type": "string", "description": "Authentication scheme prefix for the credential value, when the provider requires one." } }, "description": "For 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 stored key is still injected server-side and never returned.", "additionalProperties": false }, "connection_id": { "type": "string", "description": "Identifier of the authorized API-key/PAT connection to use, from vault_connections." } }, "additionalProperties": false }arguments 61 linesvault_provider_read auth-required never probed
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.
{ "type": "object", "required": [ "account_id", "surface_id", "path" ], "properties": { "path": { "type": "string", "description": "Provider-relative path only; absolute and scheme-relative URLs are rejected." }, "origin": { "type": "string", "description": "Required 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 fragment." }, "headers": { "type": "object", "description": "Extra request headers as name/value pairs. Authentication is controlled by API Vault and cannot be set here.", "additionalProperties": { "type": "string" } }, "account_id": { "type": "string", "description": "Identifier of the connected provider account, from vault_services or vault_autonomy." }, "surface_id": { "type": "string", "description": "Identifier of the registered provider API surface, from vault_autonomy." }, "intent_lease_id": { "type": "string", "description": "Optional active task-scoped Intent Lease. When supplied, it further narrows this provider action and consumes one lease action." } }, "additionalProperties": false }arguments 38 linesvault_services auth-required 35h ago
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesvault_models auth-required 35h ago
List AI models reachable through authorized API-key connections.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesvault_capabilities auth-required 9h ago
Describe API Vault's broker, autonomy modes, and credential boundary. Never returns stored credentials.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesvault_autonomy auth-required 9h ago
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesvault_provider_write auth-required never probed
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.
{ "type": "object", "required": [ "account_id", "surface_id", "method", "path" ], "properties": { "body": { "description": "Request body, sent as JSON." }, "path": { "type": "string", "description": "Provider-relative path only; absolute and scheme-relative URLs are rejected." }, "method": { "enum": [ "POST", "PUT", "PATCH", "DELETE" ], "type": "string", "description": "HTTP method for the provider request." }, "origin": { "type": "string", "description": "Required 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 fragment." }, "headers": { "type": "object", "description": "Extra request headers as name/value pairs. Authentication is controlled by API Vault and cannot be set here.", "additionalProperties": { "type": "string" } }, "risk_hint": { "type": "string", "description": "Optional descriptive hint; it cannot lower server-classified risk." }, "account_id": { "type": "string", "description": "Identifier of the connected provider account, from vault_services or vault_autonomy." }, "surface_id": { "type": "string", "description": "Identifier of the registered provider API surface, from vault_autonomy." }, "intent_lease_id": { "type": "string", "description": "Optional active task-scoped Intent Lease. When supplied, it further narrows this provider action and consumes one lease action." } }, "additionalProperties": false }arguments 56 linesvault_browser_action auth-required never probed
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.
{ "type": "object", "required": [ "profile_id", "action" ], "properties": { "action": { "type": "object", "required": [ "type" ], "properties": { "ms": { "type": "integer", "description": "Duration in milliseconds for wait actions." }, "key": { "type": "string", "description": "Keyboard key to press, for press actions." }, "url": { "type": "string", "description": "Target URL for navigate actions." }, "name": { "type": "string", "description": "Accessible name used with role to find the element." }, "path": { "type": "string", "description": "File path for download or upload actions." }, "role": { "type": "string", "description": "ARIA role used to find the element to act on." }, "type": { "enum": [ "navigate", "snapshot", "screenshot", "click", "type", "press", "select", "wait", "download", "upload" ], "type": "string", "description": "The kind of browser action to perform." }, "clear": { "type": "boolean", "description": "For type actions, clear the field before typing." }, "value": { "description": "Value to type, select, or upload, depending on the action type." }, "delay_ms": { "type": "integer", "description": "Delay in milliseconds between steps, when supported." }, "selector": { "type": "string", "description": "CSS selector identifying the element to act on." }, "full_page": { "type": "boolean", "description": "For screenshot actions, capture the full page instead of the viewport." }, "timeout_ms": { "type": "integer", "description": "Maximum time in milliseconds to wait for the action to complete." }, "wait_until": { "type": "string", "description": "Page load state to wait for on navigate actions, such as load or networkidle." }, "text_selector": { "type": "string", "description": "Visible text used to find the element when no selector is given." } }, "description": "The browser action to queue in the profile.", "additionalProperties": false }, "risk_hint": { "type": "string", "description": "Optional descriptive hint; it cannot lower server-classified risk." }, "profile_id": { "type": "string", "description": "Identifier of the delegated browser profile to act in, from vault_autonomy." }, "human_approved": { "type": "boolean", "description": "Set true only when the owner has approved this browser action in advance." }, "intent_lease_id": { "type": "string", "description": "Optional active task-scoped Intent Lease. When supplied, it further narrows this browser action and consumes one lease action." } }, "additionalProperties": false }arguments 107 linesvault_usage auth-required 9h ago
Read metadata-only API-key gateway usage for this connector.
{ "type": "object", "properties": { "limit": { "type": "integer", "default": 100, "maximum": 500, "minimum": 1, "description": "Maximum number of usage records to return." } }, "additionalProperties": false }arguments 13 linesvault_profile auth-required 35h ago
Return the stable API Vault profile represented by this authenticated connection. No provider credentials or internal owner identifiers are returned.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesvault_execute auth-required never probed
Execute one reviewed granular capability as the connected user, including approval-gated actions.
{ "type": "object", "required": [ "account_id", "capability_id" ], "properties": { "params": { "type": "object", "description": "Parameters for the capability, as defined by its schema in vault_services." }, "account_id": { "type": "string", "description": "Identifier of the connected provider account, from vault_services or vault_autonomy." }, "approval_id": { "type": "string", "description": "Identifier of an owner approval already granted for this action, when the capability requires one." }, "capability_id": { "type": "string", "description": "Identifier of the granular capability to execute, from vault_services." } }, "additionalProperties": false }arguments 26 linesvault_browser_result auth-required never probed
Read or consume the result of a previously queued API Vault browser job.
{ "type": "object", "required": [ "job_id" ], "properties": { "job_id": { "type": "string", "description": "Identifier of the queued browser job, returned by vault_browser_action." } }, "additionalProperties": false }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idac7174823e75be0b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/ac7174823e75be0b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/ac7174823e75be0b?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.