An agent can connect on its own if it already holds SOAR_RECORD_GATEWAY_TOKEN.Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.
tools.descriptions, tools.description_length, tools.schemas, tools.annotations, tools.directory_hints, tools.token_cost, tools.api_dumptool list unknown (behind auth, not probed, or empty)
stabilityn/a · weight 15
n/a
stability.changes, stability.rug_pulltool list unknown
dependenciesn/a · weight 15
n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package
Tool list unknown · checked 2026-10-21 01:06 UTC
Tool changes
No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
Pre-execution policy gate for consequential agent actions with durable trust receipts.
Official server.json
{
"name": "ai.lateos/soar-record-gateway",
"title": "SOAR Record Gateway",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://soar-api.nevada-f99.workers.dev/mcp",
"type": "streamable-http",
"headers": [
{
"name": "Authorization",
"isSecret": true,
"isRequired": true,
"description": "SOAR API key formatted as 'Bearer soar_live_<key>'. Keys are issued per Stripe customer. No key? POST to the Payment-Required URL in an HTTP 402 MPP challenge from https://soar-api.nevada-f99.workers.dev/v1/records/fetch to subscribe via Stripe checkout (metered SOAR plan, $0.01/search, no upfront charge), then retrieve the issued key once from the credential_endpoint."
}
]
}
],
"version": "1.0.0",
"repository": {
"url": "https://github.com/lateos-ai/website",
"source": "github"
},
"websiteUrl": "https://lateos.ai",
"description": "SOAR security playbooks for AI agents: fetch, full-text search, and count. Metered via Stripe."
}