# io.github.pierreb4/seven-dpt-mcp (npm · seven-dpt-mcp)

Feynman's twelve-problems method as an MCP server: dormant problems + an evoke loop for new tricks.

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

## Components

- npm · `seven-dpt-mcp`: 58/100 (this document), [markdown](https://verifymcp.io/servers/pierreb4-seven-dpt-mcp/seven-dpt-mcp.md), [page](https://verifymcp.io/servers/pierreb4-seven-dpt-mcp/seven-dpt-mcp)

## Channel facts

- Registry: `npm`
- Package: `seven-dpt-mcp`
- Version: `0.1.4`
- 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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 41/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 1237 tokens (~154/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 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

### Claude

```bash
claude mcp add pierreb4-seven-dpt-mcp -- npx -y seven-dpt-mcp
```

### Codex

```bash
codex mcp add pierreb4-seven-dpt-mcp -- npx -y seven-dpt-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pierreb4-seven-dpt-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "seven-dpt-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pierreb4-seven-dpt-mcp --command npx --arg -y --arg seven-dpt-mcp
```

### Hermes

```yaml
mcp_servers:
  pierreb4-seven-dpt-mcp:
    command: "npx"
    args: ["-y", "seven-dpt-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "pierreb4-seven-dpt-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "seven-dpt-mcp"
      ]
    }
  }
}
```

## 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-03 (score 58, +24)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Schema quality: unverified → fair
- [functional improvement] License: unverified → pass
- [functional] Licence: Apache-2.0

### 2026-08-02 (score 34, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-07-31 (score 19, +13)

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

### 2026-07-30 (score 6, −42)

- [security regression] Known CVEs: partial → unverified
- [security regression] Provenance: fail → unverified
- [security regression] Install scripts: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] License: pass → unverified
- [functional regression] Dependency health: partial → unverified
- [functional regression] Maintenance: pass → unverified
- [functional] Licence: Apache-2.0

### 2026-07-28 (score 48, +39)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] License: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: unverified
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: fail
- [functional] Licence: Apache-2.0

### 2026-07-27 (score 9)

First indexed and scored.

## MCP tools (8)

### `add_problem` (~143 tokens)

Add a favorite problem

Add a long-running problem to your global Feynman set — the ~dozen you keep dormant in mind across every project. Keep the active set small; that constraint is the method.

Input parameters:

- `origin` (string): Where it came from (project, context)
- `overCap` (boolean): Override the ~twelve-problem cap for this add (only after weighing a retire/merge first — the cap is the method)
- `statement` (string): Fuller description / what 'solved' would look like
- `tags` (array): Freeform tags, e.g. domains or project names
- `title` (string, required): Short name for the problem

### `update_problem` (~256 tokens)

Update / retire / solve a problem

Edit a problem or move it out of the active set — the retire/solve/merge loop that keeps the set near twelve. When closing (status solved/retired), write a resolution saying WHY plus, for a retirement, the explicit RE-OPEN trigger: a retired problem is parked with a wake condition, not deleted. A merge is a retirement whose resolution names the absorbing problem. Reopen later by setting status back to open.

Input parameters:

- `framing` (string): New framing (the 'instance of what?' reframe)
- `id` (integer, required): Problem id
- `resolution` (string): Why it left the open set + the re-open trigger in prose (write one whenever closing; for a merge, name the absorbing problem)
- `statement` (string): New fuller description
- `status` (string): open (reopen) | solved | retired
- `tags` (array): Replace the tag list
- `title` (string): New short name
- `wakeCondition`: Structured, COMPUTABLE re-open trigger — the machine half of the resolution prose. The ambient digest evaluates it every session and surfaces ripeness (see wake_status). Parked problems only; pass nu…

### `list_problems` (~39 tokens)

List your favorite problems

Show your global set of long-running problems. Defaults to open ones only.

Input parameters:

- `includeClosed` (boolean): Also show solved/retired problems

### `get_problem` (~49 tokens)

Get a problem and its history

Show one problem plus every spark (idea + next step + outcome) captured against it — the long-running memory that makes a stuck issue accumulate progress across sessions.

Input parameters:

- `id` (integer, required): Problem id

### `evoke` (~92 tokens)

Evoke — test a new trick against all your problems

The core loop. Give it a trick, result, idea, or observation you just encountered. Returns your open problems plus a scaffold that walks you through evocation -> transcendence -> approach. Call this whenever you learn something that might generalize.

Input parameters:

- `project` (string): Optional: which project you're in right now
- `trick` (string, required): The new trick / result / insight / observation to test against your problems

### `capture_spark` (~308 tokens)

Capture a spark (approach motivation)

Persist a candidate solution plus a concrete next step against a problem — the output of a successful evocation. This is the memory that lets long-running issues progress across sessions.

Input parameters:

- `cost` (number): Legacy alias for costToOpen at capture time (kept for older callers). Prefer costToOpen.
- `costToOpen` (number): Rough EXPECTED effort to chase this spark to a verdict, on a consistent scale (e.g. minutes, or a 1-5 effort score). This is the Pandora 'cost to open' the spend-policy ranks on — the a-priori estima…
- `idea` (string, required): The candidate solution or insight
- `nextStep` (string, required): ONE concrete next experiment or action
- `prior` (number): Your honest stated probability (0-1) at capture that chasing this spark yields a worked outcome. IMMUTABLE afterwards — update_spark cannot revise it — so stated credences can later be calibrated aga…
- `problemId` (integer, required): Which problem this advances
- `trick` (string, required): The trick / stimulus that evoked it
- `wakeCondition` (object): Optional: park this spark behind a computable gate from birth (captured now, actionable when X) — the ambient digest evaluates it and surfaces ripeness.

### `update_spark` (~293 tokens)

Record a spark's outcome

Record what happened when you acted on a spark — an outcome note, a new status (tried / worked / failed), and ideally the cost (effort spent) and value (graded payoff). LOG FAILURES TOO: 'most bets fail' is the premise of problem #2, so failed and zero-value outcomes are exactly the signal a spend-policy is learned from — recording only wins makes the history unusable. This outcome history is what lets the system learn when surfacing a dormant problem is worth the attention.

Input parameters:

- `cost` (number): ACTUAL effort spent chasing it to a verdict (same scale as capture's estimate).
- `costToOpen` (number): Revise the FORWARD cost-to-open estimate (uncommon — normally set once at capture). Resolution never changes it automatically.
- `id` (integer, required): Spark id
- `outcome` (string): What happened when you tried it
- `status` (string): New status for the spark
- `value` (number): Graded payoff of the outcome: 0 if it failed or yielded nothing, higher for bigger wins (heavy-tailed). The reward signal the budget policy is fit on — log it for failures too.
- `wakeCondition`: Park a HOLD/STOPped spark with its computable re-run trigger — the digest owns the wait (see wake_status). Pass null to clear; resolving worked/failed auto-clears.

### `wake_status` (~57 tokens)

Wake-condition ledger

Evaluate every parked problem/spark's wakeCondition right now: ripeness, progress, and current/target echoes per atom. Read-only. The ambient digest shows the compact version at session start; this is the full view for curation passes.

## Diagnostics

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

## Score history

- 2026-08-03: 58
- 2026-08-02: 34
- 2026-08-01: 19
- 2026-07-31: 19
- 2026-07-30: 6
- 2026-07-28: 48
- 2026-07-27: 9

## Links

- npm package: https://www.npmjs.com/package/seven-dpt-mcp
- Socket report: https://socket.dev/npm/package/seven-dpt-mcp
- Repository: https://github.com/pierreb4/seven-dpt-mcp
- Changelog RSS feed: https://verifymcp.io/servers/pierreb4-seven-dpt-mcp/seven-dpt-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/pierreb4-seven-dpt-mcp/seven-dpt-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/pierreb4-seven-dpt-mcp/seven-dpt-mcp