mcp-registry/io.github.lilo-property/mcp-server/search_philadelphia_historic_properties / alternatives

Live alternatives to mcp-registry/io.github.lilo-property/mcp-server/search_philadelphia_historic_properties

The best live alternatives to mcp-registry/io.github.lilo-property/mcp-server/search_philadelphia_historic_properties right now are mcp-registry/io.github.lucasnoah/philadelphia-restoration/get_local_info, mcp-registry/io.github.pipeworx-io/arcgis-chestercounty/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-harrisburg/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-pittsburgh/search_datasets, mcp-registry/io.github.pipeworx-io/data-pa/datasets — capability-matched and ranked by current reliability. mcp-registry/io.github.lilo-property/mcp-server/search_philadelphia_historic_properties itself is currently "healthy".

alternative	server
mcp-registry/io.github.lucasnoah/philadelphia-restoration/get_local_info	io.github.lucasnoah/philadelphia-restoration	live status →
mcp-registry/io.github.pipeworx-io/arcgis-chestercounty/search_datasets	io.github.pipeworx-io/arcgis-chestercounty	live status →
mcp-registry/io.github.pipeworx-io/arcgis-harrisburg/search_datasets	io.github.pipeworx-io/arcgis-harrisburg	live status →
mcp-registry/io.github.pipeworx-io/arcgis-pittsburgh/search_datasets	io.github.pipeworx-io/arcgis-pittsburgh	live status →
mcp-registry/io.github.pipeworx-io/data-pa/datasets	io.github.pipeworx-io/data-pa	live status →
mcp-registry/io.github.pipeworx-io/arcgis-allegheny/search_datasets	io.github.pipeworx-io/arcgis-allegheny	live status →
mcp-registry/io.github.pipeworx-io/arcgis-berkscounty/search_datasets	io.github.pipeworx-io/arcgis-berkscounty	live status →
mcp-registry/io.github.pipeworx-io/arcgis-lancaster/search_datasets	io.github.pipeworx-io/arcgis-lancaster	live status →
mcp-registry/io.github.pipeworx-io/geonames/search_geonames	io.github.pipeworx-io/geonames	live status →
mcp-registry/io.github.lucasnoah/philadelphia-restoration/estimate_cost	io.github.lucasnoah/philadelphia-restoration	live status →
mcp-registry/io.github.pipeworx-io/arcgis-delawareco/search_datasets	io.github.pipeworx-io/arcgis-delawareco	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/property_search_area	io.github.blackboxfoundry/livedatalink	live status →

FAQ

What is the best alternative to mcp-registry/io.github.lilo-property/mcp-server/search_philadelphia_historic_properties?

mcp-registry/io.github.lucasnoah/philadelphia-restoration/get_local_info is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/arcgis-chestercounty/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-harrisburg/search_datasets, mcp-registry/io.github.pipeworx-io/arcgis-pittsburgh/search_datasets, mcp-registry/io.github.pipeworx-io/data-pa/datasets. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.lilo-property/mcp-server/search_philadelphia_historic_properties down right now?

mcp-registry/io.github.lilo-property/mcp-server/search_philadelphia_historic_properties's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.lilo-property%2Fmcp-server%2Fsearch_philadelphia_historic_properties.

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.lilo-property%2Fmcp-server%2Fsearch_philadelphia_historic_properties or MCP find_alternatives. Check mcp-registry/io.github.lilo-property/mcp-server/search_philadelphia_historic_properties's live status: https://glimind.com/tool/mcp-registry/io.github.lilo-property/mcp-server/search_philadelphia_historic_properties.