Multi Carrier Tracking vs Server Everything
A side-by-side look at the Multi Carrier Tracking and Server Everything MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Multi Carrier Tracking for delivery work over a hosted endpoint; choose Server Everything for other tools and integrations as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Multi Carrier Tracking when
- You need dedicated capabilities in the Delivery domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
track_package, track_multiple, detect_carrier.
Choose Server Everything when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Delivery | Other Tools and Integrations |
| Quality signal | 43/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 91,486 |
| Directory activity | 2 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Multi Carrier Tracking | View Server Everything |
Tools & capabilities
Multi Carrier Tracking tools 5
track_packageCurrent status + event history for one package. Auto-detects carrier.track_multipleBatch tracking with per-package carrier auto-detection.detect_carrierIdentify which carrier a tracking number belongs to (with ambiguity candidates).list_carriersSupported carriers and their countries.subscribe_trackingWebhook subscription on status transitions.
Server Everything tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Multi Carrier Tracking
{
"mcpServers": {
"multi-carrier-tracking": {
"url": "https://multi-carrier-tracking-mcp.atlasword.workers.dev/mcp"
}
}
}
Server Everything
{
"mcpServers": {
"modelcontextprotocol-server-everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}
Frequently asked questions
Multi Carrier Tracking is categorized under Delivery and uses a remote HTTP/SSE transport. Server Everything belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick Multi Carrier Tracking for delivery work and Server Everything for other tools and integrations.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Multi Carrier Tracking has no declared pricing — check the project's own site. Server Everything is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add multi-carrier-tracking and modelcontextprotocol-server-everything as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Multi Carrier Tracking has a quality signal of 43/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Server Everything has 55/100 (Good) with 9 views, 0 installs and 91,486 GitHub stars.