# Algorithm Finder (npm · @pipeworx/mcp-algorithm-finder)

Algorithm Finder MCP — which algorithm, data structure or technique fits a computational problem…

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 79/100, [markdown](https://verifymcp.io/servers/pipeworx-io-algorithm-finder/algorithm-finder-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-algorithm-finder/algorithm-finder-mcp)
- npm · `@pipeworx/mcp-algorithm-finder`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-algorithm-finder/pipeworx-mcp-algorithm-finder.md), [page](https://verifymcp.io/servers/pipeworx-io-algorithm-finder/pipeworx-mcp-algorithm-finder)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-algorithm-finder`
- Version: `0.2.1`
- 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**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-algorithm-finder).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1135 tokens (~283/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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.
- **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 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Algorithm Finder MCP server?

Algorithm Finder runs locally as an npm package, launched with npx -y @pipeworx/mcp-algorithm-finder. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-algorithm-finder -- npx -y @pipeworx/mcp-algorithm-finder
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-algorithm-finder": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-algorithm-finder"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-algorithm-finder": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-algorithm-finder"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-algorithm-finder -- npx -y @pipeworx/mcp-algorithm-finder
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-algorithm-finder": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-algorithm-finder"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-algorithm-finder --command npx --arg -y --arg @pipeworx/mcp-algorithm-finder
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-algorithm-finder:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-algorithm-finder"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-algorithm-finder": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-algorithm-finder"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-algorithm-finder -t stdio -c npx -a -y @pipeworx/mcp-algorithm-finder
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-algorithm-finder": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-algorithm-finder"
      ]
    }
  }
}
```

## 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-11-04 (score 81, +1)

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

### 2026-11-02 (score 80, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-01 (score 79, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-31 (score 79, +1)

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

### 2026-10-30 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (4)

### `algorithm_find` (~304 tokens)

Which algorithm, data structure or technique fits a computational problem. Describe the problem in words ("shortest route between two points with positive costs", "assign workers to jobs minimising cost", "find near-duplicate records", "schedule jobs to minimise lateness") and get the standard textbook methods (preconditions, worst-case / expected / amortized bounds, when to use and when not, alternatives, each fact cited to CLRS and other textbooks and to the NIST Dictionary of Algorithms and Data Structures), the open questions whose answers decide between them, Skiena Algorithm Repository problem pages, and recent research papers with dates from Hugging Face Papers and arXiv. want=common for textbook only, novel for recent papers only.

Input parameters:

- `constraints` (object): Optional facts about your instance (same keys as algorithm_compare, e.g. {"negative_weights": true}); textbook results that violate one move to the end and each result carries a per-constraint fit.
- `limit` (number): Max results per leg (1-25, default 8).
- `problem` (string, required): The computational problem in plain words, e.g. "all-pairs shortest paths", "approximate nearest neighbor search in high dimensions", "longest common subsequence of two strings".
- `since_year` (number): Earliest publication year for novel results (default: five years ago).
- `want` (string): common = textbook methods; novel = recent research papers; both (default).

### `algorithm_compare` (~466 tokens)

Compare candidate algorithms against the facts of YOUR instance and get a verdict. Pass method names (e.g. ["dijkstra","bellman-ford"]) or a problem description, plus constraints such as {"negative_weights": true, "query": "single_source"}, {"stable": true, "key_type": "integer_small_range"}, {"exact": false, "dimensions": "high"}, {"false_positives_ok": true, "dynamic": "fully_dynamic"}. Each candidate gets satisfied / violated / unknown per constraint, read from a curated table cited to textbooks, papers and library docs; unknown means the table records nothing and is never guessed. Returns the winner (or "conditional" with the unknowns named, or "none_compatible"), each candidate's bounds and when-not advice, and the decisive questions you have not answered that would change the choice.

Input parameters:

- `constraints` (object): Facts about your instance. Keys: negative_weights, negative_cycles, weighted, directed, acyclic, bipartite (booleans); graph_density sparse|dense; query single_pair|single_source|all_pairs; exact, wo…
- `names` (array): Method names or aliases to compare (2-10), e.g. ["dijkstra", "bellman-ford", "johnson"].
- `problem` (string): Instead of names: a problem description; the top curated candidates for it are compared.

### `algorithm_lookup` (~153 tokens)

One named algorithm, data structure or technique in full: what it solves, preconditions, complexity bounds with their kind (worst-case / expected / amortized) and textbook citations, when to use it and what to use instead, the NIST DADS dictionary entry (definition, relations, implementation links), the cp-algorithms article, Skiena Algorithm Repository problem pages, and which languages Rosetta Code has solutions in. Accepts short names ("Dijkstra", "KMP", "union-find") and aliases.

Input parameters:

- `name` (string, required): Method name or alias, e.g. "Dijkstra", "Floyd-Warshall", "red-black tree", "Hopcroft-Karp", "LRU".

### `algorithm_implementations` (~156 tokens)

Implementations of a named algorithm: the languages Rosetta Code has solutions in and, with language set, the source code of that solution (CC BY-SA 4.0, labelled educational), plus reference implementation links from the NIST DADS entry, the cp-algorithms article, and the Skiena Algorithm Repository implementation links for the problem.

Input parameters:

- `language` (string): Programming language as Rosetta Code names it, e.g. "Python", "C++", "Go", "Rust", "Java". Omit to list the languages available.
- `name` (string, required): Algorithm name, e.g. "Dijkstra's algorithm", "Floyd-Warshall algorithm", "Knuth-Morris-Pratt".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-algorithm-finder/pipeworx-mcp-algorithm-finder#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Algorithm Finder MCP server?

Algorithm Finder is an MCP server listed in the public MCP registry as io.github.pipeworx-io/algorithm-finder. Algorithm Finder MCP, which algorithm, data structure or technique fits a computational problem… This page covers its npm package (@pipeworx/mcp-algorithm-finder).

### Is the Algorithm Finder MCP server safe to use?

Algorithm Finder scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Algorithm Finder MCP server expose?

Algorithm Finder exposes 4 tools: algorithm_find, algorithm_compare, algorithm_lookup, algorithm_implementations. Their descriptions and schemas cost roughly 1,079 tokens of context every time the server is loaded.

### Is the Algorithm Finder MCP server still maintained?

Algorithm Finder 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 licence is the Algorithm Finder MCP server under?

Algorithm Finder declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-algorithm-finder
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-algorithm-finder
- Repository: https://github.com/pipeworx-io/mcp-algorithm-finder
- Website: https://pipeworx.io/packs/algorithm-finder
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-algorithm-finder/pipeworx-mcp-algorithm-finder.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-algorithm-finder/pipeworx-mcp-algorithm-finder.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-algorithm-finder/pipeworx-mcp-algorithm-finder