mcp-registry/io.kolmo.www/kolmo-mcp-server/lookup_parcel_by_address / alternatives

Live alternatives to mcp-registry/io.kolmo.www/kolmo-mcp-server/lookup_parcel_by_address

The best live alternatives to mcp-registry/io.kolmo.www/kolmo-mcp-server/lookup_parcel_by_address right now are mcp-registry/io.github.pipeworx-io/arcgis-seattle/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-washingtoncomn/search_datasets, mcp-registry/com.ingest0r.api/cook-county-property-data/search_chicago_property_by_address, mcp-registry/io.github.blackboxfoundry/livedatalink/parcel_search, mcp-registry/io.github.pipeworx-io/arcgis-puyallup/search_datasets — capability-matched and ranked by current reliability. mcp-registry/io.kolmo.www/kolmo-mcp-server/lookup_parcel_by_address itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/arcgis-seattle/search_datasets	io.github.pipeworx-io/arcgis-seattle	live status →
mcp-registry/io.github.pipeworx-io/arcgis-washingtoncomn/search_datasets	io.github.pipeworx-io/arcgis-washingtoncomn	live status →
mcp-registry/com.ingest0r.api/cook-county-property-data/search_chicago_property_by_address	com.ingest0r.api/cook-county-property-data	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/parcel_search	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.pipeworx-io/arcgis-puyallup/search_datasets	io.github.pipeworx-io/arcgis-puyallup	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/parcel_details	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.pipeworx-io/arcgis-dc/search_datasets	io.github.pipeworx-io/arcgis-dc	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/property_search_area	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/property_lookup	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/com.skipshit/mcp/search_person_or_address	com.skipshit/mcp	live status →
mcp-registry/io.github.pipeworx-io/mapbox/geocode_forward	io.github.pipeworx-io/mapbox	live status →
mcp-registry/io.github.pipeworx-io/arcgis-honolulu/search_datasets	io.github.pipeworx-io/arcgis-honolulu	live status →

FAQ

What is the best alternative to mcp-registry/io.kolmo.www/kolmo-mcp-server/lookup_parcel_by_address?

mcp-registry/io.github.pipeworx-io/arcgis-seattle/search_datasets is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/arcgis-washingtoncomn/search_datasets, mcp-registry/com.ingest0r.api/cook-county-property-data/search_chicago_property_by_address, mcp-registry/io.github.blackboxfoundry/livedatalink/parcel_search, mcp-registry/io.github.pipeworx-io/arcgis-puyallup/search_datasets. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.kolmo.www/kolmo-mcp-server/lookup_parcel_by_address down right now?

mcp-registry/io.kolmo.www/kolmo-mcp-server/lookup_parcel_by_address's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.kolmo.www%2Fkolmo-mcp-server%2Flookup_parcel_by_address.

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.kolmo.www%2Fkolmo-mcp-server%2Flookup_parcel_by_address or MCP find_alternatives. Check mcp-registry/io.kolmo.www/kolmo-mcp-server/lookup_parcel_by_address's live status: https://glimind.com/tool/mcp-registry/io.kolmo.www/kolmo-mcp-server/lookup_parcel_by_address.