# mcpsurfr (oci · ghcr.io/nkapila6/mcpsurfr)

Local web search with multi-engine deep research and on-device re-ranking. No API keys.

- Trust score: 38/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- oci · `ghcr.io/nkapila6/mcpsurfr`: 38/100 (this document), [markdown](https://verifymcp.io/servers/nkapila6-mcpsurfr/ghcr-io-nkapila6-mcpsurfr.md), [page](https://verifymcp.io/servers/nkapila6-mcpsurfr/ghcr-io-nkapila6-mcpsurfr)
- pypi · `mcpsurfr`: 55/100, [markdown](https://verifymcp.io/servers/nkapila6-mcpsurfr/mcpsurfr.md), [page](https://verifymcp.io/servers/nkapila6-mcpsurfr/mcpsurfr)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/nkapila6/mcpsurfr`
- Version: `v1.2.3`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1715 tokens (~285/item across 6 items; 4 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: the tool surface changed between v1.1.1 and v1.2.3: 3 tool removals, 0 breaking changes, 1 additions.
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the mcpsurfr MCP server?

mcpsurfr runs locally as a container image, launched with docker run --rm -i -e MCPSURFR_MAX_CHARS ghcr.io/nkapila6/mcpsurfr:v1.2.3. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add nkapila6-mcpsurfr -- docker run --rm -i -e MCPSURFR_MAX_CHARS ghcr.io/nkapila6/mcpsurfr:v1.2.3
```

This image reads MCPSURFR_MAX_CHARS. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Cursor

```json
{
  "mcpServers": {
    "nkapila6-mcpsurfr": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "MCPSURFR_MAX_CHARS",
        "ghcr.io/nkapila6/mcpsurfr:v1.2.3"
      ]
    }
  }
}
```

This image reads MCPSURFR_MAX_CHARS. Set it in your client's env block for this server; docker run -e passes it through to the container.

### VS Code

```json
{
  "servers": {
    "nkapila6-mcpsurfr": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "MCPSURFR_MAX_CHARS",
        "ghcr.io/nkapila6/mcpsurfr:v1.2.3"
      ]
    }
  }
}
```

This image reads MCPSURFR_MAX_CHARS. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Codex

```bash
codex mcp add nkapila6-mcpsurfr -- docker run --rm -i -e MCPSURFR_MAX_CHARS ghcr.io/nkapila6/mcpsurfr:v1.2.3
```

This image reads MCPSURFR_MAX_CHARS. Set it in your client's env block for this server; docker run -e passes it through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nkapila6-mcpsurfr": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "MCPSURFR_MAX_CHARS",
        "ghcr.io/nkapila6/mcpsurfr:v1.2.3"
      ],
      "enabled": true
    }
  }
}
```

This image reads MCPSURFR_MAX_CHARS. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Hermes

```yaml
mcp_servers:
  nkapila6-mcpsurfr:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "MCPSURFR_MAX_CHARS", "ghcr.io/nkapila6/mcpsurfr:v1.2.3"]
```

This image reads MCPSURFR_MAX_CHARS. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Netclaw

```json
{
  "McpServers": {
    "nkapila6-mcpsurfr": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "MCPSURFR_MAX_CHARS",
        "ghcr.io/nkapila6/mcpsurfr:v1.2.3"
      ]
    }
  }
}
```

This image reads MCPSURFR_MAX_CHARS. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Other

```json
{
  "mcpServers": {
    "nkapila6-mcpsurfr": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "MCPSURFR_MAX_CHARS",
        "ghcr.io/nkapila6/mcpsurfr:v1.2.3"
      ]
    }
  }
}
```

This image reads MCPSURFR_MAX_CHARS. Set it in your client's env block for this server; docker run -e passes it through to the container.

## 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-10-29 (score 38, −3)

- [security regression] Stability: 0.17 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.17 → fail
- [functional regression] Schema quality: 174 → 285
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional] Package version: v1.1.1 → v1.2.3

### 2026-10-28 (score 41, +1)

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

### 2026-10-26 (score 40, +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-10-24 (score 39, +1)

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

### 2026-10-23 (score 38)

First indexed and scored.

## MCP tools (4)

### `rag_search_ddgs` (~355 tokens)

Web search

Search the web and return the most relevant pages as text, for when whole pages are
wanted (search returns only the relevant passages). Results are re-ranked locally by
semantic similarity to the query before the top pages are fetched.

Input parameters:

- `backend` (string): Search backend, same names as deep_research. Default "auto" (ddgs            metasearch over several engines, skipping blocked ones). Non-auto            backends that return nothing are retried with…
- `exclude_domains`: Never results from these sites. Example: ["pinterest.com"]
- `include_domains`: Only results from these sites, subdomains included. Example: ["python.org", "stackoverflow.com"]
- `include_urls` (boolean): Whether to include each page's source URL for citation.                 Default: True
- `news` (boolean): Search news articles instead of the web. Results then carry their published "date". News backends: auto, bing, duckduckgo, yahoo. Pair with recency for current events.
- `num_results` (integer): Number of initial search results to rank.               More results provide better coverage but increase processing time.               Default: 10
- `query` (string, required): The search query. Use natural language questions or keywords.         Example: "latest developments in quantum computing"
- `recency`: Only results from the past "day", "week", "month" or "year".
- `region`: Region-language code like "us-en", "uk-en" or "de-de". Default: ddgs's own (us-en).
- `top_k` (integer): Number of top-ranked pages to fetch and return.         Default: 5

### `search` (~427 tokens)

Search (passages)

Search the web and return only the passages that answer the query, not whole
pages: usually about a tenth of the text of rag_search_ddgs. Use this first.

