Skip to content

NetCourier Parcel Tracking MCP server

io.github.zahidul-alam-m4/tracking-mcp-serverzahidul-alam-m4streamable-httpv1.0.0Scanned

MCP server for tracking parcels using the NetCourier tracking service.

3 tools: 3 only read.

Tools: 0 delete, 0 irreversible, 0 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 NetCourier Parcel Tracking MCP server can do

The NetCourier Parcel Tracking MCP server is published by the GitHub account zahidul-alam-m4. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool brings in text other people can write (list_tracking_systems).

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 20, 2026, version 1.0.0.

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.

3 tools

Only reads 3Show 3 read-only tools
  • get_delivery_proofGet proof-of-delivery details for a parcel: delivery/collection location and the recipient's signature, from a courier system.No findings

    Why it is in this group

    • The name "get_delivery_proof" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_parcel_trackingGet the latest tracking information / status / event history of a parcel (consignment) from a courier system.No findings

    Why it is in this group

    • The name "get_parcel_tracking" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_tracking_systemsList the tracking systems that are explicitly configured, and the default URL pattern used for other system names.Reads text others writeNo findings

    Why it is in this group

    • The name "list_tracking_systems" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List the tracking systems that are explicitly configured, and the default URL pattern used for other system names.

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 write1
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:13 UTC, unchanged since Nov 20, 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
0
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

Posture changes

  1. Nov 20, 2026
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Protocol version: none to 2025-06-18
  2. Nov 13, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Protocol version: 2025-06-18 to none

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.

  1. PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 200; tools/list served without credentials: no -> yes (and 1 more).View diff
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Protocol version: none to 2025-06-18
  2. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 1 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http tracking https://netcourier.app/mcp
claude mcp add --transport http tracking https://netcourier.app/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__tracking__list_tracking_systems",
      "mcp__tracking__get_parcel_tracking",
      "mcp__tracking__get_delivery_proof"
    ],
    "ask": [],
    "deny": []
  }
}

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 tracking. Review it before you use it.

Capability tags behind 1 rule
  • mcp__tracking__list_tracking_systems 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.github.zahidul-alam-m4/tracking-mcp-server/verify?hash=5d1acdb3108206a2e1c252bda0ccc55a78c00918d4d90eec376d14143c022620" | jq -e '.changed == false'

Pinned hash 5d1acdb31082, from Nov 20, 2026, 19:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.zahidul-alam-m4/tracking-mcp-server/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.zahidul-alam-m4/tracking-mcp-server
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.zahidul-alam-m4/tracking-mcp-server.svg)](https://radar.anlyon.com/servers/io.github.zahidul-alam-m4/tracking-mcp-server)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:52 UTC.

NetCourier Parcel Tracking MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the NetCourier Parcel Tracking MCP server safe?

No scan can promise that. What its definitions show: 3 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the NetCourier Parcel Tracking MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the NetCourier Parcel Tracking 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 NetCourier Parcel Tracking MCP server have?

3 tools: 3 read. list_tracking_systems, get_parcel_tracking and get_delivery_proof.

Does the NetCourier Parcel Tracking MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the NetCourier Parcel Tracking MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the NetCourier Parcel Tracking MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.