protogrid

Search / io.github.zahidul-alam-m4/tracking-mcp-server

NetCourier Parcel Tracking

R0· no sign-in

MCP server for tracking parcels using the NetCourier tracking service.

v1.0.0 · active · repository · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality79good
Trust94of 100
Uptime, 30 days100%
Latency p50522 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "tracking-mcp-server": {
      "type": "http",
      "url": "https://netcourier.app/mcp"
    }
  }
}
claude mcp add --transport http tracking-mcp-server https://netcourier.app/mcp
[mcp_servers.tracking-mcp-server]
url = "https://netcourier.app/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tracking-mcp-server": {
      "type": "remote",
      "url": "https://netcourier.app/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "tracking-mcp-server": {
      "type": "http",
      "url": "https://netcourier.app/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=tracking-mcp-server&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbmV0Y291cmllci5hcHAvbWNwIn0%3D"
}
{
  "servers": {
    "tracking-mcp-server": {
      "type": "http",
      "url": "https://netcourier.app/mcp"
    }
  }
}
{
  "mcpServers": {
    "tracking-mcp-server": {
      "httpUrl": "https://netcourier.app/mcp"
    }
  }
}
extensions:
  "tracking-mcp-server":
    enabled: true
    name: "tracking-mcp-server"
    type: streamable_http
    uri: "https://netcourier.app/mcp"
    timeout: 300

Quality 79 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene71 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • fail
    tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: list_tracking_systems (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_parcel_tracking (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_delivery_proof (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
  • pass
    tools.token_costabout 495 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
  • pass
    stability.changesno tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

3 tools, about 495 tokens to load them all · tool set 4c9d9dc19449 · checked 2026-10-19 10:52 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 94 / 100

provenance80
liveness100
freshness100
hygiene100

+repository +namespace-matches-repo +reachable +uptime-100% +updated-17d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://netcourier.app/mcp streamable-httpnoneyes100%522 ms2025-06-182026-10-19

Tools (3)

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

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "io.github.zahidul-alam-m4/tracking-mcp-server",
  "title": "NetCourier Parcel Tracking",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://netcourier.app/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.0",
  "repository": {
    "url": "https://github.com/zahidul-alam-m4/tracking-mcp-server",
    "source": "github"
  },
  "description": "MCP server for tracking parcels using the NetCourier tracking service."
}