mcp-registry/io.github.foundrynet/forge-mcp/correct_mapping / alternatives

Live alternatives to mcp-registry/io.github.foundrynet/forge-mcp/correct_mapping

The best live alternatives to mcp-registry/io.github.foundrynet/forge-mcp/correct_mapping right now are mcp-registry/io.github.benseverndev-oss/goldenmatch/add_correction, mcp-registry/vc.doomscore/doom/supersede_calibration_case, mcp-registry/io.github.benseverndev-oss/infermap/validate, mcp-registry/io.github.benseverndev-oss/infermap/map, mcp-registry/io.corpusiq/multi-source-mcp/canonical_facts_set — capability-matched and ranked by current reliability. mcp-registry/io.github.foundrynet/forge-mcp/correct_mapping itself is currently "healthy".

alternative	server
mcp-registry/io.github.benseverndev-oss/goldenmatch/add_correction	io.github.benseverndev-oss/goldenmatch	live status →
mcp-registry/vc.doomscore/doom/supersede_calibration_case	vc.doomscore/doom	live status →
mcp-registry/io.github.benseverndev-oss/infermap/validate	io.github.benseverndev-oss/infermap	live status →
mcp-registry/io.github.benseverndev-oss/infermap/map	io.github.benseverndev-oss/infermap	live status →
mcp-registry/io.corpusiq/multi-source-mcp/canonical_facts_set	io.corpusiq/multi-source-mcp	live status →
mcp-registry/io.corpusiq/multi-source-mcp/canonical_pending_cancel	io.corpusiq/multi-source-mcp	live status →
mcp-registry/io.corpusiq/multi-source-mcp/canonical_pending_commit	io.corpusiq/multi-source-mcp	live status →
mcp-registry/io.corpusiq/multi-source-mcp/canonical_connector	io.corpusiq/multi-source-mcp	live status →
mcp-registry/io.github.stonesofcreation/stackswap/submit_correction	io.github.StonesofCreation/stackswap	live status →
mcp-registry/io.github.pipeworx-io/mapbox/map_matching	io.github.pipeworx-io/mapbox	live status →
mcp-registry/io.github.cuecrux/vaultcrux-memory-core/submit_correction	io.github.CueCrux/vaultcrux-memory-core	live status →
mcp-registry/io.corpusiq/multi-source-mcp/truth_sources_remove	io.corpusiq/multi-source-mcp	live status →

FAQ

What is the best alternative to mcp-registry/io.github.foundrynet/forge-mcp/correct_mapping?

mcp-registry/io.github.benseverndev-oss/goldenmatch/add_correction is the top capability-matched alternative that's live right now. Other options: mcp-registry/vc.doomscore/doom/supersede_calibration_case, mcp-registry/io.github.benseverndev-oss/infermap/validate, mcp-registry/io.github.benseverndev-oss/infermap/map, mcp-registry/io.corpusiq/multi-source-mcp/canonical_facts_set. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.foundrynet/forge-mcp/correct_mapping down right now?

mcp-registry/io.github.foundrynet/forge-mcp/correct_mapping's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.foundrynet%2Fforge-mcp%2Fcorrect_mapping.

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.foundrynet%2Fforge-mcp%2Fcorrect_mapping or MCP find_alternatives. Check mcp-registry/io.github.foundrynet/forge-mcp/correct_mapping's live status: https://glimind.com/tool/mcp-registry/io.github.foundrynet/forge-mcp/correct_mapping.