updated 2026-10-16 16:07 UTC

MCP Ip2location Io

Repository Website

IP Geolocation MCP server using IP2Location.io API

MCP Servers Python Listed MIT

Is MCP Ip2location Io safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.3 / 10
Provenance None
Signed commits 24%
Last push 17d ago
Advisories None known
Compare MCP Ip2location Io

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: MCP Ip2location Io scores 44.0/100 (Grade D), ranked #1145 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.3/10; 24% of recent commits are signed; no published advisory affects its latest release (mcp-ip2location-io); last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Ip2location Io 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 MCP Ip2location Io 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/ip2location/mcp-ip2location-io, MIT, last pushed 2026-09-29. 24% 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.3/10 (scanned Oct 4, 2026). The checks that decide who can get a change released:

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

  3. Published packages Not linked

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: mcp-ip2location-io 1.1.2. No published advisory affects it (OSV, checked 2026-10-15).

Changes to this chain

  • 2026-09-23 License classification changed from unlicensed to open
  • 2026-08-26 OSSF Scorecard: 1.9/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 MCP Ip2location Io’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 MCP Ip2location Io compares in MCP Servers

  1. #657 Slack Explorer MCP 44.1 +0.1
  2. #658 CodeWiki MCP — AI-generated docs for GitHub repos 44.0 ±0
  3. #659 MCP Ip2location Io 44.0 this agent
  4. #660 Perplexity Comet MCP 43.8 −0.2
  5. #661 Strava MCP 43.7 −0.3

Bars show each HVTrust score; the tick marks MCP Ip2location Io’s 44.0.

Where the 44.0 comes from

HVTrust dimensions vs the MCP Servers average

44.0 / 100 · 100.0% confidence

MCP Ip2location Io MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.1 / 25
6.4 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
10.5 / 17
1.8 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
12.8 / 20
0.5 above avg 12.3
AdoptionLog-scaled stars · package downloads
4.8 / 20
2.6 below avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-15
Rank Moved
Rank dropped 10 spots (#1131 → #1141)
2026-10-09
Rank Moved
Rank dropped 12 spots (#1094 → #1106)
2026-09-29
Activity Score Changed
Activity score up 10pts (33 → 43)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.3/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for MCP Ip2location Io View MCP Servers Report missing data
40.8
Activity sub-score · out of 100
#659
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 D 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-10-16 16:07 UTC · Repo last pushed 17 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
16
Forks
10
Last Push
2026-09-29
17 days ago
Commits (4 wk)
2
Downloads (7d)
23
pypi
HN mentions (30d)
—
Open Issues
1
Rank Change
▼4
was #1141

Analysis

Activity Inputs

40.8 / 100
StarsRepository reach
7.4 / 30
FreshnessLast push recency
22.6 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
4.8 / 20

Common questions about MCP Ip2location Io

Public trust evidence for MCP Ip2location Io is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does MCP Ip2location Io publish package provenance?
No published build provenance is currently detected for MCP Ip2location Io. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MCP Ip2location Io have an OpenSSF Scorecard?
MCP Ip2location Io has an OpenSSF Scorecard score of 2.3/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 MCP Ip2location Io actively maintained?
Maintained. Last push was 17 days ago.
What license does MCP Ip2location Io use?
MCP Ip2location Io ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Ip2location Io's commits signed?
24% of the last 100 commits to MCP Ip2location Io 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
medium confidence
Implemented
MCP Ip2location Io appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency 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
low confidence
Unknown
Package source metadata is missing or inconclusive
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 MCP Ip2location Io'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-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-08-28
Activity Resumed
Activity resumed
2026-08-24
Activity Went Stale
No commits for 90 days

Maintain MCP Ip2location Io?

For maintainers

HVTrust scores MCP Ip2location Io 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 22HVTrust 4Score 3Listed 2Stale 1Scorecard 1Fresh 1Delisted 1MCP 1License 1
2026-10-15
Rank Moved
Rank dropped 10 spots (#1131 → #1141)
2026-10-09
Rank Moved
Rank dropped 12 spots (#1094 → #1106)
2026-09-29
Activity Score Changed
Activity score up 10pts (33 → 43)
2026-09-27
Rank Moved
Rank dropped 50 spots (#1102 → #1152)
2026-09-27
Activity Score Changed
Activity score down 8pts (41 → 33)
2026-09-23
License Changed
License classification changed from unlicensed to open
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 61 spots (#1153 → #1092)
2026-09-23
HVTrust Changed
HVTrust up 22.7pts (20.6 → 43.3)
2026-09-22
Newly Listed
First tracked at rank #1153
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-17
Rank Moved
Rank rose 10 spots (#1096 → #1086)
2026-09-14
Rank Moved
Rank dropped 11 spots (#1083 → #1094)
2026-09-12
Rank Moved
Rank dropped 14 spots (#1069 → #1083)
2026-09-09
Rank Moved
Rank dropped 14 spots (#1055 → #1069)
2026-09-07
Rank Moved
Rank dropped 35 spots (#1019 → #1054)
2026-09-06
Rank Moved
Rank dropped 17 spots (#1002 → #1019)
2026-09-04
Rank Moved
Rank rose 233 spots (#1227 → #994)
2026-09-04
HVTrust Changed
HVTrust up 14.6pts (28.1 → 42.7)
2026-09-03
Rank Moved
Rank dropped 44 spots (#1183 → #1227)
2026-09-02
Rank Moved
Rank dropped 39 spots (#1144 → #1183)
2026-09-01
Rank Moved
Rank dropped 43 spots (#1101 → #1144)
2026-08-31
Rank Moved
Rank dropped 30 spots (#1071 → #1101)
2026-08-30
Rank Moved
Rank dropped 50 spots (#1021 → #1071)
2026-08-29
Rank Moved
Rank dropped 52 spots (#969 → #1021)
2026-08-28
Activity Resumed
Activity resumed
2026-08-28
Rank Moved
Rank rose 71 spots (#1040 → #969)
2026-08-28
HVTrust Changed
HVTrust up 5.7pts (22.9 → 28.6)
2026-08-28
Activity Score Changed
Activity score up 20pts (24 → 44)
2026-08-27
Rank Moved
Rank dropped 24 spots (#1016 → #1040)
2026-08-26
Scorecard Added
OSSF Scorecard: 1.9/10
2026-08-26
Rank Moved
Rank rose 280 spots (#1296 → #1016)
2026-08-26
HVTrust Changed
HVTrust up 10.3pts (12.6 → 22.9)
2026-08-24
Activity Went Stale
No commits for 90 days
2026-08-16
Rank Moved
Rank dropped 25 spots (#1270 → #1295)
2026-08-10
Rank Moved
Rank dropped 79 spots (#1191 → #1270)
2026-08-08
Newly Listed
First tracked at rank #1191
GitHub → Website → PyPI: mcp-ip2location-io

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 44.0 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcp-ip2location-io.svg)](https://hvtracker.net/agents/mcp-ip2location-io)
HTML:
<a href="https://hvtracker.net/agents/mcp-ip2location-io"><img src="https://hvtracker.net/badge/mcp-ip2location-io.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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