TrackingMore MCP by usefulapi
io.usefulapi/trackingmoreusefulapi.iostreamable-httpv1.27.4Scanned
Track parcels with TrackingMore: detect couriers, create and read trackings, delivery status.
7 tools: 3 can delete or cancel things and 4 only read.
- Reads private data · 0
- Reads text others write · 7
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the TrackingMore MCP by usefulapi can do
The TrackingMore MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 7 tools. It can delete or cancel things (3 tools: trackingmore_create_tracking, trackingmore_update_tracking and trackingmore_delete_tracking). 4 tools only read.
7 tools bring in text other people can write (trackingmore_list_couriers, trackingmore_detect_courier, trackingmore_list_trackings and 4 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.27.4.
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.
7 tools
Deletes or cancels 3Claude Code: deny
trackingmore_create_trackingWRITE: register ONE shipment so TrackingMore starts tracking it.Reads text others writeNo findings
Why it is in this group
- The name "trackingmore_create_tracking" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it WRITE: register ONE shipment so TrackingMore starts tracking it. This uses one credit of the account's plan (credits beyond the plan are billed by TrackingMore as overage): confirm with the user before creating, and never create trackings in bulk. Fails with 'Tracking No. already exists' if it is already registered. Needs the tracking number and the courier code (use trackingmore_detect_courier if unknown). Some couriers need extra fields (postal code, ship date, key). Returns the new tracking with its id. POST /trackings/create.
Annotations the server declares
- title: Register a shipment for tracking
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
trackingmore_delete_trackingWRITE (destructive): permanently remove one tracking from the TrackingMore account by id.Reads text others writeNo findings
Why it is in this group
- The name "trackingmore_delete_tracking" says "delete": a word for removing or ending something.
- The description says "permanently remove".
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it WRITE (destructive): permanently remove one tracking from the TrackingMore account by id. Its checkpoint history is lost; registering the shipment again later uses another credit. Confirm with the user first. DELETE /trackings/delete/{id}.
Annotations the server declares
- title: Delete a tracking
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
trackingmore_update_trackingWRITE: change the descriptive fields of a registered tracking (order number, customer name/email, title, note, label, language, postal code, ship date ...).Reads text others writeNo findings
Why it is in this group
- The name "trackingmore_update_tracking" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it WRITE: change the descriptive fields of a registered tracking (order number, customer name/email, title, note, label, language, postal code, ship date ...). Only the fields you pass change; the tracking number and courier cannot be changed here. PUT /trackings/update/{id}.
Annotations the server declares
- title: Update a tracking
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
Only reads 4Show 4 read-only tools
trackingmore_detect_courierFind which couriers a tracking number most likely belongs to (returns matching courier codes and names).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "find": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Find which couriers a tracking number most likely belongs to (returns matching courier codes and names). Use the code with trackingmore_create_tracking. Does not create anything. POST /couriers/detect.
Annotations the server declares
- title: Detect courier
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
trackingmore_get_trackingThe full tracking record of one shipment already registered in the account, including every checkpoint (origin_info / destination_info trackinfo with date, status, details and loca…Reads text others writeNo findings
Why it is in this group
- The name "trackingmore_get_tracking" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The full tracking record of one shipment already registered in the account, including every checkpoint (origin_info / destination_info trackinfo with date, status, details and location). Look it up by tracking number; add courier_code if the number is used by several couriers. A number that was never registered is not found: register it with trackingmore_create_tracking first. GET /trackings/get?tracking_numbers=.
Annotations the server declares
- title: Get a shipment's tracking
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
trackingmore_list_couriersList the carriers TrackingMore supports with their courier_code, name, country, website, phone and the extra fields some of them need.Reads text others writeNo findings
Why it is in this group
- The name "trackingmore_list_couriers" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "list" and "website": it reads web pages, which anyone can write.
Description, as the server wrote it List the carriers TrackingMore supports with their courier_code, name, country, website, phone and the extra fields some of them need. The full list is long (1,000+), so filter with `search` (matches name or code) and/or `country`; replies hold at most `limit` couriers. GET /couriers/all.
Annotations the server declares
- title: List supported couriers
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
trackingmore_list_trackingsList the shipments already registered in the TrackingMore account, newest first as the API returns them: id, tracking number, courier, delivery_status (pending, notfound, transit, …Reads text others writeNo findings
Why it is in this group
- The name "trackingmore_list_trackings" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List the shipments already registered in the TrackingMore account, newest first as the API returns them: id, tracking number, courier, delivery_status (pending, notfound, transit, pickup, delivered, undelivered, exception, expired, inforeceived), latest event and milestone dates. Checkpoint lists are left out (use trackingmore_get_tracking for one shipment's full history). Filters: tracking numbers, courier, delivery status, created/updated date range. GET /trackings/get.
Annotations the server declares
- title: List trackings
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
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 outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write7
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- 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:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- 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
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://trackingmore.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://trackingmore.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
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.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://trackingmore.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://trackingmore.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.27.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http trackingmore https://trackingmore.usefulapi.io/mcpclaude mcp add --transport http trackingmore https://trackingmore.usefulapi.io/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__trackingmore__trackingmore_list_couriers",
"mcp__trackingmore__trackingmore_detect_courier",
"mcp__trackingmore__trackingmore_list_trackings",
"mcp__trackingmore__trackingmore_get_tracking"
],
"ask": [],
"deny": [
"mcp__trackingmore__trackingmore_create_tracking",
"mcp__trackingmore__trackingmore_update_tracking",
"mcp__trackingmore__trackingmore_delete_tracking"
]
}
}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 trackingmore. Review it before you use it.
Capability tags behind 7 rules
- mcp__trackingmore__trackingmore_list_couriers untrusted-input
- mcp__trackingmore__trackingmore_detect_courier untrusted-input
- mcp__trackingmore__trackingmore_list_trackings untrusted-input
- mcp__trackingmore__trackingmore_get_tracking untrusted-input
- mcp__trackingmore__trackingmore_create_tracking untrusted-input
- mcp__trackingmore__trackingmore_update_tracking untrusted-input
- mcp__trackingmore__trackingmore_delete_tracking untrusted-input
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/io.usefulapi/trackingmore/verify?hash=eb943bc2422e1ba7f76427e65ae2c054f051fadbe383ad351ab2dd5d16ada32d" | jq -e '.changed == false'Pinned hash eb943bc2422e, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/trackingmore/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/trackingmore)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.
TrackingMore MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the TrackingMore MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 7 tools, 3 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 TrackingMore MCP by usefulapi delete data?
- Yes. 3 tools can delete, cancel or revoke something: trackingmore_create_tracking, trackingmore_update_tracking and trackingmore_delete_tracking.
Can the TrackingMore MCP by usefulapi 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 TrackingMore MCP by usefulapi have?
- 7 tools: 3 destructive, 4 read. trackingmore_create_tracking, trackingmore_update_tracking, trackingmore_delete_tracking, trackingmore_list_couriers, trackingmore_detect_courier, trackingmore_list_trackings and trackingmore_get_tracking.
Does the TrackingMore MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the TrackingMore MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the TrackingMore MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.