# tech.interpretai/PostAgent (remote · api.postagent.sh)

Print & mail PDF/HTML/Markdown/text/DOCX/images to US addresses; pay per call in x402 USDC on Base.

- Trust score: 68/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.postagent.sh`: 68/100 (this document), [markdown](https://verifymcp.io/servers/tech-interpretai-postagent/api.md), [page](https://verifymcp.io/servers/tech-interpretai-postagent/api)

## Channel facts

- Endpoint: `https://api.postagent.sh/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (pay_mail_with_shared_payment_token).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 4836 tokens (~241/item across 20 items; 14 tools + 6 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 79% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http tech-interpretai-postagent https://api.postagent.sh/mcp
```

### Codex

```toml
[mcp_servers.tech-interpretai-postagent]
url = "https://api.postagent.sh/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-interpretai-postagent": {
      "type": "remote",
      "url": "https://api.postagent.sh/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-interpretai-postagent --url https://api.postagent.sh/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-interpretai-postagent:
    url: "https://api.postagent.sh/mcp"
```

### Other

```json
{
  "mcpServers": {
    "tech-interpretai-postagent": {
      "type": "http",
      "url": "https://api.postagent.sh/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 63)

First indexed and scored.

## MCP tools (14)

### `check_postagent_updates` (~136 tokens)

Check latest PostAgent skill and MCP versions

Fetches the live PostAgent agent manifest. Call this before using PostAgent in a new session, after reconnecting the MCP server, or when an installed PostAgent skill may be stale. If the installed skill is older than latestSkillVersion, read latestSkillUrl and follow those instructions for this turn; if updateRequired is true, do not perform paid or irreversible PostAgent actions until the user updates.

Input parameters:

- `installedMcpVersion` (string): Version advertised by the connected PostAgent MCP server, if known.
- `installedSkillVersion` (string): Version from the installed PostAgent SKILL.md frontmatter, if known.

### `create_letter` (~491 tokens)

Upload a finished letter (identical content, no mail merge)

Upload and normalize a FINISHED, ready-to-mail document to PDF. Choose this when the content is final and IDENTICAL for every recipient — including when you mail the same letter to many people (just quote/pay once per recipient with the same documentId). The exact bytes you give are what gets printed. Use create_template instead only when the content must vary per recipient via {{fields}}. Returns a documentId, the stored page count, byte size, and source format. Free; no payment required.

Provide the document EXACTLY ONE way: `content` (inline text, for html/markdown/text), `contentBase64` (base64-encoded binary, for pdf/docx/image), or `url` (a publicly reachable URL the server fetches). Supplying none, or more than one, is an error. Maximum upload size is 31457280 bytes (~30 MB); output page size is US Letter.

Any `{{...}}` text is printed LITERALLY here — it is NOT treated as a merge field. If you want personalized mail merge across recipients, use `create_template` instead.

Reserved address zone: a recipient address block is printed over the top ~3 inches of page 1, so the server reserves that space for you automatically. For text/html/markdown/docx, page-1 content is pushed below the block (content may therefore flow onto an additional page); for pdf and image inputs, a blank first page is prepended. As a result the returned page count — and the selected-provider cost behind the resulting quote — can be higher than your source document (e.g. a single-page PDF is stored as 2 pages). You do NOT need to leave the top of your document blank yourself. See the postagent://formats resource for per-format details.

Input parameters:

- `content` (string): Inline text content (html, markdown, or text). Provide exactly one source.
- `contentBase64` (string): Base64-encoded binary content (pdf, docx, image). Provide exactly one source.
- `filename` (string): Optional original filename; used to help infer the source format.
- `format` (string): Source format. Inferred from contentType/filename/content when omitted; inline `content` with no format defaults to text.
- `url` (string): Public URL the server will fetch the document from. Provide exactly one source.

### `create_template` (~521 tokens)

Upload a mail-merge template (content varies per recipient)

Upload a REUSABLE template containing `{{field}}` placeholders (e.g. `Dear {{name}},` or `Balance due: {{amount}}`). Choose this ONLY when the content must vary per recipient (mail merge) — recipient count is irrelevant, so a single personalized letter belongs here too. If the content is identical for everyone, use create_letter instead (this tool rejects input with no `{{fields}}`). Returns a documentId with `kind: "html_template"`, a `mergeFields` list of the detected field names, and an `estimatedPageCount`. Free; no payment required.

Template source must be TEXT-BASED (html, markdown, or text) and must contain at least one `{{field}}`, or the upload is rejected — for a finished document with no merge fields, use `create_letter`.

Provide the template EXACTLY ONE way: `content` (inline text), `contentBase64` (base64-encoded text), or `url` (a publicly reachable URL the server fetches). Supplying none, or more than one, is an error. Maximum upload size is 31457280 bytes (~30 MB); output page size is US Letter.

Reuse one template documentId across recipients: call create_mail_quote ONCE PER RECIPIENT, supplying that recipient's values via `mergeVariables` (every field in `mergeFields` must have a non-empty value). The server substitutes the values and renders that recipient's personalized PDF at quote time, so `estimatedPageCount` is only a baseline — the binding page count and price are set per quote from the actual rendered output.

Reserved address zone: a recipient address block is printed over the top ~3 inches of page 1, so the server reserves that space automatically (page-1 content is pushed below the block and may flow onto an additional page). You do NOT need to leave the top blank yourself. See the postagent://formats resource for details.

Input parameters:

- `content` (string): Inline text content (html, markdown, or text). Provide exactly one source.
- `contentBase64` (string): Base64-encoded binary content (pdf, docx, image). Provide exactly one source.
- `filename` (string): Optional original filename; used to help infer the source format.
- `format` (string): Template source format (text-based only). Inferred when omitted; inline `content` defaults to text.
- `url` (string): Public URL the server will fetch the document from. Provide exactly one source.

### `create_mail_quote` (~451 tokens)

Get a locked price quote for a print-and-mail job

Verifies the recipient and sender US addresses and locks a 15-minute USDC price for a documentId. Does not charge or mail anything. Returns a `paymentUrl` (a per-quote x402-payable URL); the preferred way to actually mail the letter is for the agent's wallet to perform an in-band x402 payment against that URL (e.g. `npx awal@latest x402 pay <paymentUrl>`). The MCP `submit_paid_mail_job` tool is a fallback for clients that can emit a standalone signature header. In all cases, show the recipient, sender, options, selected-route `design` constraints, price, AND any `fulfillment.warnings` to the user and get explicit confirmation before paying. The response includes a `fulfillment` block with `requested` (what you asked for), `selected` (what will actually be printed/mailed) and `warnings` (any soft-preference downgrades — e.g. `service_level_downgraded` or `extra_service_unavailable`); do not pay through a non-empty warnings list without re-confirming the trade-off with the user. The response also includes a provider-neutral `design` block; inspect it and the preview before paying because the selected delivery method determines print address/no-ink zones.

Input parameters:

- `documentId` (string, required): ID returned by create_letter (finished document) or create_template (mail-merge template) for the piece to mail.
- `from` (object): Sender/return address. Required unless the server has a fallback configured.
- `mergeVariables` (object): Values for a template document's {{merge fields}}, e.g. { "name": "Jane", "amount": "$42.00" }. Required when documentId refers to an html_template: every field listed in that document's mergeFields…
- `options` (object)
- `to` (object, required): Recipient's US postal address.

### `create_card_checkout` (~224 tokens)

Create a hosted credit-card checkout link for a quote

Creates a Stripe-hosted Checkout page for a locked quote and returns a `checkoutUrl` plus a `statusUrl`. Use this as the LAST-RESORT payment rail, when the payer is a human paying by credit card (the agent cannot complete card entry itself). Hand the `checkoutUrl` to the user to open in a browser and pay; payment is asynchronous — once they finish, the letter is created automatically by Stripe's webhook. To track it without a job id, GET the returned `statusUrl` (`/v1/quotes/:quoteId/job`): it returns `found:false` with status `pending`/`processing` until the webhook creates the job, then the full job (id, status, tracking). Prefer x402 (or MPP, if available) for autonomous agent payment. Returns an error if Stripe Checkout is not enabled on the server. No charge occurs until the human completes the hosted page.

Input parameters:

- `quoteId` (string, required)
- `webhookUrl` (string): Optional caller-controlled webhook URL to receive job status updates.

### `pay_mail_with_shared_payment_token` (~418 tokens)

Pay a quote autonomously by card/wallet via a Shared Payment Token (MPP)

Autonomous, no-browser FIAT payment for a locked quote using a Stripe Shared Payment Token (SPT / Machine Payments Protocol). Use this when the agent can mint an SPT on the buyer's behalf and wants to pay by card/wallet without a human in a browser (prefer x402 first if the agent has a USDC-on-Base wallet; this is the autonomous fiat alternative). CHARGES MONEY AND IS IRREVERSIBLE: the server authorizes the SPT, prints the letter, then captures — a job comes back inline (no polling needed). Only call after the user has explicitly confirmed the recipient, sender, content, and price from create_mail_quote.

Minting the token (the agent's responsibility, NOT this server): the SPT must be scoped to THIS seller's Stripe profile and to at least the quote amount. The quote's `paymentOptions` entry for `mpp` carries the `stripeProfileId`, `currency`, `maxAmountCents`, and `expiresAt` you need. Mint it with the buyer's payment method via the Stripe `@stripe/link-cli` (`spend-request create … --network-id <stripeProfileId> --credential-type shared_payment_token`) or the SharedPaymentIssuedToken API, then pass the resulting `spt_…` here. SPTs are US-only and cards carry a 0.50 USD minimum. Returns an error if MPP is not enabled/configured on the server.

Input parameters:

- `quoteId` (string, required)
- `sharedPaymentToken` (string, required): A Stripe Shared Payment Token (spt_…) the agent minted for the buyer, scoped to this seller's Stripe profile (see the quote's mpp paymentOption.details.stripeProfileId) and to at least the quote amou…
- `userConfirmed` (boolean, required): Must be true. Set this only after the human user explicitly approved sending physical mail at the quoted price.
- `webhookUrl` (string): Optional caller-controlled webhook URL to receive job status updates.

### `prepare_mail_payment` (~113 tokens)

Fetch the x402 payment challenge for a quote

Returns the x402 PAYMENT-REQUIRED challenge for a locked quote so an x402-capable wallet client can sign it. No payment is taken at this step. Probes the canonical per-quote pay URL (`/v1/quotes/:quoteId/pay`). The preferred way to actually pay is for the wallet to perform the standard x402 in-band handshake against `paymentUrl`; this tool is for inspection or for the detached-signature flow via `submit_paid_mail_job`.

Input parameters:

- `quoteId` (string, required)

### `submit_paid_mail_job` (~231 tokens)

Submit a signed x402 payment to create and mail the letter

Detached-signature fallback for x402 wallets that can emit a standalone PAYMENT-SIGNATURE header. THE PRIMARY/RECOMMENDED PATH is for the agent's wallet to pay the quote's `paymentUrl` in-band (e.g. `npx awal@latest x402 pay <paymentUrl>`); use this tool only if your wallet client cannot do that. Charges the agent in USDC on Base mainnet and creates a physical letter for printing and mailing. THIS IS IRREVERSIBLE. Only call after the user has explicitly confirmed the recipient, sender, content, and price returned by create_mail_quote, and after obtaining the signed x402 payment header (see prepare_mail_payment).

Input parameters:

- `paymentSignature` (string, required): x402 PAYMENT-SIGNATURE header value produced by an x402 client after signing the prepare_mail_payment challenge.
- `quoteId` (string, required)
- `userConfirmed` (boolean, required): Must be true. Set this only after the human user explicitly approved sending physical mail at the quoted price.
- `webhookUrl` (string): Optional caller-controlled webhook URL to receive job status updates.

### `get_mail_job_status` (~38 tokens)

Get the current status of a mail job

Returns normalized status, carrier/tracking/proof data, and tracking events for a previously created job.

Input parameters:

- `jobId` (string, required)

### `create_postcard_art` (~287 tokens)

Upload postcard artwork (front or back)

Upload ONE side of a postcard (front or back) as single-page PDF, PNG, or JPEG artwork. The file is stored VERBATIM — no page-size normalization and no reserved address zone — so you are responsible for the correct trim size plus bleed: 4x6 cards need 4.25"x6.25" artwork, 6x9 needs 6.25"x9.25", 6x11 needs 6.25"x11.25" (0.125" bleed on each edge). The selected delivery method prints the recipient address block over part of the BACK, so keep that area clear of critical content and review the quote's `design` block before payment. Returns a documentId with kind "postcard_art". Upload front and back separately, then quote with create_postcard_quote. Free; no payment required.

Provide the artwork EXACTLY ONE way: `contentBase64` (base64-encoded pdf/png/jpeg) or `url` (publicly reachable). Text-based formats are rejected — postcards are artwork, not documents.

Input parameters:

- `contentBase64` (string): Base64-encoded single-page PDF, PNG, or JPEG artwork.
- `filename` (string)
- `format` (string): Artwork format; inferred from content when omitted.
- `url` (string): Public URL the server fetches the artwork from.

### `create_postcard_quote` (~310 tokens)

Get a locked price quote for printing and mailing a postcard

Verifies the recipient and sender addresses and locks a 15-minute USDC price for mailing a postcard built from two postcard_art documents (front + back, uploaded via create_postcard_art). Sizes: 4x6 (default), 6x9, 6x11 — postcards always print in full color. US recipients use the strict US address shape; INTERNATIONAL recipients are supported on 4x6 only (set `to.country` to the 2-letter ISO code; the sender must still be a US address). Payment works exactly like letters: pay the returned `paymentUrl` via x402, or use the MPP/checkout fallbacks. Show the recipient, sender, size, selected-route `design` constraints, price, AND any `fulfillment.warnings` to the user and get explicit confirmation before paying — service level is a soft preference and may have been downgraded (e.g. international economy is upgraded to standard) with a `service_level_downgraded` warning the agent must surface verbatim.

Input parameters:

- `backDocumentId` (string, required): documentId of the BACK artwork (kind postcard_art). The print partner prints the recipient address block over part of the back.
- `from` (object): US sender/return address. Required unless the server has a fallback configured.
- `frontDocumentId` (string, required): documentId of the FRONT artwork (kind postcard_art).
- `options` (object)
- `to` (object, required): Recipient address.

### `verify_address` (~330 tokens)

Verify a postal address for deliverability (paid, flat fee)

Standalone paid address verification — no mail is sent. Checks whether an address is deliverable and returns the standardized form (US: CASS with ZIP+4; international: per-country matching). Costs a small flat USDC fee per call via x402 (a fraction of a cent vs. mailing).

Two-step flow, like the mail rails: call WITHOUT `paymentSignature` to get the 402 challenge and `paymentUrl` (preferred: have the agent's x402 wallet pay `paymentUrl` in-band with the address as the JSON POST body `{"address":{...}}`); or sign the challenge and call again WITH `paymentSignature` to verify and get the result in one round trip. US addresses need line1 + (city+state or zip). International addresses need line1 + country.

Note: when mailing through PostAgent you do NOT need this tool — create_mail_quote already verifies sender and recipient for free as part of the quote.

Input parameters:

- `city` (string)
- `country` (string): 2-letter ISO country code. Omit or 'US' for CASS-standardized US verification; any other code runs international verification.
- `line1` (string, required): Street address line 1
- `line2` (string)
- `name` (string): Recipient/contact name (optional)
- `paymentSignature` (string): x402 PAYMENT-SIGNATURE header value signed against this endpoint's challenge. Omit to fetch the challenge first.
- `state` (string): State/province/region
- `zip` (string): ZIP or postal code

### `create_campaign_quote` (~362 tokens)

Get a locked price quote for a bulk mail campaign (KYC required)

Quote ONE bulk send to MANY recipients (up to 500): a single template or static document, fulfilled through PostAgent's campaign workflow. Price is an inclusive customer-facing total, locked for 15 minutes. Payment is x402 ONLY.

IMPORTANT — KYC WALL: campaigns require the paying wallet to be identity-verified with PostAgent. Verification is operator-run, not self-serve: until the wallet is verified this tool returns `kyc_required` (403). Do not retry the same wallet — instead either mail recipients individually with create_mail_quote, or request campaign access at https://interpretai.tech/contact (this URL is also returned in the 403's details.contactUrl) to get the wallet enabled.

Usage once the wallet is verified: upload a template with create_template (using {{fields}}) or a finished letter with create_letter, then call this with `recipients` (each `to` a US address, plus per-recipient `mergeVariables` for templates) and the `payerWallet` that will pay the quote. The print partner validates every recipient address after payment; failed recipients are excluded and their share refunded (processed manually). Track via get_campaign_status.

Input parameters:

- `documentId` (string, required): Template (html_template) or finished letter (pdf) documentId.
- `from` (object): US sender/return address. Required unless the server has a fallback.
- `name` (string): Campaign name (for your records).
- `options` (object)
- `payerWallet` (string, required): The x402 wallet that will pay this quote. Must be KYC-verified with PostAgent (re-checked at payment against the wallet that actually signs).
- `recipients` (array, required): One entry per recipient (1-500).

### `get_campaign_status` (~108 tokens)

Get the status of a bulk mail campaign

Returns a campaign's validation/sending progress: status (validating | sent | partial | failed), recipient counts (total / validated / failed), and a failures report URL when some recipients could not be validated. Polling this endpoint also advances the campaign (it releases the campaign for mailing once the print partner finishes validating the audience). Find the campaign id on the quote's job status (GET jobStatusUrl) after payment.

Input parameters:

- `campaignId` (string, required): Campaign id (cmp_…).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tech-interpretai-postagent/api#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 67
- 2026-08-01: 67
- 2026-07-31: 66
- 2026-07-30: 65
- 2026-07-29: 65
- 2026-07-28: 64
- 2026-07-27: 63
- 2026-07-26: 63

## Links

- Remote endpoint: https://api.postagent.sh/mcp
- Repository: https://github.com/interpretai-tech/agent-tools
- Website: https://api.postagent.sh/
- Changelog RSS feed: https://verifymcp.io/servers/tech-interpretai-postagent/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-interpretai-postagent/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/tech-interpretai-postagent/api