SOAR Record Gateway

ai.lateosPublished by lateos.aiv1.0.0Updated Oct 24, 2026

SOAR security playbooks for AI agents: fetch, full-text search, and count. Metered via Stripe.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant fetch, full-text search, and count SOAR security playbooks, with access metered through Stripe.

What you can do
SOAR Record Gateway is a remote MCP endpoint that exposes SOAR security playbooks to an AI assistant. Its described capabilities are fetching individual playbooks, running full-text searches across them, and counting records. Access is metered through Stripe, so usage is tied to a paid customer account.
When to use it
Worth adding when an assistant needs to look up or search security orchestration, automation, and response playbooks during incident or security workflows. Less useful if you only need general web content or do not have a metered SOAR subscription.
Requirements
A remote streamable HTTP endpoint; nothing runs locally. It requires an Authorization header carrying a SOAR API key in the form 'Bearer soar_live_ '. Keys are issued per Stripe customer, and the description says a key can be obtained by posting to a Payment-Required URL in an HTTP 402 challenge. Network access to the endpoint is needed.
Before you install
The Authorization header carries a live API key; treat it as a secret and avoid exposing it in logs or shared configs. Access is metered via Stripe, so calls may incur charges against your customer account. The description mentions obtaining a key by posting to a Payment-Required URL, which may involve payment details; verify the provider and pricing before installing.

Installation

In SourceWeft

  1. Open SOAR Record Gateway in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.lateos%2Fsoar-record-gateway/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "soar-record-gateway": {
      "type": "http",
      "url": "https://soar-api.nevada-f99.workers.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.