Shippo

Name: Shippo MCP Server
Availability: InStock
Author: Shippo

Productivity4 tools

Buy shipping labels, compare carrier rates and track packages from your AI assistant. Four tools, but they are a read/write dispatcher pair onto Shippo's 70-operation API — and Shippo's directory record is the only one in this catalogue that volunteers that labels can be bought and refunded.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 19 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Shippo via MCP

https://mcp.shippo.com/

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Shippo Tools & Capabilities (4)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

The tool count does not measure the surface. Four tools front 70 API operations across 20 paths, counted from Shippo's published OpenAPI specification on 2026-08-19. Review the API reference, not the tool list.
It spends real money against a live account. Shippo documents no test mode on the hosted MCP server. Label purchases charge your Shippo account; only rate comparison, address validation and Shippo-purchased tracking are free.
The confirmation gate is a vendor claim we did not verify. Shippo states buying and account-changing actions ask first. Verifying it would mean authenticating and buying a label, so we did not. It is also the server prompting, not your client.
A refund is not an undo. Unused labels only, within 90 days, up to 14 business days to process, rejected outright if the carrier scanned the label, and settled as a negative invoice line rather than an immediate credit. One label per request.
OAuth offers no least-privilege option. Both the RFC 9728 descriptor and the RFC 8414 metadata advertise scopes_supported as ["*"]. The read/write split exists in the tool names only; it has no expression in the grant.
We could not verify tool behaviour ourselves. The endpoint returned HTTP 401 to an anonymous request on 2026-08-19, so no inputSchema, no readOnlyHint and no destructiveHint annotations were readable. The four names come from Anthropic's directory snapshot; Shippo's own docs do not enumerate tool names at all.
Prompts are unconfirmed. Anthropic's snapshot lists none, and the gated endpoint blocked our own check.
The read surface is personal data. Shipping addresses are named individuals' home addresses, and the address book is a listable resource, not one shipment at a time.
Billing timing is not publicly documented. Shippo's support articles on billing cycles and payment methods sit behind a sign-in wall, so we cannot state from a public source whether a label charge hits a card immediately or accrues to a periodic invoice. Shippo's public docs confirm only that the purchase charges your account.
Carrier policies sit underneath everything. Shippo states refunds are subject to the applicable carrier's policies, which it does not enumerate. The rules above are Shippo's floor, not any individual carrier's.

Frequently asked questions

How many operations can the Shippo MCP server actually reach?

Far more than its four tools suggest. All four are dispatcher plumbing, not shipping actions, and behind them sits Shippo's REST API — 20 paths carrying 70 operations, counted from Shippo's own published OpenAPI specification on 2026-08-19. Those cover addresses, shipments, rates, transactions, refunds, tracking, orders, manifests, batches, pickups, customs and carrier accounts.

Can the Shippo connector spend my money?

Yes. Shippo's directory record says so itself, naming label purchases and refunds outright, and Shippo's documentation confirms the hosted server operates against your live account with no test mode. Comparing rates and validating addresses are free; buying a label is a live charge. Shippo states that actions which buy a label or change your account ask for confirmation first.

Does buying a label through Shippo MCP ask for confirmation?

Shippo says yes. Its MCP documentation states that actions buying a label or otherwise changing your account request confirmation before running, fetched 2026-08-19. That is a vendor claim about server behaviour, not something we verified — the endpoint is gated, and testing it would mean authenticating and buying a real label against a live account.

Can a Shippo label refund be reversed or refused?

Refused, yes — reversed, no. Shippo documents that refund requests are rejected once a carrier scans or uses the label, must be submitted within 90 days of purchase, and take up to 14 business days to process. A successful refund appears as a negative line item on your next invoice rather than an immediate credit back.

What OAuth scopes does the Shippo MCP server request?

A single wildcard. Shippo's RFC 9728 descriptor advertises a `scopes_supported` list whose only entry is `*`, and its RFC 8414 authorization-server metadata repeats that same wildcard, both verified live on 2026-08-19. There is no read-only grant and no per-resource narrowing, so the OAuth layer does not mirror the read and write split the tool names promise.

