io.github.dingdawg/agent-spend-policy-mcp
Local agent spend-policy checks. No funds, keys, payment authority, or network access.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
@dingdawg/agent-spend-policy-mcpclaude mcp add agent-spend-policy-mcp -- npx -y @dingdawg/agent-spend-policy-mcp@0.1.1
{
"mcpServers": {
"agent-spend-policy-mcp": {
"command": "npx",
"args": [
"-y",
"@dingdawg/agent-spend-policy-mcp@0.1.1"
]
}
}
}
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
DingDawg Agent Spend Policy MCP
A small, local MCP server that deterministically evaluates whether a proposed agent spend action matches a supplied policy.
It returns one of ELIGIBLE, DENY, or STEP_UP, with a stable reason code.
ELIGIBLE is local policy evidence only. It is not payment authorization.
Safety boundary
This package does not hold funds, private keys, payment credentials, customer data, or settlement authority. It does not sign, send, settle, custody, or record payments. It makes no network requests.
A production payment adapter needs separate, independently verified controls for authenticated policy/action provenance, canonical payload hashing, durable atomic budget reservation and replay protection, customer-controlled signing, rail validation, and settlement reconciliation.
Install
npx -y @dingdawg/agent-spend-policy-mcp
Configure it as a local stdio MCP server:
{
"mcpServers": {
"dingdawg-agent-spend-policy": {
"command": "npx",
"args": ["-y", "@dingdawg/agent-spend-policy-mcp"]
}
}
}
Tool
evaluate_spend_policy accepts an evaluation time, a policy, a proposed action,
and the already-spent amount. All money is passed as integer micro-unit strings,
never JavaScript floating-point numbers.
The caller supplies the clock and already-spent value; therefore this tool is safe for dry runs and local evidence, not a replacement for a trusted payment or accounting system.
Agent contract
The versioned machine-readable contract is
capabilities.json. It describes the only tool this
package exposes, its required inputs, its three possible outcomes, and its
non-negotiable safety boundary.
- Transport: local stdio MCP
- Tool:
evaluate_spend_policy - Required inputs:
evaluationTime,policy,action, andalreadySpentMicros - Outputs:
ELIGIBLE,DENY, orSTEP_UP, each with a stable reason code - Side effects: none
- Credentials, payment execution, custody, signing, settlement, and network access: not supported
The manifest is package-source evidence for this release, not a promise of a
hosted agent-discovery endpoint. ELIGIBLE remains local policy evidence only,
not payment authorization.
Development
npm install
npm test
npm run pack:check
Questions fréquentes
Qu'est-ce que io.github.dingdawg/agent-spend-policy-mcp ?
Local agent spend-policy checks. No funds, keys, payment authority, or network access.
Comment installer io.github.dingdawg/agent-spend-policy-mcp ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add agent-spend-policy-mcp -- npx -y @dingdawg/agent-spend-policy-mcp@0.1.1. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour io.github.dingdawg/agent-spend-policy-mcp ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
io.github.dingdawg/agent-spend-policy-mcp est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient io.github.dingdawg/agent-spend-policy-mcp ?
Il est publié par DingDawg. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.