# JustRouting MCP Server (mcpb · justrouting.mcpb) Road routing, travel-time matrices, geocoding, and fleet optimization for Southeast Asia. - Trust score: 6/100 (low) - Change this week: 0 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-10-19 ## Components - mcpb · `justrouting.mcpb`: 6/100 (this document), [markdown](https://verifymcp.io/servers/justrouting-justrouting/justrouting.md), [page](https://verifymcp.io/servers/justrouting-justrouting/justrouting) ## Channel facts - Registry: `mcpb` - Package: `https://github.com/justrouting/mcp/releases/download/v0.1.5/justrouting.mcpb` - Transport: `stdio` - SHA-256: `fadc7ce2b496f4a986bf3022f10e6ba1f6155797a75ecb2599611bfae29ee792` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-10-19. - **Supply Chain Security**: 0/100 - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package. - Known CVEs could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it. - Install-script risk could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it. - Dependency health could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it. - **Provenance & Transparency**: 29/100 - Source repository is publicly reachable at the declared URL. - Build provenance could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it. - Licence could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it. - Maintenance history could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it. - Publishes a security disclosure policy (SECURITY.md). - **Schema Quality & AI Usability**: 0/100 - Schema quality not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no schema to assess. - **Stability & Change Management**: 0/100 - Stability not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no schema to compare. - **Tool Coverage**: 0/100 - Tool coverage not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no tool definitions to assess. - **Tool Safety**: 0/100 - Tool safety not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no tool text to scan. - **Capabilities**: 0/100 - Protocol version not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we never saw its MCP handshake. **Unverified: 6 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm. ## Install ### How do I install the JustRouting MCP Server server? JustRouting MCP Server ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, fadc7ce2b496f4a986bf3022f10e6ba1f6155797a75ecb2599611bfae29ee792; the commands to do that are on this page. If it does not match, do not open it. - Download bundle: `https://github.com/justrouting/mcp/releases/download/v0.1.5/justrouting.mcpb` - SHA-256: `fadc7ce2b496f4a986bf3022f10e6ba1f6155797a75ecb2599611bfae29ee792` ### Verify on macOS / Linux ```bash echo "fadc7ce2b496f4a986bf3022f10e6ba1f6155797a75ecb2599611bfae29ee792 justrouting.mcpb" | shasum -a 256 -c ``` ### Verify on Windows (PowerShell) ```powershell (Get-FileHash -Algorithm SHA256 .\justrouting.mcpb).Hash -eq "fadc7ce2b496f4a986bf3022f10e6ba1f6155797a75ecb2599611bfae29ee792" ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-10-09 (score 6, +2) - [security regression] Provenance: fail → unverified - [security improvement] Source repository: fail → pass - [functional regression] License: pass → unverified - [functional regression] Maintenance: pass → unverified - [functional improvement] Security disclosure: fail → pass - [functional] Licence: MIT ### 2026-10-04 (score 4, −5) - [security regression] Source repository: pass → fail ### 2026-10-03 (score 9) First indexed and scored. ## MCP tools (0) Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package. ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/justrouting-justrouting/justrouting#diagnostics ## Score history - 2026-10-19: 6 - 2026-10-18: 6 - 2026-10-17: 6 - 2026-10-16: 6 - 2026-10-15: 6 - 2026-10-14: 6 - 2026-10-13: 6 - 2026-10-12: 6 - 2026-10-10: 6 - 2026-10-09: 6 - 2026-10-04: 4 - 2026-10-03: 9 ## Links - Repository: https://github.com/justrouting/mcp - Website: https://justrouting.tech/ - Changelog RSS feed: https://verifymcp.io/servers/justrouting-justrouting/justrouting.xml - Changelog JSON feed: https://verifymcp.io/servers/justrouting-justrouting/justrouting.json - HTML version of this page: https://verifymcp.io/servers/justrouting-justrouting/justrouting