io.github.dingdawg/agent-spend-policy-mcp
NPM · @DINGDAWG/AGENT-SPEND-POLICY-MCP · SCANNED AUG 8
Local agent spend-policy checks. No funds, keys, payment authority, or network access.
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 & Transparency48
- 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 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability40
- AI-judged instruction clarity (poor).Fail
- Tool/resource definitions use about 80 tokens (~80/item across 1 items; 1 tools + 0 resources), lean.Pass
- 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 · @dingdawg/agent-spend-policy-mcp
claude mcp add dingdawg-agent-spend-policy-mcp -- npx -y @dingdawg/agent-spend-policy-mcp
codex mcp add dingdawg-agent-spend-policy-mcp -- npx -y @dingdawg/agent-spend-policy-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dingdawg-agent-spend-policy-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@dingdawg/agent-spend-policy-mcp"
],
"enabled": true
}
}
} openclaw mcp add dingdawg-agent-spend-policy-mcp --command npx --arg -y --arg @dingdawg/agent-spend-policy-mcp
mcp_servers:
dingdawg-agent-spend-policy-mcp:
command: "npx"
args: ["-y", "@dingdawg/agent-spend-policy-mcp"] {
"mcpServers": {
"dingdawg-agent-spend-policy-mcp": {
"command": "npx",
"args": [
"-y",
"@dingdawg/agent-spend-policy-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.
- 8 Aug 26 +3
- Known CVEs: partial → pass ▲ security
- Dependency health: partial → 0.85 functional
- 7 Aug 26 +1
- Security disclosure: fail → pass ▲ functional
- 6 Aug 26 +20
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: poor functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 0 functional
- 5 Aug 26 35
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 8 Aug 2026 · Analysed npm/@dingdawg/[email protected]
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.
evaluate_spend_policy Evaluate agent spend-policy eligibility ~80
Deterministically evaluates a proposed action against caller-supplied policy. This is local policy evidence only: it never authorizes, signs, sends, settles, custodies, or records a payment.
| Name | Type | Req | Description |
|---|---|---|---|
| action | object | yes | – |
| alreadySpentMicros | – | yes | – |
| evaluationTime | string | yes | – |
| policy | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| outcome | string | yes | – |
| reasonCode | string | yes | – |
No examples provided.