hike-finder
Finds marked hiking routes from OpenStreetMap filtered by locally-computed elevation gain, distance, loop shape, and car/chairlift access, providing consistent and tunable metrics instead of third-party scraped data.
Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
Limited view: static analysis for Python is partially covered.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
BoykoNeov
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
HIKE_ELEVATION_MODESet via . See src/hike_finder/config.py.HIKE_DEM_DIRGeoTIFF DEM tile directory (for local/auto) —HIKE_API_ENDPOINTOverride the elevation API endpoint provider defaultHIKE_OVERPASS_URLOverride the Overpass endpoint (use a regional/self-hosted instance for heavy use) overpass-api.deHIKE_OVERPASS_UA(web UI), or =you@example.com in the environment — perHIKE_API_MIN_INTERVALMin seconds between elevation-API requests (keeps you under the public ~1 req/sec limit) 1.1HIKE_API_MAX_RETRIESRetries on transient API errors (429 / 5xx / network), with exponential backoff honouring Retry-After 3HIKE_API_BACKOFFBackoff base seconds, doubled each retry 2.0HIKE_API_MAX_BACKOFFCap on any single wait, seconds; a Retry-After above this (e.g. a daily-quota 429) makes the route degrade to n/a instead of stalling 30HIKE_API_DAILY_LIMITMax elevation-API requests per UTC day, counted in a persistent file across runs; at the cap, routes degrade to n/a instead of getting the IP banned. 0 disables tracking 1000HIKE_API_STATE_DIRDirectory holding the daily-counter file per-user cache (%LOCALAPPDATA%/hike-finder or ~/.cache/hike-finder)HIKE_GAIN_THRESHOLDHysteresis climb threshold, metres (must exceed peak-to-peak DEM noise) 10HIKE_SAMPLE_INTERVALResample spacing along the track, metres 25HIKE_SMOOTH_WINDOWElevation smoothing window, samples 3HIKE_LOOP_TOLERANCEstart≈end distance that closes a loop, metres 150HIKE_CAR_RADIUSParking-near-endpoint radius, metres 300HIKE_LIFT_RADIUSLift-station-near-endpoint radius, metres 400HIKE_MAX_ROUTE_FACTORDrop routes longer than this × the bbox diagonal (kills through-routes) 4.0XDG_CACHE_HOMETool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
1/1 tools missing one or more hints — find_hikes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
License file
No license file
Add a LICENSE file (MIT, Apache-2.0, etc.).
Tests exist
No test files found
Add tests that exercise each declared tool.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/boykoneov/hike-finder-mcp)?variant=verified to the badge URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check