Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Track ID icon

Track ID

Identify which carrier a tracking number belongs to from its format — length, prefix, and real checksums

Unify Dynamics LLC

Documentation
Tools9read-only
Sign-inNoneno account, no key
Data keptNoneprocessed in memory
PriceFreeoptional Pro limits
StatusLiveMCP + REST
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

What carrier is 1Z999AA10123456784 from?
Tools called
identify_carrier
Identify these five tracking numbers from my order history
Tools called
batch_identify_carriers
Does this look like a real tracking number?
Tools called
is_valid_tracking_format
What do the parts of this UPS tracking number mean?
Tools called
explain_tracking_number
What does a FedEx tracking number look like?
Tools called
carrier_format_info
What carriers can you identify?
Tools called
list_carriers
Give me an example UPS tracking number to test with
Tools called
generate_example_tracking_number
This could be FedEx or UPS — how do I tell which?
Tools called
disambiguation_tips
How does the UPS tracking number checksum work?
Tools called
checksum_algorithms

About

Trackid is a fully local carrier tracking-number format identifier. identify_carrier is the main tool: given a tracking number, it pattern-matches length, prefix and (for UPS 1Z and UPU S10 international postal numbers) a real checksum against a hand-curated table of publicly documented carrier formats, returning every match ranked by confidence. batch_identify_carriers runs the same over a list. is_valid_tracking_format gives a quick yes/no. explain_tracking_number breaks a number into its components (shipper code, service code, serial, check digit, origin-country code). carrier_format_info and list_carriers describe every format covered. generate_example_tracking_number returns a synthetic, correctly-checksummed test example. disambiguation_tips explains how to tell apart carriers sharing an identical numeric format. checksum_algorithms documents the two real checksum algorithms implemented. This never queries any carrier and cannot say where a package actually is — only which carrier(s) the format most likely belongs to. Keyless; fully local; zero upstream calls; nothing stored.

Sources: Hand-curated from publicly documented carrier tracking-number formats (USPS, FedEx, UPS, DHL, Amazon Logistics, OnTrac, Canada Post, Royal Mail) and the published UPU S10 international mail checksum standard; the UPS 1Z and UPU S10 checksum algorithms are implemented and verified against known-good example numbers. Fully local, zero upstream calls.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.
Privacy policyTerms

What it can do

