SEAR
REMOTE · SEAR.GENESISCONDUCTOR.IO · SCANNED SEP 20
Benchmark-first release surface with a read-only MCP endpoint and operator CLI.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability40
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 108 tokens (~27/item across 4 items; 3 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
How do I install the SEAR MCP server?
SEAR is a hosted endpoint at https://sear.genesisconductor.io/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · sear.genesisconductor.io
claude mcp add --transport http igor-holt-sear 'https://sear.genesisconductor.io/api/mcp'
{
"mcpServers": {
"igor-holt-sear": {
"url": "https://sear.genesisconductor.io/api/mcp"
}
}
} {
"servers": {
"igor-holt-sear": {
"type": "http",
"url": "https://sear.genesisconductor.io/api/mcp"
}
}
} [mcp_servers.igor-holt-sear] url = "https://sear.genesisconductor.io/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"igor-holt-sear": {
"type": "remote",
"url": "https://sear.genesisconductor.io/api/mcp",
"enabled": true
}
}
} openclaw mcp add igor-holt-sear --url 'https://sear.genesisconductor.io/api/mcp' --transport streamable-http
mcp_servers:
igor-holt-sear:
url: "https://sear.genesisconductor.io/api/mcp" {
"McpServers": {
"igor-holt-sear": {
"Transport": "http",
"Url": "https://sear.genesisconductor.io/api/mcp"
}
}
} assistant mcp add igor-holt-sear -t streamable-http -u 'https://sear.genesisconductor.io/api/mcp'
{
"mcpServers": {
"igor-holt-sear": {
"type": "http",
"url": "https://sear.genesisconductor.io/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 −3
- Stability: pass → 0.77 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://sear.genesisconductor.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=genesisconductor.io | CN=WE1,O=Google Trust Services,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 9b25b3009df16a151367a19836175228 |
| SANs: genesisconductor.io, sear.genesisconductor.io, *.sear.genesisconductor.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sear.genesisconductor.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| genesisconductor.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sear.genesisconductor.io/api/mcp | Verified | 200 | |
| http (plaintext) | http://sear.genesisconductor.io/api/mcp | HTTPS enforced | 301 | https://sear.genesisconductor.io/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
sear_benchmarks Show SEAR benchmarks ~36
Use this when you need measured latency, throughput, or visibility artifact status for SEAR.
| Name | Type | Req | Description |
|---|---|---|---|
| view | string | – | – |
No output schema declared.
No examples provided.
sear_cli_help Show SEAR CLI commands ~31
Use this when you need the safe first commands for verifying or querying a SEAR deployment from the terminal.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sear_overview Show SEAR overview ~35
Use this when you need a concise summary of what SEAR ships and why it exists.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | – |
No output schema declared.
No examples provided.
What is the SEAR MCP server?
SEAR is an MCP server listed in the public MCP registry as io.github.igor-holt/sear. Benchmark-first release surface with a read-only MCP endpoint and operator CLI. This page covers its hosted endpoint (https://sear.genesisconductor.io/api/mcp).
Is the SEAR MCP server safe to use?
SEAR scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SEAR MCP server expose?
SEAR exposes 3 tools: sear_overview, sear_benchmarks, sear_cli_help. Their descriptions and schemas cost roughly 102 tokens of context every time the server is loaded.
Does the SEAR MCP server require authentication?
No. We connected to SEAR without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SEAR MCP server still maintained?
SEAR is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.