updated 2026-09-26 06:32 UTC

Opencage Geocoding MCP

OpenCageData/opencage-geocoding-mcp

MCP server for querying the OpenCage geocoding API from within LLMs

MCP Servers JavaScript Listed MIT

Is Opencage Geocoding MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.5 / 10
Provenance None
Signed commits 93%
Last push 16d ago
Compare Opencage Geocoding MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Opencage Geocoding MCP scores 56.1/100 (Grade C), ranked #747 of 1325 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 5.5/10; 93% of recent commits are signed; last pushed 2026-09-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Opencage Geocoding MCP compares in MCP Servers

  1. #412 .NET MCP Server 56.1 ±0
  2. #413 Lumino MCP Server 56.1 ±0
  3. #414 Opencage Geocoding MCP 56.1 this agent
  4. #415 Licinexus MCP 56.1 ±0
  5. #416 Paparats – Local Semantic Code Search MCP 56.1 ±0

Bars show each HVTrust score; the tick marks Opencage Geocoding MCP’s 56.1.

Where the 56.1 comes from

HVTrust dimensions vs the MCP Servers average

56.1 / 100 · 100.0% confidence

Opencage Geocoding MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.5 / 25
1.2 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.2 / 17
1.0 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
14.7 / 20
2.6 above avg 12.1
AdoptionLog-scaled stars · package downloads
4.9 / 20
2.3 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 154 spots (#890 → #736)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.5/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.
Compare with another agent Get email alerts for Opencage Geocoding MCP View MCP Servers Report missing data
44.8
Activity sub-score · out of 100
#414
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-09-26 06:32 UTC · Repo last pushed 16 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
19
Forks
2
Last Push
2026-09-10
16 days ago
Commits (4 wk)
8
Downloads (7d)
20
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼5
was #742

Analysis

Activity Inputs

44.8 / 100
StarsRepository reach
7.8 / 30
FreshnessLast push recency
22.8 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
2.2 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.5 / 10
OpenSSF Scorecard · scanned Sep 23, 2026
Signed Commits
93%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review -1
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 3
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 7

Common questions about Opencage Geocoding MCP

Opencage Geocoding 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 Opencage Geocoding MCP publish package provenance?
No published build provenance is currently detected for Opencage Geocoding MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Opencage Geocoding MCP have an OpenSSF Scorecard?
Opencage Geocoding MCP has an OpenSSF Scorecard score of 5.5/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 Opencage Geocoding MCP actively maintained?
Maintained. Last push was 16 days ago.
What license does Opencage Geocoding MCP use?
Opencage Geocoding MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Opencage Geocoding MCP's commits signed?
93% of the last 100 commits to Opencage Geocoding 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
Opencage Geocoding MCP 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 Opencage Geocoding 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-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Opencage Geocoding MCP?

For maintainers

HVTrust scores Opencage Geocoding 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 3Listed 2Grade 2Scorecard 1Delisted 1MCP 1
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 154 spots (#890 → #736)
2026-09-23
HVTrust Changed
HVTrust up 29.3pts (27.0 → 56.3)
2026-09-22
Newly Listed
First tracked at rank #890
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 12 spots (#709 → #721)
2026-09-18
Rank Moved
Rank rose 67 spots (#778 → #711)
2026-09-12
Rank Moved
Rank dropped 66 spots (#687 → #753)
2026-09-11
Rank Moved
Rank dropped 32 spots (#655 → #687)
2026-09-10
Rank Moved
Rank rose 98 spots (#753 → #655)
2026-09-09
Rank Moved
Rank dropped 19 spots (#734 → #753)
2026-09-07
Rank Moved
Rank dropped 54 spots (#677 → #731)
2026-09-06
Rank Moved
Rank dropped 14 spots (#663 → #677)
2026-09-05
Grade Changed
Trust grade D → C
2026-09-05
Rank Moved
Rank rose 467 spots (#1130 → #663)
2026-09-05
HVTrust Changed
HVTrust up 19.9pts (35.9 → 55.8)
2026-09-04
Rank Moved
Rank dropped 36 spots (#1094 → #1130)
2026-09-03
Rank Moved
Rank dropped 27 spots (#1067 → #1094)
2026-09-02
Rank Moved
Rank dropped 61 spots (#1006 → #1067)
2026-09-01
Rank Moved
Rank dropped 42 spots (#964 → #1006)
2026-08-31
Rank Moved
Rank dropped 34 spots (#930 → #964)
2026-08-30
Rank Moved
Rank dropped 45 spots (#885 → #930)
2026-08-29
Rank Moved
Rank dropped 48 spots (#837 → #885)
2026-08-28
Rank Moved
Rank dropped 25 spots (#812 → #837)
2026-08-27
Rank Moved
Rank dropped 24 spots (#788 → #812)
2026-08-26
Scorecard Added
OSSF Scorecard: 5.6/10
2026-08-26
Rank Moved
Rank rose 394 spots (#1182 → #788)
2026-08-26
HVTrust Changed
HVTrust up 18.9pts (17.8 → 36.7)
2026-08-21
Rank Moved
Rank dropped 16 spots (#1167 → #1183)
2026-08-16
Rank Moved
Rank dropped 28 spots (#1136 → #1164)
2026-08-12
Rank Moved
Rank rose 21 spots (#1152 → #1131)
2026-08-10
Rank Moved
Rank dropped 71 spots (#1081 → #1152)
2026-08-08
Newly Listed
First tracked at rank #1080
GitHub → npm: @opencage/mcp-opencage-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 56.1 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/opencage-geocoding-mcp.svg)](https://hvtracker.net/agents/opencage-geocoding-mcp)
HTML:
<a href="https://hvtracker.net/agents/opencage-geocoding-mcp"><img src="https://hvtracker.net/badge/opencage-geocoding-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.3 · Raw JSON