mcp-registry/io.github.pipeworx-io/greenhouse/forget / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/greenhouse/forget

The best live alternatives to mcp-registry/io.github.pipeworx-io/greenhouse/forget right now are mcp-registry/io.github.pipeworx-io/fcc/forget, mcp-registry/io.github.pipeworx-io/madrid-events/forget, mcp-registry/io.github.pipeworx-io/openfigi/forget, mcp-registry/io.github.pipeworx-io/govcon-intel/forget, mcp-registry/io.github.pipeworx-io/datos-gob-es/forget — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/greenhouse/forget itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/fcc/forget	io.github.pipeworx-io/fcc	live status →
mcp-registry/io.github.pipeworx-io/madrid-events/forget	io.github.pipeworx-io/madrid-events	live status →
mcp-registry/io.github.pipeworx-io/openfigi/forget	io.github.pipeworx-io/openfigi	live status →
mcp-registry/io.github.pipeworx-io/govcon-intel/forget	io.github.pipeworx-io/govcon-intel	live status →
mcp-registry/io.github.pipeworx-io/datos-gob-es/forget	io.github.pipeworx-io/datos-gob-es	live status →
mcp-registry/io.github.pipeworx-io/datagov-il/forget	io.github.pipeworx-io/datagov-il	live status →
mcp-registry/io.github.pipeworx-io/data-usdot/forget	io.github.pipeworx-io/data-usdot	live status →
mcp-registry/io.github.pipeworx-io/riksbank-se/forget	io.github.pipeworx-io/riksbank-se	live status →
mcp-registry/io.github.pipeworx-io/kalshi/forget	io.github.pipeworx-io/kalshi	live status →
mcp-registry/io.github.pipeworx-io/jpl-ssd/forget	io.github.pipeworx-io/jpl-ssd	live status →
mcp-registry/io.github.pipeworx-io/jargon-translator/forget	io.github.pipeworx-io/jargon-translator	live status →
mcp-registry/io.github.pipeworx-io/epa-envirofacts/forget	io.github.pipeworx-io/epa-envirofacts	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/greenhouse/forget?

mcp-registry/io.github.pipeworx-io/fcc/forget is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/madrid-events/forget, mcp-registry/io.github.pipeworx-io/openfigi/forget, mcp-registry/io.github.pipeworx-io/govcon-intel/forget, mcp-registry/io.github.pipeworx-io/datos-gob-es/forget. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/greenhouse/forget down right now?

mcp-registry/io.github.pipeworx-io/greenhouse/forget's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fgreenhouse%2Fforget.

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.pipeworx-io%2Fgreenhouse%2Fforget or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/greenhouse/forget's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/greenhouse/forget.