Tiers, cheapest first:
1\. Search, then keep the top_pages results whose title/snippet match best.
2\. Fetch those pages, split them into ~600-char passages, keyword-match them (BM25)
   against the query plus `keywords`.
3\. Only if that leaves too many candidates, or matches nothing (a paraphrase),
   the local embedder ranks them by meaning.
If nothing matched the keywords and the client can show questions, the user is
asked whether they want the full pages instead.

Input parameters:

- `backend` (string): Search backend, same names as deep_research. Default "auto".
- `exclude_domains`: Never results from these sites. Example: ["pinterest.com"]
- `include_domains`: Only results from these sites, subdomains included. Example: ["python.org", "stackoverflow.com"]
- `keywords`: Terms a good answer would contain, including synonyms and exact phrases. Example for "how do I make postgres faster": ["index", "EXPLAIN ANALYZE", "query planner", "vacuum"]. Strongly improves result…
- `max_passages` (integer): Passages to return. Default 8.
- `news` (boolean): Search news articles instead of the web. Results then carry their published "date". News backends: auto, bing, duckduckgo, yahoo. Pair with recency for current events.
- `num_results` (integer): Search results to consider. Default 10.
- `query` (string, required): The question or topic, in natural language.
- `recency`: Only results from the past "day", "week", "month" or "year".
- `region`: Region-language code like "us-en", "uk-en" or "de-de". Default: ddgs's own (us-en).
- `top_pages` (integer): Pages to fetch and split. Default 5.

### `read_url` (~145 tokens)

Read a page

Read one page whose URL you already have: a link the user pasted, or one from earlier
results. HTML or PDF. With a query, returns only the passages that answer it, the same
way search does; without one, the page's main text (cut to the shared budget).

Input parameters:

- `keywords`: Terms a good answer would contain, as for search.
- `max_passages` (integer): Passages to return when there's a query. Default 8.
- `query`: What you want from the page. Leave out to get the whole text.
- `url` (string, required): A public http(s) URL. Localhost and private network addresses are refused.

### `deep_research` (~440 tokens)

Deep research

Research a topic across several search terms and engines. Each term is searched on
each backend, results are re-ranked locally by relevance, duplicates are removed,
and the best pages are fetched as text.

Backends: auto, brave, duckduckgo, google, grokipedia, mojeek, startpage, wikipedia, yahoo.
\- "auto" (default): ddgs metasearch over several engines, skipping blocked ones. Most reliable.
\- "brave": fast and usually available.
\- "wikipedia": exact article lookups, best with title-like terms.
\- "google", "startpage", "yahoo", "mojeek": often blocked. Empty engines are reported
  as warnings, and if every chosen engine is empty the terms are retried with "auto".

Input parameters:

- `backends`: Backends to use. Defaults to ["auto"]. Unknown names are skipped with a warning.
- `exclude_domains`: Never results from these sites. Example: ["pinterest.com"]
- `include_domains`: Only results from these sites, subdomains included. Example: ["python.org", "stackoverflow.com"]
- `include_urls` (boolean): Whether to include each page's source URL.
- `news` (boolean): Search news articles instead of the web. Results then carry their published "date". News backends: auto, bing, duckduckgo, yahoo. Pair with recency for current events.
- `num_results_per_term` (integer): Number of results to rank per search term per backend.
- `recency`: Applied to every term. Only results from the past "day", "week", "month" or "year".
- `region`: Region-language code like "us-en", "uk-en" or "de-de". Default: ddgs's own (us-en).
- `search_terms` (array, required): 2-5 specific, related search queries covering different angles.                       Example: ["postgres query planner", "postgres index types", "EXPLAIN ANALYZE tutorial"]
- `top_k_per_term` (integer): Number of top-ranked results to keep per search term per backend.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/nkapila6-mcpsurfr/ghcr-io-nkapila6-mcpsurfr#diagnostics

## Score history

- 2026-11-05: 38
- 2026-11-04: 38
- 2026-11-03: 38
- 2026-11-02: 38
- 2026-11-01: 38
- 2026-10-31: 38
- 2026-10-30: 38
- 2026-10-29: 38
- 2026-10-28: 41
- 2026-10-27: 40
- 2026-10-26: 40
- 2026-10-25: 39
- 2026-10-24: 39
- 2026-10-23: 38

## Common questions

### What is the mcpsurfr MCP server?

mcpsurfr is an MCP server listed in the public MCP registry as io.github.nkapila6/mcpsurfr. Local web search with multi-engine deep research and on-device re-ranking. No API keys. This page covers its container image (ghcr.io/nkapila6/mcpsurfr).

### Is the mcpsurfr MCP server safe to use?

mcpsurfr scores 38 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 mcpsurfr MCP server expose?

mcpsurfr exposes 4 tools: rag_search_ddgs, search, read_url, deep_research. Their descriptions and schemas cost roughly 1,367 tokens of context every time the server is loaded.

### Is the mcpsurfr MCP server still maintained?

mcpsurfr is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the mcpsurfr MCP server?

VerifyMCP ran 12 checks on mcpsurfr, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about mcpsurfr: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/nkapila6/mcpsurfr
- Repository: https://github.com/nkapila6/mcpsurfr
- Changelog RSS feed: https://verifymcp.io/servers/nkapila6-mcpsurfr/ghcr-io-nkapila6-mcpsurfr.xml
- Changelog JSON feed: https://verifymcp.io/servers/nkapila6-mcpsurfr/ghcr-io-nkapila6-mcpsurfr/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/nkapila6-mcpsurfr/ghcr-io-nkapila6-mcpsurfr.json
- HTML version of this page: https://verifymcp.io/servers/nkapila6-mcpsurfr/ghcr-io-nkapila6-mcpsurfr