RefConvMCP
Related Servers
Alternatives to RefConvMCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceProvides 22 geospatial tools for coordinate conversion, geocoding, routing, terrain analysis, weather, and radio link planning, all without requiring API keys.22MIT
- AlicenseNot gradedqualityBmaintenanceEnables geocoding, reverse geocoding, place search, OpenStreetMap object lookup, nearby category search, and local great-circle distance calculations through public OpenStreetMap APIs.79 npmMIT
- AlicenseNot gradedqualityCmaintenanceEncode latitude/longitude to geohash strings and decode geohashes to coordinates with offline, keyless operation.74 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables ham radio operators to render and manipulate an interactive grayline and Maidenhead grid map, add or remove points and highlighted grids, configure map options, and convert grid locators to coordinates with distance and heading from home.-
- AlicenseNot gradedqualityCmaintenanceProvides tools to search for KartaView street-level imagery near a location and retrieve all frames of a given sequence.72 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables UK postcode lookups including geographic details, nearest postcodes, validation, and random postcode generation via the free postcodes.io API.86 npmMIT
TDQS
Scored across 4 tools
The conversion pair (gridref_to_latlon vs latlon_to_gridref) is unambiguous, distinguished by direction and argument names. The two Street View tools are mostly distinct (free metadata probe vs image retrieval), but streetview_coverage overlaps with the panorama-lookup step already embedded in streetview_from_gridref, so an agent may wonder which to call first.
All names use snake_case and the two conversion tools follow a clean symmetric 'a_to_b' pattern, with streetview_ prefix grouping the imagery tools. Minor deviation: 'coverage' is a noun while the others are action/prepositional phrases, but the set is still easily readable.
Four tools is tight and appropriate for a narrow conversion-plus-imagery utility, with each tool mapping to a distinct step. It is slightly on the lean side, and streetview_coverage is partially redundant with the lookup inside streetview_from_gridref.
Both conversion directions plus a coverage check and image retrieval cover the core workflow end to end. Gaps are minor: no batch conversion, no alternative datums/other national grids, and no reverse lookup of a panorama back to coordinates.