ProShip Thailand Post
REMOTE · MCP.PROSHIP.ME · SCANNED SEP 25
Create Thailand Post shipments, print labels, and track parcels in Thailand via ProShip.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 890 tokens (~80/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the ProShip Thailand Post MCP server?
ProShip Thailand Post is a hosted endpoint at https://mcp.proship.me/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.proship.me
claude mcp add --transport http me-proship-mcp-proship-mcp 'https://mcp.proship.me/mcp'
{
"mcpServers": {
"me-proship-mcp-proship-mcp": {
"url": "https://mcp.proship.me/mcp"
}
}
} {
"servers": {
"me-proship-mcp-proship-mcp": {
"type": "http",
"url": "https://mcp.proship.me/mcp"
}
}
} [mcp_servers.me-proship-mcp-proship-mcp] url = "https://mcp.proship.me/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"me-proship-mcp-proship-mcp": {
"type": "remote",
"url": "https://mcp.proship.me/mcp",
"enabled": true
}
}
} openclaw mcp add me-proship-mcp-proship-mcp --url 'https://mcp.proship.me/mcp' --transport streamable-http
mcp_servers:
me-proship-mcp-proship-mcp:
url: "https://mcp.proship.me/mcp" {
"McpServers": {
"me-proship-mcp-proship-mcp": {
"Transport": "http",
"Url": "https://mcp.proship.me/mcp"
}
}
} assistant mcp add me-proship-mcp-proship-mcp -t streamable-http -u 'https://mcp.proship.me/mcp'
{
"mcpServers": {
"me-proship-mcp-proship-mcp": {
"type": "http",
"url": "https://mcp.proship.me/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://mcp.proship.me/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.proship.me | CN=YE1,O=Let's Encrypt,C=US | 18 Aug 2026 | 16 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5d584955e32ff563ff6070100fb019d55f7 |
| SANs: mcp.proship.me | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.proship.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| me. | present | 45352 | 8 | Verified |
| proship.me. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.proship.me/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.proship.me/mcp | HTTPS enforced | 301 | https://mcp.proship.me/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_order ~24
Delete/cancel an order by id.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
No output schema declared.
No examples provided.
check_duplicate ~35
Check whether a customer phone number already has a recent order (duplicate-shipment guard).
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | Customer phone number |
No output schema declared.
No examples provided.
create_order ~194
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cod_amount | number | – | Optional: cash-on-delivery amount (THB) |
| customer | object | yes | – |
| products | array | – | Optional line items |
| ref_no | string | – | Optional: your own order reference |
| remarks | string | – | – |
| shipping_method | string | – | Default thaipost0 (EPS). thaipost requires a Thailand Post contract on your account. |
| shop_id | string | yes | Your shop id (see list_shops) |
| user | string | – | Optional: ProShip username. Normally decoded from your token automatically. |
| weight | number | yes | Parcel weight in grams |
No output schema declared.
No examples provided.
get_order ~40
Get one order by id (full pipe-suffixed id is fine). Returns status with Thai label and tracking number.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
No output schema declared.
No examples provided.
get_order_statuses ~43
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_orders ~64
List orders on YOUR account. Optional numeric status filter (see get_order_statuses). Paginated.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Default 1 |
| per_page | number | – | Default 50, max 100 |
| status | number | – | Optional status code filter |
No output schema declared.
No examples provided.
list_shops ~26
List the shops on YOUR ProShip account. Use the shop_id with create_order.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
print_label ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_ids | array | yes | FULL pipe-suffixed order ids |
| printer | string | – | Label format, default "proship" |
| size | string | – | Label size, default "normal" |
No output schema declared.
No examples provided.
signup ~147
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).
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | yes | Thai address, structured |
| display_name | string | – | Optional account display name (defaults to shop_name) |
| phone | string | yes | Thai mobile number for the shop, e.g. 0812345678 |
| shop_name | string | yes | Name of your shop (prints on labels) |
No output schema declared.
No examples provided.
track_parcel ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tracking_no | string | yes | Carrier tracking number, e.g. TH0139... |
No output schema declared.
No examples provided.
update_order_status ~50
Set an order status by numeric code (see get_order_statuses).
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
| status | number | yes | Status code, e.g. 5 = cancelled by seller |
No output schema declared.
No examples provided.
What is the ProShip Thailand Post MCP server?
ProShip Thailand Post is an MCP server listed in the public MCP registry as me.proship.mcp/proship-mcp. Create Thailand Post shipments, print labels, and track parcels in Thailand via ProShip. This page covers its hosted endpoint (https://mcp.proship.me/mcp).
Is the ProShip Thailand Post MCP server safe to use?
ProShip Thailand Post scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ProShip Thailand Post MCP server expose?
ProShip Thailand Post exposes 11 tools: track_parcel, get_order_statuses, signup, list_shops, create_order, and 6 more. Their descriptions and schemas cost roughly 797 tokens of context every time the server is loaded.
Does the ProShip Thailand Post MCP server require authentication?
No. We connected to ProShip Thailand Post without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ProShip Thailand Post MCP server still maintained?
ProShip Thailand Post is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.