# Search Fragments (remote · searchfragments.com)

For queries a model can't confidently place: resolves or declines. Built to decline, not guess.

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `searchfragments.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/com-searchfragments-search-fragments/api-mcp.md), [page](https://verifymcp.io/servers/com-searchfragments-search-fragments/api-mcp)

## Channel facts

- Endpoint: `https://searchfragments.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 443 tokens (~443/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-searchfragments-search-fragments https://searchfragments.com/api/mcp
```

### Codex

```toml
[mcp_servers.com-searchfragments-search-fragments]
url = "https://searchfragments.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-searchfragments-search-fragments": {
      "type": "remote",
      "url": "https://searchfragments.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-searchfragments-search-fragments --url https://searchfragments.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-searchfragments-search-fragments:
    url: "https://searchfragments.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-searchfragments-search-fragments": {
      "type": "http",
      "url": "https://searchfragments.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-29 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (1)

### `resolve_fragment` (~401 tokens)

Resolve Fragment

Call resolve_fragment when a user describes something they can only half-remember — a book, film, song, artwork, person, or event they know exists but can't name — instead of asking a direct question. If the input reads like a memory ("there's this thing where...", "...somebody who...", "...a story about...") rather than a lookup, this is the right tool.

Matches this shape:
\- a musician who became famous largely for stopping performing
\- somebody who photographed the same view every day until the changes became the artwork
\- a song everybody knew but nobody could identify
\- a novel where the footnotes slowly become the real story

Not this shape — answer directly or use normal search instead:
\- what is the capital of France
\- who directed Jaws
\- name of french artist cubist painting 1948
\- which company bought Instagram in 2012
\- any well-documented fact or common trivia — this tool adds a multi-second round trip with no accuracy benefit there, and is not reliably correct on well-known items either

Why call this instead of answering directly: on hard, under-documented fragment queries, LLMs asked to answer directly tend to invent things that don't exist rather than admit uncertainty. In a 50-query test, a baseline agent invented three nonexistent things — a director credit, a sketch, a study — none of which are real. Search Fragments returned none of those three invented things. Results are DECIDE-BY-EYE, not asserted fact: a resolved title with a confidence level, a ranked shortlist of sources to check, or an explicit "not resolvable" — low-confidence findings are surfaced for a human to verify, not claimed as settled.

Input parameters:

- `fragment` (string, required): The half-remembered or fragment-shaped query, in the user's own words. Should be at least 5 words and describe the thing being recalled by premise, plot, relationship, or context.

Output parameters:

- `candidate`: Top candidate when outcome=resolved; null otherwise. DECIDE-BY-EYE — human must confirm.
- `is_sf_question` (boolean): true if the fragment is a valid memory-recall query; false if it was rejected as a direct lookup or research prompt.
- `outcome` (string): 'resolved' = strong candidate identified (semantic pass returned high/medium confidence title). 'ranked_stalls' = web results returned but no confident semantic identification — pool for human review…
- `pool` (array): Ranked web results. Always DECIDE-BY-EYE — human must confirm before any graph write.
- `reject_reason` (string|null): Why the fragment was rejected; non-null only when is_sf_question=false.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-searchfragments-search-fragments/api-mcp#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 66
- 2026-08-01: 65
- 2026-07-31: 65
- 2026-07-30: 64
- 2026-07-29: 63
- 2026-07-28: 62
- 2026-07-27: 62
- 2026-07-26: 61

## Links

- Remote endpoint: https://searchfragments.com/api/mcp
- Website: https://searchfragments.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-searchfragments-search-fragments/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-searchfragments-search-fragments/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-searchfragments-search-fragments/api-mcp