Ha Tang docs and API for agents: email, VietQR payments, e-invoices, support inbox (Vietnam).
Nothing to run from here
NostrPulse is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
trust score
10
tools declared
local
runs on your machine
—
downloads a day
What it does
Autonomous payment & Web-of-Trust anti-Sybil layer for AI agents via Nostr & Cashu (NIP-61 NutZaps).
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user nostrpulse-mcp '--' npx -y nostrpulse-mcp
# 2 — ask your agent for something these tools do
# pay_lightning_nwc, audit_cashu_mint, route_cashu_mint and 7 more
NostrPulse costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PHAll 1 server
phonguit221 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts NostrPulse as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user nostrpulse-mcp '--' npx -y nostrpulse-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Pay a BOLT-11 Lightning invoice via NIP-47 Nostr Wallet Connect.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoice | string | yes | BOLT-11 Lightning invoice. |
| nwcUri | string | no | Explicit NWC connection URI (falls back to env NWC_CONNECTION_URI). |
| timeoutMs | integer | no | Timeout in milliseconds (default: 15000) |
| amountMsat | integer | no | Optional amount in millisatoshis for amountless invoices |
Audit Cashu mint health, NUT-06 status, and counterparty risk score.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mintUrl | string | yes | Target Cashu mint URL (e.g., https://mint.minibits.cash/Bitcoin). |
| forceRefresh | boolean | no | Bypass in-memory audit cache and perform fresh live probe (default: false) |
Route to the highest-trust, lowest-latency Cashu mint for a payment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amountSats | integer | no | Intended payment or minting amount in Satoshis |
| preferredMint | string | no | Optional preferred mint URL to prioritize if verified and healthy |
| minTrustScore | integer | no | Minimum WoT Trust Score required to pass the security gate (default: 45) |
Get the autonomous agent's Nostr public identity and npub.
No parameter schema on file.
Check current AI agent spending budget, daily limits, and remaining satoshis.
No parameter schema on file.
Retrieve agent telemetry metrics, rolling spend volume, and security events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| timeframeHours | integer | no | Rolling window in hours (default: 24) |
| limit | integer | no | Maximum number of telemetry events to retrieve (default: 20) |
Verify anti-Sybil Trust Score (0-100) and Web-of-Trust distance for a Nostr pubkey.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pubkey | string | yes | Target Nostr public key in 64-char hex or npub format |
Send an eCash NutZap payment (NIP-61) to a Nostr recipient under guardrail limits.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| recipient | string | yes | Recipient Nostr public key (64-char hex or bech32 npub) |
| amountSats | integer | yes | Amount in satoshis to pay |
| cashuToken | string | no | Optional Cashu eCash token string; if omitted, generates a mint quote invoice |
| mintUrl | string | no | Optional target Cashu mint URL |
| comment | string | no | Optional payment message memo |
Dispatch a NIP-90 DVM analytics computation task across Nostr relays with local fallback.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prompt | string | yes | Target Nostr public key or computation query |
| category | string | no | Task category: 'zap-analytics', 'reputation', or 'trust-score' (default: 'trust-score') |
| timeframe | string | no | Historical timeframe: 'all-time', '1y', or '30d' (default: 'all-time') |
| bidSats | integer | no | Bid fee in satoshis (default: 5) |
| timeoutMs | integer | no | Timeout in milliseconds (default: 3500) |
Pay a BOLT-11 Lightning invoice via NIP-47 Nostr Wallet Connect (alias).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoice | string | yes | BOLT-11 Lightning invoice |
| nwcUri | string | no | Optional NWC connection URI (falls back to env NWC_CONNECTION_URI) |
| timeoutMs | integer | no | Timeout in milliseconds (default: 15000) |
| amountMsat | integer | no | Optional amount in millisatoshis for amountless invoices |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install NostrPulse or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 96 / 100
Release 1.3.1 · scanned 5 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings3 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest00ea90290aa30f8a98b942ba2955afab4cbf92ac0d8c6199f57c5292dbf04d78
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (10 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
1 of the 10 recovered tools are registered only when isToolAllowed("check_trust_score") holds (dist/mcp-entry.js:905) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 10 recovered tools are registered only when isToolAllowed("pay_cashu_nutzap") holds (dist/mcp-entry.js:1012) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 10 recovered tools are registered only when isToolAllowed("request_nip90_job") holds (dist/mcp-entry.js:1212) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 10 recovered tools are registered only when isToolAllowed("pay_lightning_nwc") holds (dist/mcp-entry.js:1417) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 10 recovered tools are registered only when activeProfile === "full" && isToolAllowed("pay_with_nwc") holds (dist/mcp-entry.js:1425) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 10 recovered tools are registered only when isToolAllowed("audit_cashu_mint") holds (dist/mcp-entry.js:1433) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 10 recovered tools are registered only when isToolAllowed("route_cashu_mint") holds (dist/mcp-entry.js:1473) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 10 recovered tools are registered only when isToolAllowed("get_agent_identity") holds (dist/mcp-entry.js:1519) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 10 recovered tools are registered only when isToolAllowed("get_spending_guardrails") holds (dist/mcp-entry.js:1559) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 10 recovered tools are registered only when isToolAllowed("get_agent_telemetry") holds (dist/mcp-entry.js:1590) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
No tool is registered unconditionally · (1) 1 only when isToolAllowed("check_trust_score") holds (dist/mcp-entry.js:905) · (2) 1 only when isToolAllowed("pay_cashu_nutzap") holds (dist/mcp-entry.js:1012) · (3) 1 only when isToolAllowed("request_nip90_job") holds (dist/mcp-entry.js:1212) · (4) 1 only when isToolAllowed("pay_lightning_nwc") holds (dist/mcp-entry.js:1417) · (5) 1 only when activeProfile === "full" && isToolAllowed("pay_with_nwc") holds (dist/mcp-entry.js:1425) · (6) 1 only when isToolAllowed("audit_cashu_mint") holds (dist/mcp-entry.js:1433) · (7) 1 only when isToolAllowed("route_cashu_mint") holds (dist/mcp-entry.js:1473) · (8) 1 only when isToolAllowed("get_agent_identity") holds (dist/mcp-entry.js:1519) · (9) 1 only when isToolAllowed("get_spending_guardrails") holds (dist/mcp-entry.js:1559) · (10) 1 only when isToolAllowed("get_agent_telemetry") holds (dist/mcp-entry.js:1590) — typically when a key or option is configured. All 10 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| check_trust_score conditional (1) | no tags | |
| pay_cashu_nutzap conditional (2) | external-sink | external-sink: parameter "recipient" |
| request_nip90_job conditional (3) | no tags | |
| pay_lightning_nwc conditional (4) | no tags | |
| pay_with_nwc conditional (5) | no tags | |
| audit_cashu_mint conditional (6) | no tags | |
| route_cashu_mint conditional (7) | no tags | |
| get_agent_identity conditional (8) | no tags | |
| get_spending_guardrails conditional (9) | no tags | |
| get_agent_telemetry conditional (10) | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest00ea90290aa30f8a
Scanned2026-11-05
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.3.1. Pin a release below and the command asks for exactly that one.
1.3.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish NostrPulse can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.