com.theaslangroupllc.pulse/agent-wallet
NPM · @PULSENETWORK/MCP
Local agent wallet + 900 pay-per-call data APIs — free discovery, x402 USDC, code-level spend caps
Available components
Last scanned (20 hours ago)
Scores higher than 66% of npm 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 112 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 100 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 376 tokens (~75/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 +1
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.97 functional
- 15 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 14 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 11 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 −2
- Stability: pass → 0.90 functional
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 21 Nov 2026 · Analysed npm/@pulsenetwork/mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 112 packages
| Packages resolved | 112 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
pulse_balance ~45
FREE — the local wallet address and its USDC balance on Base. If the balance is 0, paid calls will fail: give the user the address so they can fund it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pulse_call ~145
PAID — call a PulseNetwork endpoint, paying its listed price in USDC on Base from the local wallet. Spend caps are enforced in code before signing; if a call is blocked by a guardrail, do NOT retry or attempt to route around it — tell the user. Only *.theaslangroupllc.com hosts are payable. Quote the price to the user before calling when the request is theirs.
| Name | Type | Req | Description |
|---|---|---|---|
| params | object | – | Query parameters for the endpoint |
| path | string | yes | Endpoint path from pulse_discover, e.g. "/api/rights/check" |
| vertical | string | yes | Vertical id from pulse_discover, e.g. "travelpulse" |
No output schema declared.
No examples provided.
pulse_discover ~107
FREE — search the PulseNetwork catalog (74 verticals, ~900 endpoints). Returns matching endpoints with price, params, and description. Always discover before calling; prefer the cheapest endpoint that answers the question.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 20) |
| query | string | – | Keywords, e.g. "flight compensation", "token safety", "clinical trials" |
| vertical | string | – | Restrict to one vertical id, e.g. "cryptopulse" |
No output schema declared.
No examples provided.
pulse_guardrail ~44
FREE — show the active spend caps. Caps can only be changed by the USER editing the config file (or env vars) — there is deliberately no tool to raise them.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pulse_report ~35
FREE — local spend report from this wallet's ledger.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look-back window in days (default 7) |
No output schema declared.
No examples provided.
How do I install the com.theaslangroupllc.pulse/agent-wallet MCP server?
com.theaslangroupllc.pulse/agent-wallet runs locally as an npm package, launched with npx -y @pulsenetwork/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pulsenetwork/mcp
claude mcp add com-theaslangroupllc-pulse-agent-wallet -- npx -y @pulsenetwork/mcp
What is the com.theaslangroupllc.pulse/agent-wallet MCP server?
com.theaslangroupllc.pulse/agent-wallet is an MCP server listed in the public MCP registry as com.theaslangroupllc.pulse/agent-wallet. Local agent wallet + 900 pay-per-call data APIs, free discovery, x402 USDC, code-level spend caps. This page covers its npm package (@pulsenetwork/mcp).
Is the com.theaslangroupllc.pulse/agent-wallet MCP server safe to use?
com.theaslangroupllc.pulse/agent-wallet scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 com.theaslangroupllc.pulse/agent-wallet MCP server expose?
com.theaslangroupllc.pulse/agent-wallet exposes 5 tools: pulse_discover, pulse_call, pulse_balance, pulse_report, pulse_guardrail. Their descriptions and schemas cost roughly 376 tokens of context every time the server is loaded.
Is the com.theaslangroupllc.pulse/agent-wallet MCP server still maintained?
com.theaslangroupllc.pulse/agent-wallet is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.theaslangroupllc.pulse/agent-wallet MCP server under?
com.theaslangroupllc.pulse/agent-wallet declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the com.theaslangroupllc.pulse/agent-wallet MCP server?
VerifyMCP ran 16 checks on com.theaslangroupllc.pulse/agent-wallet, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.