MCP server for terminal commands, file operations, and process management
Docs 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
Documents and web for AI agents: PDF parse, OCR, web extract, invoice checks. x402, no API key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mart402-docs-mcp https://mart402.com/mcp/docs
# 2 — ask your agent for something these tools do
# get_catalog, quote_parse, get_receipt and 11 more
Docs 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 mart402-docs-mcp https://mart402.com/mcp/docsReconnect, 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.
14 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.
Mart402 product catalog: all products, prices, payment config, error codes, rate limits. Free.
No parameter schema on file.
Free quote for PDF parsing: page count, route (text/scan-OCR) and the exact final price, before any payment. Use the returned quote_id with parse_document (on /mcp or /mcp/docs).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | PDF URL |
Re-fetch a previously paid result for free by receipt id (every paid response carries receipt_id).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| receipt_id | string | yes | receipt_id from a paid response (rcpt_...) |
Free recorded sample response for a paid product (from real production runs, marked sample:true) - see the exact response shape before paying anything. Available: document-pipeline, enrich, extract, jp-bonus-net, jp-business-days, jp-company, jp-consumption-tax, jp-crypto-tax, jp-dependent-threshold, jp-mortgage, jp-overtime-wage, jp-payroll-net, jp-payroll-suite, jp-payslip-audit, jp-retirement-t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | yes | One of: document-pipeline, enrich, extract, jp-bonus-net, jp-business-days, jp-company, jp-consumption-tax, jp-crypto-tax, jp-dependent-threshold, jp-mortgage, jp-overtime-wage, jp-payroll-net, jp-pay |
Extract a web page to clean Markdown + metadata (auto JS rendering, robots.txt respected). $0.005 fast / $0.01 rendered; cached results half price. Choose this when you need a web PAGE as clean Markdown to read yourself; to fill a schema use structured_extract, for a PDF use pdf_info then parse_document.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Absolute http(s) URL of the input (web page or PDF, per tool) |
| mode | string | no | Extraction mode: auto (fast with rendered fallback), fast, heavy |
| ttl | integer | no | cache seconds (0 = no cache) |
| x_payment | string | no | Optional: base64 X-PAYMENT header value (x402 exact scheme, USDC on Base mainnet). Omit it to receive the payment requirements (accepts[] + docs) for this call without being charged. |
Parse a PDF to structured Markdown (hallucination-guarded OCR for scanned pages, Japanese-strong). Pass url (one step: the 402 quotes the exact price for that PDF) or quote_id from quote_parse (price fixed by the quote). One of the two is required. Choose this when the input is a PDF and you want its full text as Markdown; call pdf_info first if you do not know whether it is scanned, and use docum
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | Absolute http(s) URL of the PDF (one-step form) |
| quote_id | string | no | quote_id returned by quote_parse (price is fixed by the quote) |
| x_payment | string | no | Optional: base64 X-PAYMENT header value (x402 exact scheme, USDC on Base mainnet). Omit it to receive the payment requirements (accepts[] + docs) for this call without being charged. |
OCR one image to text with dual-engine consensus, calibrated confidence and per-segment corroboration. Japanese-strong. Flat $0.05/image. Choose this when the input is an IMAGE (photo, screenshot, receipt); for PDFs use parse_document.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| image_url | string | no | Absolute http(s) URL of the image (JPEG/PNG/WebP) |
| image_base64 | string | no | Base64-encoded image bytes (alternative to image_url) |
| lang | string | no | One of: japanese, latin. Expected script for OCR: japanese or latin |
| x_payment | string | no | Optional: base64 X-PAYMENT header value (x402 exact scheme, USDC on Base mainnet). Omit it to receive the payment requirements (accepts[] + docs) for this call without being charged. |
Verify extracted invoice fields: arithmetic consistency, line-item totals, JP registration number check-digit + corporate-number existence observation (official Japan NTA registry), accounting-ready JSON. $0.015/call. Choose this when you already HAVE invoice fields (from your own extraction) and only need them checked; to start from a PDF use document_pipeline.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | object | yes | Extracted invoice fields: total_jpy, tax_jpy, reg_no, invoice_no, issue_date, due_date, vendor, customer |
| line_items | array | no | Optional line items [{description, amount_jpy}] to reconcile against the subtotal |
| x_payment | string | no | Optional: base64 X-PAYMENT header value (x402 exact scheme, USDC on Base mainnet). Omit it to receive the payment requirements (accepts[] + docs) for this call without being charged. |
Company name/domain/URL to a verified profile from primary sources + GLEIF LEI and Japan NTA corporate-number registries. Per-field evidence + confidence, honest nulls; unresolved lookups never charged. $0.03/company. Choose this when you have a company NAME or DOMAIN and need a registry-grounded profile (GLEIF LEI / Japan NTA) with per-field evidence; pass country_hint 'jp' for Japanese companies
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | yes | Company name, domain or URL |
| country_hint | string | no | ISO country hint for registry lookups, e.g. 'jp' |
| x_payment | string | no | Optional: base64 X-PAYMENT header value (x402 exact scheme, USDC on Base mainnet). Omit it to receive the payment requirements (accepts[] + docs) for this call without being charged. |
Fill YOUR JSON schema from any URL (hybrid LLM + deterministic canonicalization). $0.03/call. Choose this when you have your OWN JSON schema to fill from any page; for company profiles use enrich_company or jp_company_profile.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Absolute http(s) URL of the input (web page or PDF, per tool) |
| schema | object | yes | {key: description} pairs |
| instructions | string | no | optional extra guidance for filling the schema |
| x_payment | string | no | Optional: base64 X-PAYMENT header value (x402 exact scheme, USDC on Base mainnet). Omit it to receive the payment requirements (accepts[] + docs) for this call without being charged. |
One call: PDF invoice to parse (hallucination-guarded OCR) + field extraction + arithmetic verification (+optional issuer enrich). Flat $0.05/document; inputs validated before payment. Choose this when a PDF is an invoice/receipt and you want parse + field extraction + arithmetic verification in one paid call; for text only use parse_document.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Absolute http(s) URL of the input (web page or PDF, per tool) |
| enrich | boolean | no | Also run issuer enrichment on the parsed invoice |
| x_payment | string | no | Optional: base64 X-PAYMENT header value (x402 exact scheme, USDC on Base mainnet). Omit it to receive the payment requirements (accepts[] + docs) for this call without being charged. |
Merge 2-10 PDFs into one, in order. Deterministic, $0.003.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| urls | array | yes | List of absolute PDF URLs, in order (2-10) |
| x_payment | string | no | Optional: base64 X-PAYMENT header value (x402 exact scheme, USDC on Base mainnet). Omit it to receive the payment requirements (accepts[] + docs) for this call without being charged. |
Extract pages from a PDF by 1-based ranges (e.g. 1-3,7) into a new PDF. Deterministic, $0.002.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Absolute http(s) URL of the input (web page or PDF, per tool) |
| pages | string | yes | 1-based page ranges, e.g. '1-3,7' |
| x_payment | string | no | Optional: base64 X-PAYMENT header value (x402 exact scheme, USDC on Base mainnet). Omit it to receive the payment requirements (accepts[] + docs) for this call without being charged. |
PDF facts before you pay for parsing: pages, metadata, per-page text volume, scanned-or-not estimate. $0.001. Choose this first for any unknown PDF (cheapest real call); then parse_document, pdf_pages or document_pipeline.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Absolute http(s) URL of the input (web page or PDF, per tool) |
| x_payment | string | no | Optional: base64 X-PAYMENT header value (x402 exact scheme, USDC on Base mainnet). Omit it to receive the payment requirements (accepts[] + docs) for this call without being charged. |
- 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 Docs 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 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
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 |
|---|---|---|
| get_catalog | no tags | |
| quote_parse | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_receipt | untrusted-input | untrusted-input: keyword "fetch" |
| get_sample | no tags | |
| extract_url | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| parse_document | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| ocr_image | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| verify_invoice | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| enrich_company | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| structured_extract | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| document_pipeline | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| pdf_merge | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| pdf_pages | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| pdf_info | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
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.
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
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 1.0.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 Docs 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.