Server Everything vs Multi Carrier Tracking
A side-by-side look at the Server Everything and Multi Carrier Tracking MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Server Everything for other tools and integrations work as a local process; choose Multi Carrier Tracking for delivery over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Other Tools and Integrations | Delivery |
| Quality signal | 55/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 91,486 | 0 |
| Directory activity | 9 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Server Everything | View Multi Carrier Tracking |
Tools & capabilities
Server Everything tools
No tool names declared yet. Check the project README from the listing page.
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.
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.
Server Everything
{
"mcpServers": {
"modelcontextprotocol-server-everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}
Multi Carrier Tracking
{
"mcpServers": {
"multi-carrier-tracking": {
"url": "https://multi-carrier-tracking-mcp.atlasword.workers.dev/mcp"
}
}
}
Frequently asked questions
Server Everything is categorized under Other Tools and Integrations and uses a local stdio subprocess. Multi Carrier Tracking belongs to Delivery and uses a remote HTTP/SSE transport. Pick Server Everything for other tools and integrations work and Multi Carrier Tracking for delivery.
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.
Server Everything is listed as free. Auth: no auth required. Multi Carrier Tracking has no declared pricing — check the project's own site. 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 modelcontextprotocol-server-everything and multi-carrier-tracking as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Server Everything has a quality signal of 55/100 (Good) with 9 views, 0 installs and 91,486 GitHub stars. Multi Carrier Tracking has 43/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.