9 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Identify a Tracking Number4 tools
  • Identify carrierIdentifies which carrier(s) a tracking number's FORMAT most likely belongs to, ranked by confidence (definite/likely/possible), including a real…
  • Batch identify carriersRuns identify_carrier over a list of tracking numbers at once.
  • Is valid tracking formatA quick yes/no on whether a string is shaped like ANY known carrier tracking number, without naming which one.
  • Explain tracking numberBreaks a tracking number down into its known components (shipper/service code, serial, check digit, origin-country code for international postal…
Reference3 tools
  • Carrier format infoFull detail on one carrier's tracking-number format(s): pattern, length, checksum type, confidence and a sample.
  • List carriersEvery carrier this reference covers, with how many distinct formats each has.
  • Generate example tracking numberGenerates a synthetic, correctly-formatted example tracking number for a named carrier (with a genuinely valid checksum where that carrier's…
How It Works2 tools
  • Disambiguation tipsExplains how to tell apart carriers whose tracking numbers share an identical length/shape (e.g. plain 12-digit numbers used by both FedEx and UPS…
  • Checksum algorithmsDocuments the two real, verifiable checksum algorithms this tool implements: UPS's 1Z modulus-10 check digit, and the UPU S10 international postal…

Information

PublisherUnify Dynamics LLC
CategoryEveryday life · Shopping
LanguagesEnglish
Built forGlobal
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://trackid.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide

More like this

Relo

A local home-moving toolkit — checklists, box/truck calculators, and a rough cost estimator

Live · MCP + REST10 tools

Flock

A hand-curated backyard bird ID guide — North America, India and Brazil

Live · MCP + REST10 tools

Gauge

Live US river and stream gauge data from USGS Water Services

Live · MCP + REST9 tools

Brew

A live brewery directory plus ABV/IBU/SRM/priming homebrew calculators and a 26-style beer guide

Live · MCP + REST10 tools

Knots

A hand-curated practical knot-tying reference — steps, strength ratings, uses and safety notes

Live · MCP + REST9 tools

Packlist

A fully local travel packing-list generator and airline baggage-rule reference

Live · MCP + REST10 tools

Documentation

Back to top

What Track ID is for

"What carrier is 1Z999AA10123456784 from?", "does this look like a real tracking number?", "what do the parts of this tracking number mean?" — a fully local carrier tracking-number format identifier that answers instantly from the number's shape alone, with no live lookup and no carrier account.

What it does

identify_carrier pattern-matches a tracking number's length, prefix and (for UPS 1Z numbers and international UPU S10 postal numbers) a real, verifiable checksum against a hand-curated table of publicly documented carrier formats — USPS, FedEx, UPS, DHL Express, DHL eCommerce, Amazon Logistics, OnTrac, Canada Post, Royal Mail, and other UPU-member postal services — returning every match ranked by confidence (definite/likely/possible). batch_identify_carriers runs the same check over a list. is_valid_tracking_format gives a quick yes/no. explain_tracking_number breaks a number into its known components: for a UPS number, the shipper number, service code, package serial and check digit; for an international postal number, the service indicator, serial digits, check digit and origin-country code. carrier_format_info and list_carriers describe every format covered. generate_example_tracking_number returns a synthetic, correctly-checksummed test example. disambiguation_tips explains how to tell apart carriers that happen to share an identical numeric format (a plain 12-digit number, for instance, could be FedEx Express or UPS Mail Innovations). checksum_algorithms documents exactly how the two implemented checksums — UPS's modulus-10 check digit and the UPU S10 international postal check digit — work.

What it is not

This is pure pattern-matching against a number's shape. It never calls any carrier's tracking API and cannot tell you where a package actually is, whether it has shipped, or its delivery status — only which carrier(s) publish a format that matches. Tracking-number formats occasionally overlap between carriers and carriers sometimes introduce new formats, so treat "likely" and "possible" matches as a strong hint, not a certainty — your order confirmation email naming the carrier is always the definitive source.

Privacy policy

Back to top

Track ID — Privacy Policy

Effective 25 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Track ID is. Track ID is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a carrier tracking-number format identifier — given a tracking number string, it identifies which carrier(s) it likely belongs to from length, prefix and (where a real algorithm applies) checksum. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup.

What we receive. The arguments of each tool call, the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Everything is answered from a bundled, hand-curated reference file and nothing is stored. No request is forwarded to any third party — there is no upstream call at all, live or otherwise — and no query is logged in request bodies, recorded, or used to train anything.

What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — the entire dataset is bundled with the server and answered locally. Hosting: Vercel (United States regions).

Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. Track ID is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Track ID — Terms of Service

Effective 25 September 2026. These terms govern use of the Track ID connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Track ID returns a carrier tracking-number format identifier — given a tracking number string, it identifies which carrier(s) it likely belongs to from length, prefix and (where a real algorithm applies) checksum. It is accessed through an AI assistant or directly over MCP or HTTP.
  2. General information, not professional advice. Track ID provides general, hand-curated reference information. It does not know your specific product, purchase, brand, or situation, and it is not a substitute for reading the manufacturer's or retailer's own materials, or for professional advice where relevant.
  3. Reference, not guaranteed-current. Content reflects general, widely published practice as of the build date stated in the Service's own data. Some figures, dates or rules change over time and vary by brand, retailer or region — always verify anything decision-critical against a primary source.
  4. Acceptable use. Automated use within the published rate limits is welcome.
  5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
  6. Data. Our Privacy Policy describes what we process. In short: your query is answered from a bundled reference file, and nothing is stored.
  7. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
  8. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss, injury, or damage arising from use of, or reliance on, the Service. Our total liability is limited to US $100.
  9. Governing law. California law; venue in San Mateo County, California.
  10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/trackid

Support

Back to top

Track ID support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Track ID never asks for them.

Get Track ID

Free · No sign-in · Read-only

Streamable HTTP, stateless, no authentication. Paste the endpoint into any MCP-capable agent.

https://trackid.connectorbay.com/mcp
{
  "mcpServers": {
    "trackid": {
      "type": "http",
      "url": "https://trackid.connectorbay.com/mcp"
    }
  }
}