NetCourier Parcel Tracking
REMOTE · NETCOURIER.APP · SCANNED OCT 8
MCP server for tracking parcels using the NetCourier tracking service.
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 3 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 Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 371 tokens (~123/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 NetCourier Parcel Tracking MCP server?
NetCourier Parcel Tracking is a hosted endpoint at https://netcourier.app/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 · netcourier.app
claude mcp add --transport http zahidul-alam-m4-tracking-mcp-server 'https://netcourier.app/mcp'
{
"mcpServers": {
"zahidul-alam-m4-tracking-mcp-server": {
"url": "https://netcourier.app/mcp"
}
}
} {
"servers": {
"zahidul-alam-m4-tracking-mcp-server": {
"type": "http",
"url": "https://netcourier.app/mcp"
}
}
} [mcp_servers.zahidul-alam-m4-tracking-mcp-server] url = "https://netcourier.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zahidul-alam-m4-tracking-mcp-server": {
"type": "remote",
"url": "https://netcourier.app/mcp",
"enabled": true
}
}
} openclaw mcp add zahidul-alam-m4-tracking-mcp-server --url 'https://netcourier.app/mcp' --transport streamable-http
mcp_servers:
zahidul-alam-m4-tracking-mcp-server:
url: "https://netcourier.app/mcp" {
"McpServers": {
"zahidul-alam-m4-tracking-mcp-server": {
"Transport": "http",
"Url": "https://netcourier.app/mcp"
}
}
} assistant mcp add zahidul-alam-m4-tracking-mcp-server -t streamable-http -u 'https://netcourier.app/mcp'
{
"mcpServers": {
"zahidul-alam-m4-tracking-mcp-server": {
"type": "http",
"url": "https://netcourier.app/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.
- 8 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 13. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Oct 26 64
First indexed and scored.
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 8 Oct 2026 · Probed https://netcourier.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=netcourier.app | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 1 Oct 2026 | 16 Apr 2027 | RSA 2048 | SHA256-RSA | 58ec7e0cd510ecd8eca9c0aef105634 |
| SANs: netcourier.app, *.netcourier.app | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of netcourier.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| netcourier.app. | 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://netcourier.app/mcp | Verified | 200 | |
| http (plaintext) | http://netcourier.app/mcp | HTTPS enforced | 301 | https://netcourier.app/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 →
get_delivery_proof ~177
Get proof-of-delivery details for a parcel: delivery/collection location and the recipient's signature, from a courier system. Use when the user asks where a parcel was delivered, who signed for it, or for proof of delivery / POD. Requires the system name, the tracking number, and a postcode (the collection or delivery postcode for that parcel) - if the postcode is not given or known from earlier in the conversation, ask the user for it rather than guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| postcode | string | yes | The collection or delivery postcode for this parcel, e.g. 'W14 0HN' |
| system | string | yes | Name of the tracking system, e.g. 'sparkle'. Lower-case sub-domain name only. |
| trackingNo | string | yes | The parcel tracking number, e.g. EX10004130651 |
No output schema declared.
No examples provided.
get_parcel_tracking ~164
Get the latest tracking information / status / event history of a parcel (consignment) from a courier system. Use when the user asks about a parcel, shipment, consignment or tracking number and mentions a system name (e.g. 'sparkle'). Extract the system name and the tracking number from the user's message. If the user separately asks for the delivery location or the signature/proof of delivery, use the get_delivery_proof tool instead (or afterwards) - it needs a postcode as well.
| Name | Type | Req | Description |
|---|---|---|---|
| system | string | yes | Name of the tracking system, e.g. 'sparkle' from 'in sparkle system'. Lower-case sub-domain name only. |
| trackingNo | string | yes | The parcel tracking number, e.g. EX10004130651 |
No output schema declared.
No examples provided.
list_tracking_systems ~30
List the tracking systems that are explicitly configured, and the default URL pattern used for other system names.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the NetCourier Parcel Tracking MCP server?
NetCourier Parcel Tracking is an MCP server listed in the public MCP registry as io.github.zahidul-alam-m4/tracking-mcp-server. MCP server for tracking parcels using the NetCourier tracking service. This page covers its hosted endpoint (https://netcourier.app/mcp).
Is the NetCourier Parcel Tracking MCP server safe to use?
NetCourier Parcel Tracking scores 67 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 NetCourier Parcel Tracking MCP server expose?
NetCourier Parcel Tracking exposes 3 tools: list_tracking_systems, get_parcel_tracking, get_delivery_proof. Their descriptions and schemas cost roughly 371 tokens of context every time the server is loaded.
Does the NetCourier Parcel Tracking MCP server require authentication?
No. We connected to NetCourier Parcel Tracking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the NetCourier Parcel Tracking MCP server still maintained?
NetCourier Parcel Tracking is still listed as active in the MCP registry. We last reached this channel on 8 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.