mcp-registry/io.github.baneado98/freight-pulse/record_performance / alternatives

Live alternatives to mcp-registry/io.github.baneado98/freight-pulse/record_performance

The best live alternatives to mcp-registry/io.github.baneado98/freight-pulse/record_performance right now are mcp-registry/vc.doomscore/doom/record_outcome, mcp-registry/io.github.edholofy/eyepup/eyepup_log, mcp-registry/com.aftership.mcp/tracking-public/track_shipment, pulsemcp/aftership-tracking/track_shipment, mcp-registry/io.github.lxxmng/container-loading/export_plan — capability-matched and ranked by current reliability. mcp-registry/io.github.baneado98/freight-pulse/record_performance itself is currently "healthy".

alternative	server
mcp-registry/vc.doomscore/doom/record_outcome	vc.doomscore/doom	live status →
mcp-registry/io.github.edholofy/eyepup/eyepup_log	io.github.edholofy/eyepup	live status →
mcp-registry/com.aftership.mcp/tracking-public/track_shipment	com.aftership.mcp/tracking-public	live status →
pulsemcp/aftership-tracking/track_shipment	AfterShip Tracking	live status →
mcp-registry/io.github.lxxmng/container-loading/export_plan	io.github.lxxmng/container-loading	live status →
mcp-registry/com.zobrx/zobrx/list_manifests	com.zobrx/zobrx	live status →
mcp-registry/xyz.lonestaroracle/mcp-server/supply_chain_intelligence	xyz.lonestaroracle/mcp-server	live status →
mcp-registry/io.github.pipeworx-io/postmark/delivery_stats	io.github.pipeworx-io/postmark	live status →
mcp-registry/io.github.meltingpixelsai/zero-core-verify/report_outcome	io.github.meltingpixelsai/zero-core-verify	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_reliability	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/io.github.meltingpixelsai/zero-core-budget/report_spend	io.github.meltingpixelsai/zero-core-budget	live status →
mcp-registry/io.github.tickadoo/tickadoo-mcp/report_quality_signal	io.github.tickadoo/tickadoo-mcp	live status →

FAQ

What is the best alternative to mcp-registry/io.github.baneado98/freight-pulse/record_performance?

mcp-registry/vc.doomscore/doom/record_outcome is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.edholofy/eyepup/eyepup_log, mcp-registry/com.aftership.mcp/tracking-public/track_shipment, pulsemcp/aftership-tracking/track_shipment, mcp-registry/io.github.lxxmng/container-loading/export_plan. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.baneado98/freight-pulse/record_performance down right now?

mcp-registry/io.github.baneado98/freight-pulse/record_performance's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.baneado98%2Ffreight-pulse%2Frecord_performance.

How does Glimind pick alternatives?

By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.baneado98%2Ffreight-pulse%2Frecord_performance or MCP find_alternatives. Check mcp-registry/io.github.baneado98/freight-pulse/record_performance's live status: https://glimind.com/tool/mcp-registry/io.github.baneado98/freight-pulse/record_performance.