io.github.pierreb4/seven-dpt-mcp
NPM · SEVEN-DPT-MCP · SCANNED AUG 3
Feynman's twelve-problems method as an MCP server: dormant problems + an evoke loop for new tricks.
Available components
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. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability41
- AI-judged instruction clarity (fair).Partial
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · seven-dpt-mcp
claude mcp add pierreb4-seven-dpt-mcp -- npx -y seven-dpt-mcp
codex mcp add pierreb4-seven-dpt-mcp -- npx -y seven-dpt-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pierreb4-seven-dpt-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"seven-dpt-mcp"
],
"enabled": true
}
}
} openclaw mcp add pierreb4-seven-dpt-mcp --command npx --arg -y --arg seven-dpt-mcp
mcp_servers:
pierreb4-seven-dpt-mcp:
command: "npx"
args: ["-y", "seven-dpt-mcp"] {
"mcpServers": {
"pierreb4-seven-dpt-mcp": {
"command": "npx",
"args": [
"-y",
"seven-dpt-mcp"
]
}
}
} 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.
- 3 Aug 26 +24
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Schema quality: unverified → fair ▲ functional
- License: unverified → pass ▲ functional
- Licence: Apache-2.0 functional
- 2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Jul 26 +13
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −42
- Known CVEs: partial → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- License: pass → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Licence: Apache-2.0 functional
- 28 Jul 26 +39
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- 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 functional
- 27 Jul 26 9
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
add_problem Add a favorite problem ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Short name for the problem |
No output schema declared.
No examples provided.
capture_spark Capture a spark (approach motivation) ~308
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The candidate solution or insight |
| nextStep | string | yes | 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 | yes | Which problem this advances |
| trick | string | yes | 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. |
No output schema declared.
No examples provided.
evoke Evoke — test a new trick against all your problems ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | — | Optional: which project you're in right now |
| trick | string | yes | The new trick / result / insight / observation to test against your problems |
No output schema declared.
No examples provided.
get_problem Get a problem and its history ~49
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Problem id |
No output schema declared.
No examples provided.
list_problems List your favorite problems ~39
Show your global set of long-running problems. Defaults to open ones only.
| Name | Type | Req | Description |
|---|---|---|---|
| includeClosed | boolean | — | Also show solved/retired problems |
No output schema declared.
No examples provided.
update_problem Update / retire / solve a problem ~256
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.
| Name | Type | Req | Description |
|---|---|---|---|
| framing | string | — | New framing (the 'instance of what?' reframe) |
| id | integer | yes | 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… |
No output schema declared.
No examples provided.
update_spark Record a spark's outcome ~293
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
wake_status Wake-condition ledger ~57
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.