Pink Agentic AI Payments (by PinkWallet): lets Claude, ChatGPT, Cursor pay vendor invoices within company spending rules (budgets, caps, allow-lists, human approval). Sandbox preview, test money.
Loop 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.
What it does
15 pay-per-call Bitcoin and developer tools, paid in sats over Lightning (L402).
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http loop-mcp https://mcp.loopxxi.com/mcp
# 2 — ask your agent for something these tools do
# btc_price, btc_send_decision, lightning_address_resolve and 12 more
Loop costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http loop-mcp https://mcp.loopxxi.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
15 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.
Get the current Bitcoin price in USD and other major currencies. Source: mempool.space. Real-time.
No parameter schema on file.
Returns a composited send-or-wait recommendation for a Bitcoin transaction. Fetches live mempool and fee data, then outputs a machine-actionable verdict (SEND_NOW, WAIT, or URGENT_ONLY) with fee rates in sat/vB, mempool pressure level, and estimated savings if you wait. Ideal for agents that need a single decision call instead of parsing multiple raw mempool endpoints.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| urgency | string | no | How time-sensitive is your transaction? low=economy, medium=default, high=next-block. |
Resolve a Lightning Address (user@domain.com) to a payable BOLT11 invoice for a given amount. Handles the full LNURL-pay protocol internally. Returns the invoice plus min/max sendable amounts for validation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Lightning Address in user@domain.com format. |
| amount_sats | integer | yes | Amount you want to send, in satoshis. |
Fetch a Bitcoin transaction by txid and return a structured, agent-ready summary: type (P2WPKH/P2TR/P2SH/etc.), input/output counts, fees, fee rate in sat/vB, confirmation status, RBF flag, SegWit/Taproot flags, and a one-line agent_summary string ready for LLM context injection. Saves 500-2000 tokens vs parsing raw TX JSON.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| txid | string | yes | Bitcoin transaction ID (64 hex characters). |
Bitcoin transaction timing intelligence. Returns a congestion forecast for the next 1-4h, a recommended UTC send window when fees are projected at/below your target, a fee trajectory (rising/stable/falling) with a calibrated confidence score, next-block minimum fee, confirmation targets for 3/6/144 blocks, and an RBF-viability flag. A synthesis layer above raw fee data — the decision an autonomous
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target_sat_vb | number | no | Your fee ceiling in sat/vB. The recommended window targets at-or-below this rate. Omit to get the lowest-projected window. |
| hours_ahead | integer | no | How far ahead to search for the optimal window (1-6h, default 4). |
Validate JSON, identify its root type, and return normalized JSON plus a SHA-256 content hash.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| json | string | yes | JSON text to validate, up to 100 KB. |
Extract one value from JSON using a simple dot path with array indexes, for example users[0].email.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| json | string | yes | JSON text, up to 100 KB. |
| path | string | yes | Dot path such as user.profile.name or users[0].email. |
Convert CSV, TSV, semicolon, or pipe-delimited text into structured JSON with bounded row output.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| csv | string | yes | Delimited text, up to 100 KB. |
| delimiter | string | no | Delimiter name. Default comma. |
| header | boolean | no | Use the first row as object keys. Default true. |
| max_rows | integer | no | Maximum data rows to return. Default 100. |
Return deterministic text statistics, estimated tokens, reading time, and a SHA-256 content hash.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | Text to analyze, up to 100 KB. |
Generate a SHA-256 or SHA-512 digest in hexadecimal or Base64 form.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | Input text, up to 100 KB. |
| algorithm | string | no | Hash algorithm. Default sha256. |
| encoding | string | no | Output encoding. Default hex. |
Encode UTF-8 text to Base64 or decode Base64 safely, with standard and URL-safe alphabets.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| data | string | yes | Text or Base64 data, up to 100 KB. |
| action | string | yes | — |
| url_safe | boolean | no | Use the URL-safe alphabet without padding. |
Convert Unix seconds, Unix milliseconds, RFC3339, or ISO dates into normalized UTC timestamp forms.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | string | yes | Timestamp value. |
| from | string | no | Input format. Default auto. |
Generate one to one hundred cryptographically random RFC 4122 UUID version 4 identifiers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| count | integer | no | Number of UUIDs. Default 1. |
Parse an HTTP or HTTPS URL into normalized scheme, host, port, path, query, and fragment fields without fetching it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Absolute HTTP or HTTPS URL, up to 4,096 characters. |
Decode JWT header and payload claims locally without verifying the signature. The response always marks verification as false.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| token | string | yes | JWT compact serialization, up to 20 KB. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Loop or to call it, at any volume.
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.4.0.
No release note was published with this version.
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.
Any signed-in account that does not publish Loop can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.