mcp-registry/io.github.baneado98/muni-dev-cost/get_fee_schedule_source / alternatives
mcp-registry/io.github.baneado98/muni-dev-cost/get_fee_schedule_sourceThe best live alternatives to mcp-registry/io.github.baneado98/muni-dev-cost/get_fee_schedule_source right now are mcp-registry/io.kolmo.www/kolmo-mcp-server/estimate_permit_fee, mcp-registry/io.github.realopengroup/mcp-server/get_fee_structure, mcp-registry/com.weverlabs/agentic-rails/get_movement_fee_schedule, mcp-registry/network.tenzro/tenzro/get_fee_route, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_transit_schedules — capability-matched and ranked by current reliability. mcp-registry/io.github.baneado98/muni-dev-cost/get_fee_schedule_source itself is currently "healthy".
mcp-registry/io.kolmo.www/kolmo-mcp-server/estimate_permit_fee is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.realopengroup/mcp-server/get_fee_structure, mcp-registry/com.weverlabs/agentic-rails/get_movement_fee_schedule, mcp-registry/network.tenzro/tenzro/get_fee_route, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_transit_schedules. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.baneado98/muni-dev-cost/get_fee_schedule_source's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.baneado98%2Fmuni-dev-cost%2Fget_fee_schedule_source.
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.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.baneado98%2Fmuni-dev-cost%2Fget_fee_schedule_source
or MCP find_alternatives. Check mcp-registry/io.github.baneado98/muni-dev-cost/get_fee_schedule_source's live status: https://glimind.com/tool/mcp-registry/io.github.baneado98/muni-dev-cost/get_fee_schedule_source.