# Ship24 > Ship24 is a parcel tracking API from Ship24 Limited in Hong Kong. Its REST API and hosted MCP server create trackers, return normalised tracking events across couriers and push updates by webhook. - Canonical: https://www.anchorterminal.com/tools/ship24 - Markdown: https://www.anchorterminal.com/tools/ship24.md (~8,200 tokens) - Slim: https://www.anchorterminal.com/tools/ship24.min.md (~2,030 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/ship24.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade C · 55/100 · rank #522 of 722 · #6 in Shipping & fulfilment · not agent-ready · confidence medium** ## Assessment The REST API and the hosted MCP server share one public OpenAPI 3.1 spec, numbered rate limits with Retry-After, and tracker creation that is idempotent by payload. No status page, SLA or security certification was found, API keys carry no scopes, and the API agreement and data processing agreement named in the terms aren't published. ## Facts | Field | Value | | --- | --- | | Vendor | Ship24 Limited (https://www.ship24.com) | | Kind | HTTP API | | Category | Shipping & fulfilment (https://www.anchorterminal.com/categories/shipping) | | Transport | HTTP | | Endpoint | `https://api.ship24.com/public/v1` | | Auth | API key · A self-serve API key, sent as `Authorization: Bearer apik_...`. A default key is created once a plan (free or paid) is chosen in the dashboard, and an account can hold up to 20 active keys. Keys have no scopes. The hosted MCP server takes the same key in the same header. No OAuth, partner review or sales approval is needed for the listed plans. | | Pricing | Freemium ($39 / mo) · Free for 10 shipments a month on the Tracking API, blocked at the limit, so an agent can start without a contract. Paid per-shipment plans start at $39 a month for 1,000 shipments with $0.045 for each extra. Per-call plans start at $99 a month for 10,000 calls with $0.015 for each extra. Above 1,000,000 shipments a month pricing is by sales. Whether the free plan needs a card wasn't established (checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the docs, the OpenAPI spec or the pricing page (checked 2026-10-08). | | Licence | Proprietary service under Ship24's Terms and Conditions. The Node SDK and the AI plugin on GitHub are MIT | | Tools exposed | 12 | | Packages | npm: `ship24` | | MCP registry name | `com.ship24/tracking-mcp` | | Source | https://github.com/ship24/ship24-node | | Docs | https://docs.ship24.com | | llms.txt | https://docs.ship24.com/llms.txt | | Last release | 2026-10-06 | | GitHub stars | 0 (as of 2026-10-08) | | npm downloads / week | 79 | | API | REST at https://api.ship24.com/public/v1, JSON, 12 operations. Create, bulk create (up to 100), list, get and update trackers, get results by tracker or tracking number, create and track in one call, per-call search, list couriers, resend webhooks and download webhook history | | MCP server | Hosted at https://api.ship24.com/mcp, Streamable HTTP, Bearer API key, version 1.0.1. 12 tools (create_tracker, bulk_create_trackers, track, list_trackers, get_tracker, update_tracker, get_tracking_results, search_tracking_by_number, get_couriers, search_tracking, resend_webhooks, download_webhook_history), registered by the plan on the key | | Credentials | API key (`apik_...`) as a Bearer token. Up to 20 active keys an account, managed in the dashboard. No scopes | | Getting access | Self-serve signup at dashboard.ship24.com. A plan, free or paid, must be chosen before the default key is created | | Testing | No separate sandbox. The free plan and sample tracking numbers (SHIP24_SAMPLE__000) simulate each of the eight status milestones | | Rate limits | A second, per endpoint. 10 on most, 3 on `POST /trackers/bulk`, 1 on `GET /couriers` and on webhook resend. `RateLimit-*`, `X-RateLimit-*` and `Retry-After` headers | | Lists | `GET /trackers` takes `page`, `limit` (default 100, maximum 500) and `sort`. `GET /couriers` returns the whole list | | Errors | JSON `errors` array of `code` and `message`. 12 documented codes, among them validation_error, quota_limit_reached, no_active_subscription, tracker_conflict and request_conflict (409) | | Idempotency | `POST /trackers` and `POST /trackers/track` reuse the tracker for an identical payload. Any changed field creates a new tracker. `clientTrackerId` is unique across subscribed trackers. Bulk create isn't fully idempotent | | Statuses | `statusMilestone` on every event (pending, info_received, in_transit, out_for_delivery, failed_attempt, available_for_pickup, delivered, exception), plus `statusCategory` and `statusCode` | | Webhooks | One URL set in the dashboard. A static secret in the `Authorization` header, up to 20 retries with exponential backoff, replay by tracker, sent from 54.161.7.2. Order isn't guaranteed | | Limits | Tracking numbers of 5 to 50 characters. Up to three courier codes a request and nine a shipment. Trackers with a shipping date more than 180 days old are rejected | | Plans | Per shipment, Free (10 a month), Pro from $39 for 1,000 to 1,000,000 a month, Enterprise by sales. Per call, from $99 for 10,000 calls to $5,999 for 1.5 million. Monthly billing only, by card through Stripe | | Add-ons | Shipment Dashboard from $10 a month, Proof of Delivery, AI Predictive Delivery Date and AI Analytics at $9 a month each, first month free | | SDK and plugin | `ship24` on npm, 1.1.0 (6 October 2026), Node 18+, no runtime dependencies, MIT. ship24-ai-plugin 1.0.0 (9 September 2026) with eight skills. An n8n node is also in the vendor's GitHub account | | Support | Contact form on ship24.com. Dedicated customer support is listed from the Pro plan | | Capabilities | shipping.tracking | | Tags | hosted, closed-source, api-key, openapi, llms-txt, mcp, webhooks, free-tier, typescript, tracking | | JSON | https://www.anchorterminal.com/api/v1/tools/ship24.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 45 | 9.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 81 | 13.2 | | Agent ergonomics | 13% | 16.2 | 68 | 11.1 | | Security & auth | 14% | 17.5 | 37 | 6.5 | | Payments & pricing | 10% | 12.5 | 30 | 3.8 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 80 | 7.0 | | Transparency & trust (editorial 38, provenance 65) | 7% | 8.8 | 52 | 4.5 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **55 → C** | ### Why each score - Reliability 45: Read with the hosted lines and scored on the REST API at `api.ship24.com/public/v1`, which the hosted MCP server wraps. No status page was found. `status.ship24.com` doesn't resolve, `ship24.statuspage.io` is inactive, and neither the site footer nor the docs link to one (0). With no readable incident history the record scores the default (5 of 30). The rate limiter page gives a number for each of 11 endpoints, from 1 request a second on `GET /couriers` to 10 on most others (15). Responses carry `RateLimit-*`, `X-RateLimit-*` and `Retry-After` headers, which we saw on a live response, the errors page recommends exponential backoff on 429, and tracker creation is documented as idempotent with a 409 `request_conflict` that can be retried (15). The terms supply the service as is and as available, with no SLA found for any plan (0). The path is `/public/v1` and the MCP server reports version 1.0.1, with no beta label (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 81: A public OpenAPI 3.1 spec at `docs.ship24.com/assets/openapi/ship24-tracking-api.yaml` covers 12 operations and two webhooks, and every MCP tool has a typed input and output schema (25). llms.txt and a hosted `SKILL.md` guide exist, but the docs pages have no Markdown copies and llms.txt truncates its descriptions (8 of 10). The MCP tool descriptions say when to use each tool and which to prefer, such as `search_tracking_by_number` before a billed lookup, and the docs explain the three ways to fetch results (18 of 20). Inputs are typed with required fields, 12 enums and limits such as 5 to 50 characters for a tracking number and 500 a page, though the `Authorization` header is modelled as a plain string parameter (12 of 15). The spec has many examples and the errors page lists 12 codes, but most operations document only their success response and the live `auth_missing_header` code isn't on the list (10 of 15). The path carries v1 and the data format page promises that fields are never removed and lists four deprecated fields with months. No API changelog was found, only the SDK and plugin changelogs (8 of 15). - Agent ergonomics 68: Scored on the REST API and the MCP server together. The MCP server has 12 tools, registered by plan, but its tools/list answer is about 61 KB because every tool carries an output schema, and the REST API has no field selection, so a results call returns every event (13 of 25). `GET /trackers` pages by `page` and `limit` (default 100, maximum 500) with a sort order. No filter appears in the spec for that call, and `GET /couriers` returns the full list unpaged (12 of 20). Errors are a JSON `errors` array with a stable `code` and a message that says what to fix, with 12 documented codes (16 of 20). `POST /trackers` and `POST /trackers/track` are idempotent for an identical payload, `clientTrackerId` is validated as unique, the bulk call is documented as not fully idempotent, and all 12 MCP tools carry `readOnlyHint` or `destructiveHint` and `idempotentHint` annotations (18 of 20). Only `trackingNumber` is required and the courier is detected automatically. One official SDK exists, for Node.js and TypeScript, so the two-language line isn't met (9 of 15). - Security & auth 37: API keys are sent as a Bearer token in the `Authorization` header. An account can hold up to 20, managed in the dashboard, and the plugin's security note advises a dedicated key so it can be revoked alone. Keys have no scopes and no secret travels in a query string (20 of 30). No read-only key or approval step was found. The API has no delete operation, the MCP server registers tools by plan and marks `resend_webhooks` as destructive, and that is the only least-privilege control (5 of 20). Results carry courier event text, which is untrusted, and no prompt-injection guidance was found in the docs or the plugin (3 of 15). `GET /trackers/:trackerId/webhook-history/download` returns every webhook push with its response, but no log of API calls or key use was found (4 of 15). `SECURITY.md` in the plugin repository gives contact@ship24.com for reports on the API and MCP server. No security.txt, bug bounty, SOC 2 or ISO 27001 statement was found, and webhooks are checked by a static shared secret with no signature (5 of 20). - Payments & pricing 30: Read with the hosted rubric. No x402, MPP or L402 was found in the docs, the spec or the pricing page (0). The pricing page lists both billing models without a login, per shipment from $39 a month for 1,000 with $0.045 for each extra shipment, and per call from $99 a month for 10,000 with $0.015 for each extra call, with every tier and overage rate in a table (20). The Tracking API has a free plan of 10 shipments a month. Whether signup asks for a card wasn't established, because the dashboard needs a login we didn't create (10 of 20). A person signs up and picks a plan in the dashboard, and API key creation isn't available through the API or the MCP server (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 80: The `ship24` npm package reached 1.1.0 on 6 October 2026, two days before the check (30). In the 90 days before the check there were five dated releases, the Node SDK 1.0.0 on 14 July and 1.1.0 on 6 October, MCP server 1.0.0 on 16 July and 1.0.1 on 27 August in the official registry, and the AI plugin 1.0.0 on 9 September (20). The service is closed, with no API changelog. Support is a contact form, and the GitHub API shows four open issues on the SDK repository and two on the plugin, which we didn't read (6 of 15). The MCP server is in the official registry under the domain namespace `com.ship24/tracking-mcp` (15). The SDK has no runtime dependencies, CI that tests Node 20, 22 and 24, and a workflow that reports drift from the OpenAPI spec (9 of 10). - Transparency & trust 52: The service is closed, under Terms and Conditions that name Ship24 Limited of Hong Kong and carry no date or version. They say an Application developer and API agreement applies to API use, and we found no such document on the site. The SDK and plugin are MIT (12 of 30). The privacy policy, last updated August 2026, covers accounts, payments and the MCP integration and gives retention only in general terms. The pricing page lists six months of data retention on the Pro plan, the terms allow deletion of an account's data without notice, and the data processing agreement the terms refer to wasn't found (12 of 30). The data format page promises that existing fields are never removed or changed and lists deprecated fields with the month, most recently `signedBy` in August 2026. No notice period is stated (10 of 20). Stripe, Google and Meta are named in the privacy policy, with no subprocessor list and no hosting locations (4 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (21 items): https://www.anchorterminal.com/fixes/ship24.md (JSON https://www.anchorterminal.com/fixes/ship24.json) ### What we couldn't check - unchecked: whether the free plan asks for a card. The dashboard at dashboard.ship24.com needs an account, and we didn't sign up. - unchecked: API key rotation and revocation in the dashboard. The docs say keys are viewed and managed there, and the plugin's security note says a key can be revoked. - unchecked: GitHub issues on ship24-node (four open) and ship24-ai-plugin (two open), and how quickly they are answered. - No status page was found. status.ship24.com failed to resolve from two readers and ship24.statuspage.io redirects to an inactive page. Ship24 may publish one at an address we didn't find. - The Application developer and API agreement and the Ship24 Data Processing Agreement named in the terms were not found on the site, so `provenance.terms` points at the Terms and Conditions. - The Terms and Conditions carry no effective date or version. - A second registry entry, io.github.ship24-official/ship24-tracking, describes a stdio server from a different GitHub account. We didn't establish whether Ship24 runs that account and left it out. - The listing covers the Tracking API. Ship24's tracking pages, delivery notifications, IOSS and Ship from China services have no API in the reviewed documentation. - Courier count (2,500+) is the vendor's figure. We didn't fetch `GET /couriers`, which needs a key. ### Sources - home page: (seen 2026-10-08) - Tracking API pricing, per-shipment and per-call tables: (seen 2026-10-08) - Tracking API product page: (seen 2026-10-08) - about page, offices: (seen 2026-10-08) - Terms and Conditions: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - docs llms.txt: (seen 2026-10-08) - getting started, API keys: (seen 2026-10-08) - AI integration page, plugin and MCP server: (seen 2026-10-08) - hosted integration skill: (seen 2026-10-08) - OpenAPI 3.1 spec: (seen 2026-10-08) - rate limiter: (seen 2026-10-08) - error management: (seen 2026-10-08) - trackers: (seen 2026-10-08) - data format, API evolution and deprecated fields: (seen 2026-10-08) - couriers: (seen 2026-10-08) - statuses and sample tracking numbers: (seen 2026-10-08) - per-call API: (seen 2026-10-08) - webhook authentication: (seen 2026-10-08) - webhook sending behaviour, retries and IPs: (seen 2026-10-08) - support: (seen 2026-10-08) - MCP endpoint, initialize and tools/list without a key: (seen 2026-10-08) - REST API response without a key (400, rate limit headers): (seen 2026-10-08) - official MCP registry search: (seen 2026-10-08) - AI plugin repository, README, SECURITY.md, changelog: (seen 2026-10-08) - Node SDK repository, README, changelog, CI: (seen 2026-10-08) - vendor repositories: (seen 2026-10-08) - npm package: (seen 2026-10-08) - npm weekly downloads: (seen 2026-10-08) - security.txt (404): (seen 2026-10-08) - Statuspage address (inactive): (seen 2026-10-08) - domain registration (RDAP): (seen 2026-10-08) ## Who's behind it (provenance 65/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Ship24 Limited | 20/20 | | Domain age | ship24.com, registered 2005-09-18 (21 years) | 15/15 | | Endpoint on the vendor's domain | api.ship24.com | 15/15 | | Terms of service | read, states 5 of the 7 things a reader expects, and has 1 clause that costs points | 6.3/10 | | Privacy policy | read, states 6 of the 8 things a reader expects | 8.5/10 | | Status page | not found | 0/10 | | Changelog | not found | 0/10 | | security.txt | not found | 0/10 | The Terms and Conditions say Ship24 Limited, a company registered in Hong Kong, is the party called Ship24, and place disputes with the courts of Hong Kong. They carry no date or version. The terms govern accounts, fees and the API, and say an Application developer and API agreement and a Data Processing Agreement also apply. Neither document was found on the site. The privacy policy was last updated in August 2026 and has a section on the MCP integration. It names UAB Clefino of Lithuania as a group company for the IOSS service. The about page lists offices in Hong Kong, Tremblay-en-France and Vilnius. www.ship24.com, docs.ship24.com and api.ship24.com have no security.txt. SECURITY.md in ship24-ai-plugin gives contact@ship24.com for reports. No status page and no API changelog were found. The Node SDK and the plugin each keep a CHANGELOG.md on GitHub. RDAP for ship24.com gives a registration date of 2005-09-18. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.ship24.com/terms), read 2026-10-08, gives no date, states 5 of the 7 things a reader expects. - To know. Restricts benchmarking or competitive use (costs points). "(o) not to use or access the Service in order to monitor the availability, performance or functionality of the Service or for any other similar benchmarking purposes;" - To know. Says access can be ended without notice or for any reason. "Ship24 reserves the right in its sole discretion to terminate Your Account, delete Your profile and any of Your Data and restrict Your use of all or any part of the Service for any or no reason, without notice, and without liability to you or anyone else." - Not found in the text. Gives the date it was last updated. - Names the governing law or courts. The law of Hong Kong. - States a limit on its liability. Capped at the fees paid in the 12 months before the claim. - Says how changes to the terms are announced. Changes are posted, with no other notice named. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). Use of the service through a third-party AI assistant or agent platform is also governed by that platform's terms, and the section 3.4 restrictions apply to such access. "Your access to and use of the Service through any AI Platform is additionally governed by that AI Platform's own terms of use and policies." - Also in the text (2026-10-08). Ship24 may treat an account as inactive and permanently delete it and its data when the user has not logged in for 12 or more months. "If User does not log in to the Account for 12 or more months, Ship24 may treat the Account as "inactive" and permanently delete the Account, Your Data and any other data associated with it." - Also in the text (2026-10-08). Ship24 may use, combine, disclose, analyse and create derivative works of anonymised data, which includes customer data with identifying information removed. "Ship24 shall be authorized to use, combine, disclose, analyze and create derivative works of all Anonymized Data." **Privacy policy** (https://www.ship24.com/privacy-policy), read 2026-10-08, dated 2026-08-01, states 6 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2026-08-01. - Not found in the text. Says what personal data is collected. - Says how long data is kept. For as long as needed, with no period named. - Not found in the text. Says whether personal data is sold or shared for advertising. - Also in the text (2026-10-08). Queries made through a third-party AI assistant and Ship24's responses pass through that platform, whose own privacy policy governs the conversation data. "Third-party platform: your query and Ship24's response pass through the AI assistant platform (e.g., OpenAI) as part of that conversation." ## Live (updated 2026-10-08 21:53 UTC) - Right now: up, HTTP 404, 252 ms, checked 2026-10-08 21:53 UTC (get on `https://api.ship24.com/public/v1`) - Uptime 24h 100.0% (28 probes) · 30 days 100.0% (28 probes) · p50 252 ms · p95 369 ms - Always current: https://www.anchorterminal.com/api/v1/live/ship24.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Tracking API Pro, 1,000 shipments | $39 | per month (plan) | $0.039 a shipment; tiers up to 1,000,000 a month | | Extra tracked shipment | $0.045 | per transaction | on the 1,000 tier; $0.010 on the 1,000,000 tier | | Per-call plan, 10,000 calls | $99 | per month (plan) | separate subscription for `POST /tracking/search` | | Extra per-call lookup | $0.015 | per call | on the 10,000 tier; $0.007 on the 1.5 million tier | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Public OpenAPI 3.1 spec with 12 operations and two webhook definitions, plus llms.txt and a hosted `SKILL.md` integration guide - Hosted MCP server at `https://api.ship24.com/mcp` with 12 tools, each carrying read-only, destructive and idempotent annotations and an output schema - Rate limits are published per endpoint (1 to 10 requests a second) with `RateLimit-*`, `X-RateLimit-*` and `Retry-After` headers - `POST /trackers` and `POST /trackers/track` are idempotent for an identical payload, and `clientTrackerId` is checked for uniqueness - Prices are public for both billing models, with a free API plan of 10 shipments a month and sample tracking numbers for each status ## Weaknesses - No status page was found. `status.ship24.com` doesn't resolve, and neither the site nor the docs link to one - The terms supply the service as is, with no uptime commitment, and allow account termination and data deletion without notice - API keys have no scopes or read-only mode. The docs describe up to 20 keys an account, managed in the dashboard - Webhooks are authenticated by a static secret in the `Authorization` header, with no payload signature - The API agreement and the data processing agreement named in the terms, and a subprocessor list, were not found on the site ## Before you call it (notes for agents) 1. Send `Authorization: Bearer apik_...` to `https://api.ship24.com/public/v1`. The same key works on the MCP server, which lists tools without a key but answers 401 on calls 2. Store the `trackerId` or set a unique `clientTrackerId`. Tracking numbers aren't unique, and any changed field on a repeat `POST /trackers` creates a second tracker that uses quota 3. Allow up to 60 seconds for the first `POST /trackers/track` or `POST /tracking/search` call, since results are fetched from the courier synchronously 4. Cache `GET /couriers`. It is limited to one request a second and returns the whole courier list, and courier auto-detection usually makes `courierCode` unnecessary 5. Check for `quota_limit_reached` and `no_active_subscription`. `POST /tracking/search` needs a separate per-call plan, and the free plan blocks at 10 shipments a month ## Connect Install: ```bash npm install ship24 ``` First request: ```bash curl -sS -X POST https://api.ship24.com/public/v1/trackers/track \ -H "Authorization: Bearer $SHIP24_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "trackingNumber": "SHIP24_SAMPLE_DELIVERED_000" }' ``` Claude Code: ```bash claude mcp add --transport http ship24-tracking https://api.ship24.com/mcp -H "Authorization: Bearer apik_your_key_here" ``` MCP client configuration: ```json { "mcpServers": { "ship24-tracking": { "headers": { "Authorization": "Bearer apik_your_key_here" }, "type": "http", "url": "https://api.ship24.com/mcp" } } } ``` Through letme (picks today, calling later): https://letme.dev/ship24. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Easyship | B | 68.8 | 173 | shipping.tracking | no | https://www.anchorterminal.com/tools/easyship.md | | Sendcloud | B | 62 | 352 | shipping.tracking | no | https://www.anchorterminal.com/tools/sendcloud.md | | Shippo | C | 61.9 | 355 | shipping.tracking | no | https://www.anchorterminal.com/tools/shippo.md | | ShipBob | C | 60.8 | 387 | shipping.tracking | no | https://www.anchorterminal.com/tools/shipbob.md | | ShipStation API | C | 59.3 | 433 | shipping.tracking | no | https://www.anchorterminal.com/tools/shipstation.md | | EasyPost | C | 54.3 | 531 | shipping.tracking | no | https://www.anchorterminal.com/tools/easypost.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The hosted MCP server at https://api.ship24.com/mcp lists 12 tools without a key and answers calls only with one. Each tool has annotations and an output schema (source: ) - The server is in the official MCP registry as com.ship24/tracking-mcp, version 1.0.1 published 27 August 2026 (source: ) - ship24-ai-plugin packages eight skills, a read-only integration reviewer agent and the MCP configuration for Claude Code, Cursor, Codex, Gemini CLI and Copilot (source: ) - Two billing models with separate endpoints. Per-shipment plans use trackers and webhooks, and per-call plans use `POST /tracking/search`, which fetches from the courier on each call (source: ) - Sample tracking numbers such as SHIP24_SAMPLE_DELIVERED_000 simulate each status milestone for testing (source: ) - Ship24 says it covers more than 2,500 couriers and third-party logistics firms, with the courier detected from the tracking number (source: ) - Section 7.5 of the terms covers access through AI platforms by MCP and applies the same usage restrictions (source: ) - No status page was found. status.ship24.com doesn't resolve and ship24.statuspage.io is inactive (checked 2026-10-08) ## Compare - [EasyPost vs Ship24](https://www.anchorterminal.com/compare/easypost-vs-ship24.md): C 54.3 vs C 55 - [Easyship vs Ship24](https://www.anchorterminal.com/compare/easyship-vs-ship24.md): B 68.8 vs C 55 - [Karrio vs Ship24](https://www.anchorterminal.com/compare/karrio-vs-ship24.md): D 48.7 vs C 55 - [Sendcloud vs Ship24](https://www.anchorterminal.com/compare/sendcloud-vs-ship24.md): B 62 vs C 55 - [Ship24 vs ShipBob](https://www.anchorterminal.com/compare/ship24-vs-shipbob.md): C 55 vs C 60.8 - [Ship24 vs Shippo](https://www.anchorterminal.com/compare/ship24-vs-shippo.md): C 55 vs C 61.9 - [Ship24 vs ShipStation API](https://www.anchorterminal.com/compare/ship24-vs-shipstation.md): C 55 vs C 59.3 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on ship24.com or one of its subdomains, or the README of github.com/ship24/ship24-node. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "ship24", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Ship24 on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Ship24 on Anchor Terminal](https://www.anchorterminal.com/badges/ship24.svg)](https://www.anchorterminal.com/tools/ship24) ``` Plain link: ```html Ship24 on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Ship24 is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/ship24-dark.png - Light: https://www.anchorterminal.com/assets/share/ship24-light.png