SEAR

io.github.igor-holtPublished by GitHub account igor-holtv0.1.0Updated Oct 25, 2026

Benchmark-first release surface with a read-only MCP endpoint and operator CLI.

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & Analytics

Overview

AI-generated overview

A remote, read-only MCP endpoint that gives an assistant concise information about the SEAR release: its overview, benchmark figures and safe CLI commands.

What you can do
Get a concise summary of what SEAR ships and why it exists, including its benchmark-first release surface and operator CLI orientation. Retrieve measured latency, throughput and visibility artifact status for SEAR. Look up safe first commands for verifying or querying a SEAR deployment from the terminal. All access is read-only, so the assistant can inform and orient but not change a deployment.
When to use it
Use it when you want an assistant to explain SEAR, quote its benchmark numbers, or suggest first terminal commands for checking a SEAR deployment, without setting up anything locally.
Requirements
A remote streamable HTTP endpoint at the provider's hosted address; no package, environment variable or header is declared. No authentication is declared, so no account or key is needed as described.
Before you install
The endpoint is described as read-only, but the CLI commands it returns are meant to be run by a person in a terminal; review them before executing. Benchmark figures come from the provider and should be treated as its own claims.

Installation

In SourceWeft

  1. Open SEAR in the dashboard and add it to a workspace.
  2. 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/io.github.igor-holt%2Fsear/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": {
    "sear": {
      "type": "http",
      "url": "https://sear.genesisconductor.io/api/mcp"
    }
  }
}

README

This repository has no README.

Tools

3

sear_overview

Show SEAR overview

Use this when you need a concise summary of what SEAR ships and why it exists.

Parametersaudience

sear_benchmarks

Show SEAR benchmarks

Use this when you need measured latency, throughput, or visibility artifact status for SEAR.

Parametersview

sear_cli_help

Show SEAR CLI commands

Use this when you need the safe first commands for verifying or querying a SEAR deployment from the terminal.

Takes no parameters.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

75% 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 listedRequired15 pts
  • 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.