buy
NPM · @CELO/BUY
Pay per request for APIs, compute, browsers, RPC and LLM inference with stablecoins on Celo.
Available components
Last scanned (5 hours ago)
Scores higher than 31% of npm servers
Category Crypto and Web3
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 39 of 132 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 7 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1486 tokens (~212/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "buy_pay_quote" 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 8 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
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.
- 5 Nov 26 +1
- Stability: unverified → 0.10 ▲ functional
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 47
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 npm/@celo/buy@0.8.5
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 →
Dependencies 132 packages
| Packages resolved | 132 |
|---|---|
| Stale | 32 |
| No linked repository | 7 |
| 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 →
buy_balance Check wallet balances ~106
Report the native (CELO) and ERC-20 stablecoin balances of a buy account — the same data as the `buy whoami` CLI command. Read-only: no keychain access, no signing. Use this before buy_send or buy_curl to confirm the wallet is funded.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Account name. Defaults to the configured default account. |
| sandbox | boolean | – | If true, report balances on celo-sepolia. Otherwise uses the account network. |
No output schema declared.
No examples provided.
buy_curl Curl with x402 + Self.xyz auto-pay ~303
Call any URL. If the server returns 402 with an x402 challenge, buy signs an EIP-3009 USDC, USDT or USAT payment locally and retries with X-PAYMENT. If the challenge also demands a Self.xyz attestation, the matching one from the local keystore is attached as X-SELF-ATTESTATION (bound to the same wallet address). Use this instead of plain HTTP when calling paid APIs from your tool calls. Quote first with buy_pay_quote using the same method and body; if this tool then returns a 5xx or fails after the 402 challenge, the payment may still have settled, so do not re-send — report the outcome and any tx hash in this tool's output to the user.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | buy account name. If omitted, uses the configured default account. Run buy_whoami to list available accounts. |
| body | string | – | Request body (raw string) |
| headers | object | – | Extra request headers as a key/value map |
| maxAmount | string | – | Optional cap in atomic selected-token units (6 decimals). If the challenge asks for more, the call aborts before signing. |
| method | string | – | HTTP method |
| sandbox | boolean | – | If true, route payment through celo-sepolia. Otherwise uses the account network. |
| token | string | – | Payment token preference. |
| url | string | yes | Absolute URL to fetch |
No output schema declared.
No examples provided.
buy_discover Discover x402 services ~131
Search the provider registry bundled with buy. This is read-only and never pays. Use it to find a service and its agent instructions, then fetch the service catalog and call buy_pay_quote before any purchase. An entry with stage "experimental" is an early-stage third-party seller buy has not reviewed: confirm with the user before paying it.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional exact category filter. |
| name | string | – | Exact provider name, such as buy/api-gateway. Takes precedence over query. |
| query | string | – | Case-insensitive search across provider name, title, description, and category. |
No output schema declared.
No examples provided.
buy_fetch Fetch with x402 + Self.xyz auto-pay (compatibility alias) ~302
Call any URL. If the server returns 402 with an x402 challenge, buy signs an EIP-3009 USDC, USDT or USAT payment locally and retries with X-PAYMENT. If the challenge also demands a Self.xyz attestation, the matching one from the local keystore is attached as X-SELF-ATTESTATION (bound to the same wallet address). Compatibility alias for buy_curl; prefer buy_curl in new integrations. Quote first with buy_pay_quote using the same method and body; if this tool then returns a 5xx or fails after the 402 challenge, the payment may still have settled, so do not re-send — report the outcome and any tx hash in this tool's output to the user.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | buy account name. If omitted, uses the configured default account. Run buy_whoami to list available accounts. |
| body | string | – | Request body (raw string) |
| headers | object | – | Extra request headers as a key/value map |
| maxAmount | string | – | Optional cap in atomic selected-token units (6 decimals). If the challenge asks for more, the call aborts before signing. |
| method | string | – | HTTP method |
| sandbox | boolean | – | If true, route payment through celo-sepolia. Otherwise uses the account network. |
| token | string | – | Payment token preference. |
| url | string | yes | Absolute URL to fetch |
No output schema declared.
No examples provided.
buy_pay_quote Quote an x402 price (dry run) ~242
DRY RUN — never pays, never signs, never touches the keychain. Fetches a URL once; if the server answers 402 with an x402 challenge, returns the price, network, asset, recipient, and any Self.xyz requirements so you can decide whether to pay before calling buy_curl. Run this before the first paid call to an endpoint: buy_curl settles without a quote, and a settled payment is irreversible.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | buy account name, used to pick the preferred network. If omitted, uses the configured default account. |
| body | string | – | Request body (raw string), same as buy_curl. Required by endpoints that validate input before pricing: quoting POST /google/vm without its JSON body returns 400, not the 402 challenge you are asking… |
| headers | object | – | Extra request headers as a key/value map |
| method | string | – | HTTP method |
| sandbox | boolean | – | If true, prefer the celo-sepolia requirement. Otherwise uses the account network. |
| token | string | – | Payment token preference. |
| url | string | yes | Absolute URL to probe |
No output schema declared.
No examples provided.
buy_verify_status Inspect Self.xyz attestations ~116
List Self.xyz attestations stored on a buy account. Useful before calling a KYC-gated endpoint to confirm the wallet already has a matching attestation (scope, minimum age, OFAC, etc.). This tool cannot create an attestation: the user creates one with `buy verify hosted --endpoint <receiver-url>` against a gateway-hosted receiver, or `buy verify serve --scope <scope> --min-age N --ofac` locally.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Account name. Defaults to the configured default account. |
No output schema declared.
No examples provided.
buy_whoami Inspect buy accounts ~64
List the buy accounts available in the local keystore, the active default, and each account address. Use this before buy_curl to confirm which wallet will sign payments.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | If set, returns details for this specific account instead of a list. |
No output schema declared.
No examples provided.
How do I install the buy MCP server?
buy runs locally as an npm package, launched with npx -y @celo/buy. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @celo/buy
claude mcp add ai-usebuy-buy -- npx -y @celo/buy
What is the buy MCP server?
buy is an MCP server listed in the public MCP registry as ai.usebuy/buy. Pay per request for APIs, compute, browsers, RPC and LLM inference with stablecoins on Celo. This page covers its npm package (@celo/buy).
Is the buy MCP server safe to use?
buy scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 buy MCP server expose?
buy exposes 7 tools: buy_discover, buy_curl, buy_fetch, buy_whoami, buy_verify_status, and 2 more. Their descriptions and schemas cost roughly 1,264 tokens of context every time the server is loaded.
Is the buy MCP server still maintained?
buy 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.
What licence is the buy MCP server under?
buy declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.