Non-custodial USDT and USDC payments from your AI assistant: invoices, payment totals and ready prompts across your Stablevoy stores, docs without a key. Keys cannot move funds.
Machina 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
x402-powered AI agent services — URL extraction, PDF processing, code scanning, and more.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'MACHINA_WALLET_KEY=${MACHINA_WALLET_KEY}' --transport stdio machina-mcp '--' uvx machina-mcp
# 2 — ask your agent for something these tools do
# url_extract, scan_python, validate_email and 5 more
It needs MACHINA_WALLET_KEY: this reads it from your environment, so export it first.
Machina 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. This one runs on your machine: your client starts Machina 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.
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads MACHINA_WALLET_KEY (Ethereum private key (hex, 0x-prefixed) for x402 payments in USDC on Base) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx MACHINA_WALLET_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'MACHINA_WALLET_KEY=${MACHINA_WALLET_KEY}' --transport stdio machina-mcp '--' uvx machina-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
It reaches a system of yours, so it needs your own credential rather than the publisher’s: MACHINA_WALLET_KEY — Ethereum private key (hex, 0x-prefixed) for x402 payments in USDC on Base. You set it in your own client’s config, on your machine — this marketplace never holds it.
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.
8 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.
Fetch a URL and return its full content as clean Markdown. Useful for reading web pages, articles, blog posts, and documentation. Returns title, word count, and the full text as Markdown. Cost: $0.005 per call.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | — |
Scan Python source code for security vulnerabilities. Detects: hardcoded secrets/API keys, eval/exec misuse, shell injection, insecure SSL/TLS, dangerous deserialization (pickle, yaml.load), path traversal, and CVE-affected dependency versions. Returns structured findings with severity…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | — |
| filename | string | no | — |
Validate a single email address. Checks: syntax/format, MX record existence, disposable email provider detection, and role-address detection (noreply@, info@, etc.). With smtp_probe=True, attempts an SMTP connection to verify the mailbox exists (best-effort — some servers block probes). Returns a…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | — | |
| smtp_probe | boolean | no | — |
Validate up to 100 email addresses in a single call. Same checks as validate_email (syntax, MX, disposable, role-address) but optimised for batch processing. SMTP probing is off by default to keep latency low. Returns per-address results plus a summary. Cost: $0.500 per call (up to 100 emails,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| emails | array | yes | — |
| smtp_probe | boolean | no | — |
Get comprehensive intelligence on a domain name. Returns: DNS records (A/MX/NS/TXT/SPF/DMARC), WHOIS registration data and domain age, SSL certificate details and expiry, HTTP response headers, tech stack detection (CMS, server, CDN, etc.), and email infrastructure analysis. Cost: $0.050 per call.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | — |
FREE pre-check for a PDF file. Returns page count, file size, and metadata (title, author, creator, creation date) without extracting any text. Use this before pdf_extract or pdf_extract_large to check the page count and decide which extractor to use. No payment required. Cost: FREE.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pdf_path | string | no | — |
| pdf_base64 | string | no | — |
Extract text from a PDF (up to 50 pages) and return it as Markdown. Preserves headings, tables, lists, and document structure. Call pdf_inspect first to verify page count — use pdf_extract_large for documents over 50 pages. Cost: $0.050 per call.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pdf_path | string | no | — |
| pdf_base64 | string | no | — |
Extract text from a large PDF (up to 200 pages) and return it as Markdown. For documents over 50 pages. Call pdf_inspect first to check the page count. For documents ≤50 pages, prefer pdf_extract (cheaper). Cost: $0.180 per call.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pdf_path | string | no | — |
| pdf_base64 | string | no | — |
- 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 Machina 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.
| 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 |
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.
Tools were statically extracted from the published source (8 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>".
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.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| url_extract | untrusted-input | untrusted-input: keyword "fetch", parameter "url" with "fetch" in the description |
| scan_python | no tags | |
| validate_email | no tags | |
| validate_email_bulk | no tags | |
| domain_intel | no tags | |
| pdf_inspect | no tags | |
| pdf_extract | no tags | |
| pdf_extract_large | 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
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 0.1.1. Pin a release below and the command asks for exactly that one.
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 Machina 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.