ProShip Thailand Post MCP server
me.proship.mcp/proship-mcpmcp.proship.mestreamable-httpv1.0.1Scanned
Create Thailand Post shipments, print labels, and track parcels in Thailand via ProShip.
11 tools: 1 can delete or cancel things, 6 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 3
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the ProShip Thailand Post MCP server can do
The ProShip Thailand Post MCP server is published by mcp.proship.me, a domain the MCP Registry verified. It has 11 tools. It can delete or cancel things (1 tool: cancel_order) and create or change data (6 tools: track_parcel, signup, create_order, update_order_status and 2 more). 4 tools only read.
3 tools can send data out of your system (signup, create_order and check_duplicate).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
11 tools
Deletes or cancels 1Claude Code: deny
cancel_orderDelete/cancel an order by id.No findings
Why it is in this group
- The name "cancel_order" says "cancel": a word for removing or ending something.
Description, as the server wrote it Delete/cancel an order by id.
Changes things 6Claude Code: ask
check_duplicateCheck whether a customer phone number already has a recent order (duplicate-shipment guard).Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it Check whether a customer phone number already has a recent order (duplicate-shipment guard).
create_orderCreate a shipment order.Can send data outNo findings
Why it is in this group
- The name "create_order" says "create": a word for a change.
What it can reach
- outboundThe input takes a destination (input.customer.phone): what the tool writes goes there.
Description, as the server wrote it Create a shipment order. Defaults to Thailand Post EPS (thaipost0). Weight is in GRAMS. Returns the order_id — it contains a pipe suffix (order-xxx|123); always pass the FULL id to other tools. Optional cod_amount enables cash-on-delivery.
print_labelGenerate the shipping label PDF for one or more orders.No findings
Why it is in this group
- The name "print_label" says "label": a word for a change.
Description, as the server wrote it Generate the shipping label PDF for one or more orders. REQUIRES the FULL pipe-suffixed order ids (order-xxx|123) — stripped ids are rejected upstream. Returns a temporary URL (valid ~10 minutes) where the PDF can be downloaded.
signupCreates a real ProShip account and shop, ready for Thailand Post EPS (thaipost0) shipping.Can send data outNo findings
Why it is in this group
- The description's first verb is "create": a word for a change.
What it can reach
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it Creates a real ProShip account and shop, ready for Thailand Post EPS (thaipost0) shipping. The response contains your API token, user, and shop_id — SHOWN ONLY ONCE. Save the token into your MCP client's Authorization header. A full thaipost contract additionally requires a Thailand Post account arranged with ProShip support (multi-day human process).
track_parcelTrack any parcel by tracking number (Thailand Post and other Thai carriers).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Track any parcel by tracking number (Thailand Post and other Thai carriers). Returns current status with Thai label plus the event history. Works without auth if the server has a tracking token configured; otherwise pass your Bearer token.
update_order_statusSet an order status by numeric code (see get_order_statuses).No findings
Why it is in this group
- The name "update_order_status" says "update": a word for a change.
Description, as the server wrote it Set an order status by numeric code (see get_order_statuses).
Only reads 4Show 4 read-only tools
get_orderGet one order by id (full pipe-suffixed id is fine).No findings
Why it is in this group
- The name "get_order" says "get": a word for reading.
Description, as the server wrote it Get one order by id (full pipe-suffixed id is fine). Returns status with Thai label and tracking number.
get_order_statusesReference data: the ProShip order status pipeline.No findings
Why it is in this group
- The name "get_order_statuses" says "get": a word for reading.
Description, as the server wrote it Reference data: the ProShip order status pipeline. Returns every status code with its Thai label and English meaning. Use these codes with list_orders and update_order_status.
list_ordersList orders on YOUR account.No findings
Why it is in this group
- The name "list_orders" says "list": a word for reading.
Description, as the server wrote it List orders on YOUR account. Optional numeric status filter (see get_order_statuses). Paginated.
list_shopsList the shops on YOUR ProShip account.No findings
Why it is in this group
- The name "list_shops" says "list": a word for reading.
Description, as the server wrote it List the shops on YOUR ProShip account. Use the shop_id with create_order.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:15 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 7
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (1 destructive, 6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.proship.me/mcp: tools/list returned 11 tools to an anonymous client, including cancel_order (destructive), track_parcel (write), signup (write), create_order (write), update_order_status (write) and 2 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http proship https://mcp.proship.me/mcpclaude mcp add --transport http proship https://mcp.proship.me/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__proship__get_order_statuses",
"mcp__proship__list_shops",
"mcp__proship__list_orders",
"mcp__proship__get_order"
],
"ask": [
"mcp__proship__track_parcel",
"mcp__proship__signup",
"mcp__proship__create_order",
"mcp__proship__update_order_status",
"mcp__proship__check_duplicate",
"mcp__proship__print_label"
],
"deny": [
"mcp__proship__cancel_order"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as proship. Review it before you use it.
Capability tags behind 3 rules
- mcp__proship__signup outbound
- mcp__proship__create_order outbound
- mcp__proship__check_duplicate outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/me.proship.mcp/proship-mcp/verify?hash=dd7f75bbd466c5a3ee0d370d51b6ea65bf8ecebf7a9bab0d716cf2b29b3bed6c" | jq -e '.changed == false'Pinned hash dd7f75bbd466, from Nov 17, 2026, 23:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/me.proship.mcp/proship-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/me.proship.mcp/proship-mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:53 UTC.
ProShip Thailand Post MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ProShip Thailand Post MCP server safe?
- No scan can promise that. What its definitions show: 11 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ProShip Thailand Post MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: cancel_order.
Can the ProShip Thailand Post MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the ProShip Thailand Post MCP server have?
- 11 tools: 1 destructive, 6 write, 4 read. cancel_order, track_parcel, signup, create_order, update_order_status, check_duplicate, print_label, get_order_statuses and 3 more.
Does the ProShip Thailand Post MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ProShip Thailand Post MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): signup, create_order and check_duplicate.
Has the ProShip Thailand Post MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.