What personal data can a Shippo agent read?

Shipping addresses, which are named individuals' home addresses. Shippo's directory record lists addresses, shipments, rates, tracking, orders, manifests and carrier accounts as readable. Its API documents address records carrying name, street, city, postal code, phone and email. An agent granted read on this connector can enumerate your address book, not merely one shipment.

Sources

Shippo MCP server guide — https://docs.goshippo.com/mcp-server (fetched 2026-08-19 as Markdown via the .md suffix; redirects to /guides/mcp-server. This is the documentation URL Anthropic's directory publishes) · retrieved 2026-08-19
Shippo docs machine index — https://docs.goshippo.com/llms.txt (fetched 2026-08-19; 198 documentation links, of which 77 are API-reference operation pages across 23 resource groups) · retrieved 2026-08-19
Shippo public API specification — https://docs.goshippo.com/spec/shippoapi/public-api.yaml (fetched 2026-08-19; the 20-path, 70-operation count is derived from its paths block: 38 GET, 22 POST, 6 PUT, 4 DELETE) · retrieved 2026-08-19
Shippo refunding labels — https://docs.goshippo.com/billing-and-invoices/refunding-labels (fetched 2026-08-19; 90-day window, 14-business-day processing, rejection on carrier scan, negative invoice line item) · retrieved 2026-08-19
Shippo create-a-shipping-label reference — https://docs.goshippo.com/api-reference/transactions/create-a-shipping-label (fetched 2026-08-19) · retrieved 2026-08-19
docs.goshippo.com/robots.txt (fetched 2026-08-19) carries a Content-Signal line permitting all three axes — ai-train=yes, search=yes, ai-input=yes — the most permissive signal we have recorded in this catalogue. It disallows only /cdn-cgi/ and /_next/. The marketing host goshippo.com/robots.txt is a bare Allow: / · retrieved 2026-08-19
Official MCP registry entry — https://registry.modelcontextprotocol.io/v0/servers?search=shippo (fetched 2026-08-19; com.shippo/shippo-mcp, streamable-http remote at https://mcp.shippo.com, published 2026-07-10) · retrieved 2026-08-19
npm bridge package metadata — https://registry.npmjs.org/@shippo/shippo-mcp/latest (fetched 2026-08-19; version 3.0.4, described as a local bridge to the same hosted server) · retrieved 2026-08-19
Live RFC 9728 protected-resource descriptor — https://mcp.shippo.com/.well-known/oauth-protected-resource (fetched 2026-08-19; scopes_supported: ["*"], one authorization server https://goshippo.com. The path-append and path-insert forms both return 403 Missing Authentication Token) · retrieved 2026-08-19
Live RFC 8414 authorization-server metadata — https://goshippo.com/.well-known/oauth-authorization-server (fetched 2026-08-19; issuer https://goshippo.com, authorization_code grant only, S256, none client auth, dynamic registration, scopes_supported: ["*"]. The same path on the MCP host returns 403) · retrieved 2026-08-19
Live anonymous probe — 2026-08-19: an initialize POST to https://mcp.shippo.com returns HTTP 401 with JSON-RPC error Missing Bearer token; the challenge arrives on x-amzn-remapped-www-authenticate naming realm="shippo-mcp" and the resource_metadata URL. The endpoint is a bare host, so the root and path-append probe forms collapse to one URL — no redirect was observed · retrieved 2026-08-19
Anthropic connector directory — https://claude.ai/directory/983c8e05-8485-481c-b9b6-c25b291331ce (snapshot 2026-08-16; permissions published as a full paragraph rather than a short label, prompt_names empty, four tool names) · retrieved 2026-08-16
Shippo billing support articles (e.g. support.goshippo.com billing-cycle and payment-method pages) were not usable as sources — the host returns 403 to a plain request and a sign-in page to a browser user agent, so charge timing is reported here as undocumented publicly