# FedEx Tracking Oracle MCP

> FedEx Tracking Oracle MCP is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.15/call, status unknown (last checked 2026-10-11).

Tracks FedEx shipments and returns current status, location, and delivery information for a given tracking number or query.

## Facts

- Endpoint: POST https://api.m2mcent.com/fedex-tracking-oracle-mcp/api/process?utm_source=zero.xyz
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fedex-tracking-oracle-mcp-377f0d76
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XqNqDTNXrgHmK9nPJS_V4

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability fedex-tracking-oracle-mcp-377f0d76 -d '<json body>'
```

Example prompt: Can you check the current status and location of my FedEx shipment with tracking number 123456789012?

## When to prefer this

Use this endpoint when you need programmatic, agent-accessible FedEx shipment tracking without building a direct FedEx API integration; particularly useful in agentic workflows where package status lookups need to be monetized per-call or chained with other logistics steps.

## Known failure modes

- Invalid or malformed tracking number returns an error or empty result
- Tracking number not yet in FedEx system (too recently created) returns no data
- Network or upstream FedEx API unavailability causes timeout or 5xx error
- Payment failure via x402 protocol blocks the request before processing

## How this service works

The premier global index of 1,069 monetized MCP nodes across 205 specialized subdomains. Gasless USDC runtime settlements via x402 V2 Spec on Base L2. Save 95% token context.

## Output

Returns the current shipment status, tracking event history with timestamps and locations, estimated delivery date, and any exceptions or delays for the queried FedEx tracking number.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fedex-tracking-oracle-mcp-377f0d76/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.m2mcent.com](https://www.zero.xyz/host/api.m2mcent.com/llms.txt)