ThoughtProof
NPM · THOUGHTPROOF-MCP · SCANNED AUG 20
Pre-action gate: verify before pay/trade/write/deploy. execute=true only on ALLOW.
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 96 dependencies flagged as unhealthy. 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 (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1066 tokens (~213/item across 5 items; 5 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage60
- 40% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 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
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 · thoughtproof-mcp
claude mcp add thoughtproof-thoughtproof-mcp -- npx -y thoughtproof-mcp
codex mcp add thoughtproof-thoughtproof-mcp -- npx -y thoughtproof-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"thoughtproof-thoughtproof-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"thoughtproof-mcp"
],
"enabled": true
}
}
} openclaw mcp add thoughtproof-thoughtproof-mcp --command npx --arg -y --arg thoughtproof-mcp
mcp_servers:
thoughtproof-thoughtproof-mcp:
command: "npx"
args: ["-y", "thoughtproof-mcp"] {
"mcpServers": {
"thoughtproof-thoughtproof-mcp": {
"command": "npx",
"args": [
"-y",
"thoughtproof-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.
- 20 Aug 26 +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.
- 19 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Aug 26 +1
- Malware scan: unverified → pass ▲ security
- Schema quality: 169 → 213 ▼ functional
- Tool coverage: 25% → 40% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.3.1 → 0.3.2 functional
- 17 Aug 26 47
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 20 Aug 2026 · Analysed npm/thoughtproof-mcp@0.3.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
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.
check_agent_score ~43
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | The agent ID to look up (e.g. 'agent_abc123xyz') |
| domain | string | – | Optional domain filter for the score |
No output schema declared.
No examples provided.
verify_before_action ~350
ThoughtProof pre-action verification gate: verify before the agent pays, trades, writes, or deploys. Call this BEFORE any consequential tool (payment, trade, transfer, publish, delete, deploy, irreversible write). Returns { verdict: ALLOW|BLOCK|UNCERTAIN|…, execute: boolean, objections, receipt_id, surface, axes?, recommendation }. execute is true ONLY on ALLOW — on any other result do NOT execute (soft fail-closed; host must honor execute=false). Routes internally to DQL (spend/checkout) or Sentinel (irreversible exit). Camera mandate: you must NOT put the overshoot or constraint violation in proposed_action or reasoning (for example, do not write "price is above the cap"). Put the user goal in mandate, the action you are about to take in proposed_action, and your plan in reasoning — the verifier must find the mismatch. Replan = new call = new receipt. Aliases: verify_decision, verify_before_action, verify_before_act.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional extra evidence, tool outputs, or prior turns. |
| mandate | string | yes | The user's stated goal or instruction the agent is acting on. |
| mode | string | – | Routing override. auto (default) picks DQL for spend/checkout language and Sentinel for high-blast irreversible exits; unsure → DQL. Explicit mode wins. |
| proposed_action | string | yes | What the agent is about to do (pay/trade/write/deploy/…). Do not include the overshoot or constraint violation here. |
| reasoning | string | yes | The agent's own plan or reasoning. Do not include the overshoot; the verifier has to find the mismatch. |
No output schema declared.
No examples provided.
verify_claim ~116
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | The claim or AI-generated reasoning to verify. Can be a statement, decision, analysis, or any text that needs adversarial verification. |
| domain | string | – | Domain context for specialized verification. Default: general |
| speed | string | – | Verification depth. fast=$0.008 (2 models), standard=$0.02 (4 models), deep=$0.08 (5+ models). Default: standard |
| stakeLevel | string | – | Risk level — higher stakes trigger more thorough verification. Default: medium |
No output schema declared.
No examples provided.
verify_decision ~350
ThoughtProof pre-action verification gate: verify before the agent pays, trades, writes, or deploys. Call this BEFORE any consequential tool (payment, trade, transfer, publish, delete, deploy, irreversible write). Returns { verdict: ALLOW|BLOCK|UNCERTAIN|…, execute: boolean, objections, receipt_id, surface, axes?, recommendation }. execute is true ONLY on ALLOW — on any other result do NOT execute (soft fail-closed; host must honor execute=false). Routes internally to DQL (spend/checkout) or Sentinel (irreversible exit). Camera mandate: you must NOT put the overshoot or constraint violation in proposed_action or reasoning (for example, do not write "price is above the cap"). Put the user goal in mandate, the action you are about to take in proposed_action, and your plan in reasoning — the verifier must find the mismatch. Replan = new call = new receipt. Aliases: verify_decision, verify_before_action, verify_before_act.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional extra evidence, tool outputs, or prior turns. |
| mandate | string | yes | The user's stated goal or instruction the agent is acting on. |
| mode | string | – | Routing override. auto (default) picks DQL for spend/checkout language and Sentinel for high-blast irreversible exits; unsure → DQL. Explicit mode wins. |
| proposed_action | string | yes | What the agent is about to do (pay/trade/write/deploy/…). Do not include the overshoot or constraint violation here. |
| reasoning | string | yes | The agent's own plan or reasoning. Do not include the overshoot; the verifier has to find the mismatch. |
No output schema declared.
No examples provided.
verify_trade ~207
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | The action the agent intends to execute, e.g. 'open 5x long BTC, 8000 USDC margin' or 'swap 10 ETH for USDC'. |
| reasoning | string | yes | The full reasoning chain that produced the decision — the actual chain of thought, not a summary. This is what ThoughtProof verifies. |
| situation | string | – | Optional market/context snapshot WITHOUT the chosen action. Lets the adversarial panel form an independent view before seeing the decision (stronger verification). |
| stakeLevel | string | – | Stake level — drives the verdict threshold. Higher stake demands higher reasoning soundness to ALLOW: the SAME decision can ALLOW at low stake and BLOCK/UNCERTAIN at critical stake. Default 'high' (s… |
| thesis | string | yes | The agent's one-line decisive rationale for the action. |
No output schema declared.
No examples provided.