Eclipse Agent Wallet MCP
OCI · GHCR.IO/CYAN-ECLIPSE-TECHNOLOGIES-LLC/AGENT-WALLET-MCP
Policy-scoped agent wallet: caps, recipient allowlist, human approvals, kill switch, audit trail.
Available components
Last scanned (4 hours ago)
Scores higher than 37% of OCI servers
Category Finance and Payments
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 → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 502 tokens (~50/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pay" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.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.
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 31
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 5 Nov 2026 · Analysed oci/ghcr.io/cyan-eclipse-technologies-llc/agent-wallet-mcp@2842d69a363c4412a4c1347878fd27b7ca9d9aeb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
approve_payment ~27
Owner approves a pending payment request; it executes immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
No output schema declared.
No examples provided.
audit_log ~49
The append-only audit trail: policy grants, payments, rejections, approvals, revocations. The evidence of what was authorized.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| wallet_id | string | – | – |
No output schema declared.
No examples provided.
check_payment ~57
Dry-run a payment against the policy. Returns allow / approve / deny with the reason. Agents should call this before pay.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usdc | string | yes | – |
| to | string | yes | – |
| wallet_id | string | yes | – |
No output schema declared.
No examples provided.
create_wallet ~45
Create a sandbox agent wallet owned by a named human. A wallet cannot spend until its owner grants a policy.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | – |
| owner_id | string | yes | – |
No output schema declared.
No examples provided.
deny_payment ~23
Owner denies a pending payment request.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
No output schema declared.
No examples provided.
fund_wallet ~46
SANDBOX faucet: add simulated test USDC so demos and tests can run. Not real money.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usdc | string | yes | – |
| wallet_id | string | yes | – |
No output schema declared.
No examples provided.
get_wallet ~30
Wallet summary: balance, frozen state, spend today, active policy.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet_id | string | yes | – |
No output schema declared.
No examples provided.
pay ~69
Execute a payment if it is inside the granted scope. Outside scope: rejected, or routed to the human approval queue if it only exceeds the approval threshold.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usdc | string | yes | – |
| memo | string | – | – |
| to | string | yes | – |
| wallet_id | string | yes | – |
No output schema declared.
No examples provided.
revoke ~46
KILL SWITCH: freeze the wallet instantly. All spending stops; the revocation is timestamped in the audit log.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | – |
| wallet_id | string | yes | – |
No output schema declared.
No examples provided.
set_policy ~110
The owner grants the spending scope: per-transaction cap, daily cap, approval threshold, recipient allowlist, expiry, purpose. Returns a plain-language liability receipt. Responsibility follows this scope.
| Name | Type | Req | Description |
|---|---|---|---|
| allowlist | array | – | – |
| approval_above_usdc | string | – | – |
| daily_cap_usdc | string | yes | – |
| expires_in_days | integer | – | – |
| per_tx_cap_usdc | string | yes | – |
| purpose | string | – | – |
| wallet_id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Eclipse Agent Wallet MCP server?
Eclipse Agent Wallet MCP runs locally as a container image, launched with docker run --rm -i -e AGENT_WALLET_LEDGER ghcr.io/cyan-eclipse-technologies-llc/agent-wallet-mcp:2842d69a363c4412a4c1347878fd27b7ca9d9aeb. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/cyan-eclipse-technologies-llc/agent-wallet-mcp
claude mcp add cyan-eclipse-technologies-llc-agent-wallet -- docker run --rm -i -e AGENT_WALLET_LEDGER ghcr.io/cyan-eclipse-technologies-llc/agent-wallet-mcp:2842d69a363c4412a4c1347878fd27b7ca9d9aeb
This image reads AGENT_WALLET_LEDGER. Set it in your client's env block for this server; docker run -e passes it through to the container.
What is the Eclipse Agent Wallet MCP server?
Eclipse Agent Wallet MCP is listed in the public MCP registry as io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/agent-wallet. Policy-scoped agent wallet: caps, recipient allowlist, human approvals, kill switch, audit trail. This page covers its container image (ghcr.io/cyan-eclipse-technologies-llc/agent-wallet-mcp).
Is the Eclipse Agent Wallet MCP server safe to use?
Eclipse Agent Wallet MCP scores 35 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Eclipse Agent Wallet MCP server expose?
Eclipse Agent Wallet MCP exposes 10 tools: create_wallet, get_wallet, set_policy, fund_wallet, check_payment, and 5 more. Their descriptions and schemas cost roughly 502 tokens of context every time the server is loaded.
Is the Eclipse Agent Wallet MCP server still maintained?
Eclipse Agent Wallet MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.