mcp-registry/io.github.foundrole/jobs-mcp-proxy/job_alert_unsubscribe / alternatives

Live alternatives to mcp-registry/io.github.foundrole/jobs-mcp-proxy/job_alert_unsubscribe

The best live alternatives to mcp-registry/io.github.foundrole/jobs-mcp-proxy/job_alert_unsubscribe right now are pulsemcp/100hires/hires_delete_job_webhook, mcp-registry/com.100hires/100hires/hires_delete_job_webhook, mcp-registry/ai.snowsure/snow/unsubscribe_alerts, mcp-registry/app.himalayas/mcp/delete_company_job, mcp-registry/app.himalayas/mcp/remove_saved_job — capability-matched and ranked by current reliability. mcp-registry/io.github.foundrole/jobs-mcp-proxy/job_alert_unsubscribe itself is currently "healthy".

alternative	server
pulsemcp/100hires/hires_delete_job_webhook	100Hires	live status →
mcp-registry/com.100hires/100hires/hires_delete_job_webhook	com.100hires/100hires	live status →
mcp-registry/ai.snowsure/snow/unsubscribe_alerts	ai.snowsure/snow	live status →
mcp-registry/app.himalayas/mcp/delete_company_job	app.himalayas/mcp	live status →
mcp-registry/app.himalayas/mcp/remove_saved_job	app.himalayas/mcp	live status →
mcp-registry/io.github.syenite-ai/syenite/alerts.remove	io.github.syenite-ai/syenite	live status →
mcp-registry/io.github.pipeworx-io/arcgis-chatham/unsubscribe	io.github.pipeworx-io/arcgis-chatham	live status →
mcp-registry/io.github.pipeworx-io/data-texas/unsubscribe	io.github.pipeworx-io/data-texas	live status →
mcp-registry/io.github.pipeworx-io/geoapify/unsubscribe	io.github.pipeworx-io/geoapify	live status →
mcp-registry/io.github.pipeworx-io/gbif/unsubscribe	io.github.pipeworx-io/gbif	live status →
mcp-registry/io.github.pipeworx-io/leetcode/unsubscribe	io.github.pipeworx-io/leetcode	live status →
mcp-registry/io.github.pipeworx-io/data-ny/unsubscribe	io.github.pipeworx-io/data-ny	live status →

FAQ

What is the best alternative to mcp-registry/io.github.foundrole/jobs-mcp-proxy/job_alert_unsubscribe?

pulsemcp/100hires/hires_delete_job_webhook is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.100hires/100hires/hires_delete_job_webhook, mcp-registry/ai.snowsure/snow/unsubscribe_alerts, mcp-registry/app.himalayas/mcp/delete_company_job, mcp-registry/app.himalayas/mcp/remove_saved_job. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.foundrole/jobs-mcp-proxy/job_alert_unsubscribe down right now?

mcp-registry/io.github.foundrole/jobs-mcp-proxy/job_alert_unsubscribe's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.foundrole%2Fjobs-mcp-proxy%2Fjob_alert_unsubscribe.

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.foundrole%2Fjobs-mcp-proxy%2Fjob_alert_unsubscribe or MCP find_alternatives. Check mcp-registry/io.github.foundrole/jobs-mcp-proxy/job_alert_unsubscribe's live status: https://glimind.com/tool/mcp-registry/io.github.foundrole/jobs-mcp-proxy/job_alert_unsubscribe.