updated 2026-11-10 04:07 UTC

Map Traveler MCP

Repository Website

Virtual traveler library for MCP

MCP Servers TypeScript Listed MIT

Is Map Traveler MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 2.8 / 10
Provenance Attested
Signed commits 38%
Last push 99d ago
Advisories None known
Compare Map Traveler MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Map Traveler MCP scores 57.8/100 (Grade C), ranked #767 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 2.8/10; 38% of recent commits are signed; no published advisory affects its latest release (@mfukushim/map-traveler-mcp); last pushed 2026-08-03. Every point is earned from checkable signals — never paid placement. How scoring works →

How Map Traveler MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Map Traveler MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/mfukushim/map-traveler-mcp, MIT, last pushed 2026-08-03. 38% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 2.8/10 (scanned Oct 30, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 8
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: @mfukushim/map-traveler-mcp 0.1.7. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-09-02 OSSF Scorecard: 2.8/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Map Traveler MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Map Traveler MCP compares in MCP Servers

  1. #415 MCPfinder - MCP Server Discovery 57.9 +0.1
  2. #416 Tradingview MCP 57.8 ±0
  3. #417 Map Traveler MCP 57.8 this agent
  4. #418 MCP Shodan 57.5 −0.3
  5. #419 MCP Console Automation 57.5 −0.3

Bars show each HVTrust score; the tick marks Map Traveler MCP’s 57.8.

Where the 57.8 comes from

HVTrust dimensions vs the MCP Servers average

57.8 / 100 · 100.0% confidence

Map Traveler MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.9 / 25
2.1 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
10.9 / 17
1.4 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
5.4 / 20
6.8 below avg 12.2
AdoptionLog-scaled stars · package downloads
6.1 / 20
1.5 below avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-11-02
Rank Moved
Rank dropped 10 spots (#735 → #745)
2026-11-01
Activity Went Stale
No commits for 90 days
2026-10-27
Rank Moved
Rank dropped 10 spots (#737 → #747)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.8/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 99 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
24.5
Activity sub-score · out of 100
#417
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 99 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
24
Forks
9
Last Push
2026-08-03
99 days ago
Commits (4 wk)
0
Downloads (7d)
105
npm
HN mentions (30d)
—
Open Issues
3
Rank Change
▼3
was #764

Analysis

Activity Inputs

24.5 / 100
StarsRepository reach
8.4 / 30
FreshnessLast push recency
11.2 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.7 / 20

Common questions about Map Traveler MCP

Map Traveler MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Map Traveler MCP publish package provenance?
Yes. Map Traveler MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Map Traveler MCP have an OpenSSF Scorecard?
Map Traveler MCP has an OpenSSF Scorecard score of 2.8/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Map Traveler MCP actively maintained?
Slowing down. Last push was 99 days ago — keep an eye on whether activity resumes.
What license does Map Traveler MCP use?
Map Traveler MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Map Traveler MCP's commits signed?
38% of the last 100 commits to Map Traveler MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Map Traveler MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Map Traveler MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-11-01
Activity Went Stale
No commits for 90 days
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Map Traveler MCP?

For maintainers

HVTrust scores Map Traveler MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 24HVTrust 3Grade 2Scorecard 1Delisted 1Listed 1Provenance 1MCP 1Surface 1Stale 1
2026-11-02
Rank Moved
Rank dropped 10 spots (#735 → #745)
2026-11-01
Activity Went Stale
No commits for 90 days
2026-10-27
Rank Moved
Rank dropped 10 spots (#737 → #747)
2026-10-26
Rank Moved
Rank dropped 12 spots (#725 → #737)
2026-10-23
Rank Moved
Rank dropped 10 spots (#718 → #728)
2026-10-18
Rank Moved
Rank dropped 14 spots (#698 → #712)
2026-10-12
Rank Moved
Rank dropped 10 spots (#660 → #670)
2026-10-03
Rank Moved
Rank dropped 14 spots (#632 → #646)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 596 spots (#1200 → #604)
2026-09-23
HVTrust Changed
HVTrust up 41.9pts (19.1 → 61.0)
2026-09-22
Newly Listed
First tracked at rank #1200
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 13 spots (#577 → #590)
2026-09-15
Rank Moved
Rank dropped 11 spots (#570 → #581)
2026-09-11
Rank Moved
Rank dropped 13 spots (#538 → #551)
2026-09-08
Rank Moved
Rank dropped 10 spots (#524 → #534)
2026-09-07
Rank Moved
Rank dropped 33 spots (#491 → #524)
2026-09-05
Rank Moved
Rank dropped 75 spots (#407 → #482)
2026-09-03
Grade Changed
Trust grade D → C
2026-09-03
Rank Moved
Rank rose 551 spots (#949 → #398)
2026-09-03
HVTrust Changed
HVTrust up 21.0pts (41.2 → 62.2)
2026-09-02
Scorecard Added
OSSF Scorecard: 2.8/10
2026-09-02
Rank Moved
Rank rose 31 spots (#980 → #949)
2026-09-02
HVTrust Changed
HVTrust up 3.4pts (37.8 → 41.2)
2026-09-01
Rank Moved
Rank dropped 40 spots (#940 → #980)
2026-08-31
Rank Moved
Rank dropped 33 spots (#907 → #940)
2026-08-30
Rank Moved
Rank dropped 42 spots (#865 → #907)
2026-08-29
Rank Moved
Rank dropped 48 spots (#817 → #865)
2026-08-28
Rank Moved
Rank dropped 24 spots (#793 → #817)
2026-08-27
Rank Moved
Rank dropped 22 spots (#771 → #793)
2026-08-26
Rank Moved
Rank dropped 102 spots (#669 → #771)
2026-08-16
Rank Moved
Rank dropped 15 spots (#648 → #663)
GitHub → Website → npm: @mfukushim/map-traveler-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 57.8 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/map-traveler-mcp.svg)](https://hvtracker.net/agents/map-traveler-mcp)
HTML:
<a href="https://hvtracker.net/agents/map-traveler-mcp"><img src="https://hvtracker.net/badge/map-traveler-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON