com.mcparmory/opencage-geocoding
OCI · GHCR.IO/MCPARMORY/OPENCAGE-GEOCODING:1.0.2 · 2 COMPONENTS
Convert addresses to coordinates and reverse-geocode locations worldwide
Last scanned (10 hours ago)
Scores higher than 77% of OCI servers
Category Maps and Location
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. How we score → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 176 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1070 tokens (~356/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: 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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 87. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed oci/ghcr.io/mcparmory/opencage-geocoding:1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
search_geojson Search GeoJSON ~345
Search for geographic locations and return results in GeoJSON format. Supports geocoding by address, place name, or coordinates with optional filtering and result customization.
| Name | Type | Req | Description |
|---|---|---|---|
| address_only | boolean | – | When enabled, limits the formatted field in results to address details only, excluding other metadata. |
| bounds | string | – | Restrict results to a geographic area by specifying a bounding box as four coordinates: southwest corner latitude, southwest corner longitude, northeast corner latitude, northeast corner longitude. |
| countrycode | string | – | Limit results to specific countries by providing a comma-separated list of ISO 3166-1 Alpha 2 country codes (e.g., 'de' for Germany, 'ch,li' for Switzerland and Liechtenstein). |
| language | string | – | Return results in a specific language using IETF language codes (e.g., 'de' for German, 'pt-BR' for Brazilian Portuguese), or use 'native' for the location's native language. |
| limit | integer | – | Maximum number of results to return. Must be between 1 and 100; defaults to 10 if not specified. |
| proximity | string | – | Bias results toward a specific location by providing coordinates in lat,lng format. Useful for prioritizing results near the user's current location. |
| q | string | yes | The location to geocode: either a place name (e.g., 'Times Square, New York, USA'), landmark name (e.g., 'Eiffel Tower'), or coordinates in lat,lng format. Minimum 2 characters required. |
| roadinfo | boolean | – | When enabled, geocodes to the nearest road and includes detailed road information in the results. |
No output schema declared.
No examples provided.
search_location Search Location ~354
Search for geographic locations by address, place name, or coordinates and return detailed geocoding results in JSON format.
| Name | Type | Req | Description |
|---|---|---|---|
| abbrv | boolean | – | When enabled, abbreviates the formatted address field in results (e.g., 'USA' instead of 'United States of America'). |
| address_only | boolean | – | When enabled, returns only the address portion in the formatted field, excluding additional details like business names or landmarks. |
| bounds | string | – | Restricts results to a geographic area using a bounding box defined by southwest and northeast corner coordinates in lat,lng format. |
| countrycode | string | – | Limits results to specific countries using a comma-separated list of ISO 3166-1 Alpha 2 country codes (e.g., 'de' for Germany, 'ch,li' for Switzerland and Liechtenstein). |
| language | string | – | Sets the language for results using an IETF language code (e.g., 'de' for German, 'pt-BR' for Brazilian Portuguese) or 'native' to use the location's native language. |
| limit | integer | – | Maximum number of results to return, between 1 and 100. Defaults to 10 results. |
| proximity | string | – | Biases results toward a specific location using coordinates in lat,lng format, prioritizing nearby matches. |
| q | string | yes | The location to geocode: either a place name (e.g., 'Times Square, New York, USA'), landmark name (e.g., 'Eiffel Tower'), or coordinates in lat,lng format. Minimum 2 characters. |
| roadinfo | boolean | – | When enabled, geocodes to the nearest road and includes detailed road information in the results. |
No output schema declared.
No examples provided.
search_location_xml Search Location XML ~371
Geocode a location query or coordinate pair and return results in XML format. Supports forward geocoding (address to coordinates) and reverse geocoding (coordinates to address).
| Name | Type | Req | Description |
|---|---|---|---|
| abbrv | boolean | – | When enabled, abbreviates the formatted address field in results (e.g., 'St' instead of 'Street'). |
| address_only | boolean | – | When enabled, returns only the address portion in the formatted field, excluding additional details. |
| bounds | string | – | Restricts results to a geographic bounding box defined by southwest and northeast corner coordinates in the format: min_longitude,min_latitude,max_longitude,max_latitude. |
| countrycode | string | – | Limits results to specific countries using a comma-separated list of ISO 3166-1 Alpha 2 country codes (e.g., 'de' for Germany, 'ch,li' for Switzerland and Liechtenstein). |
| language | string | – | Returns results in the specified language using IETF language codes (e.g., 'de' for German, 'pt-BR' for Brazilian Portuguese), or 'native' for the region's native language. |
| limit | integer | – | Maximum number of results to return, between 1 and 100. Defaults to 10 if not specified. |
| proximity | string | – | Biases results toward a specific location using latitude,longitude coordinates, prioritizing nearby matches. |
| q | string | yes | The location to geocode: either a place name/address (e.g., 'Times Square, New York, USA') or latitude,longitude coordinates (e.g., '52.5432379, 13.4142133'). Minimum 2 characters. |
| roadinfo | boolean | – | When enabled, geocodes to the nearest road and includes road information annotations in the results. |
No output schema declared.
No examples provided.
How do I install the com.mcparmory/opencage-geocoding MCP server?
com.mcparmory/opencage-geocoding runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/opencage-geocoding:1.0.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/opencage-geocoding:1.0.2
claude mcp add com-mcparmory-opencage-geocoding -- docker run --rm -i ghcr.io/mcparmory/opencage-geocoding:1.0.2
What is the com.mcparmory/opencage-geocoding MCP server?
com.mcparmory/opencage-geocoding is an MCP server listed in the public MCP registry as com.mcparmory/opencage-geocoding. Convert addresses to coordinates and reverse-geocode locations worldwide. This page covers its container image (ghcr.io/mcparmory/opencage-geocoding:1.0.2).
Is the com.mcparmory/opencage-geocoding MCP server safe to use?
com.mcparmory/opencage-geocoding scores 50 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/opencage-geocoding MCP server expose?
com.mcparmory/opencage-geocoding exposes 3 tools: search_location, search_location_xml, search_geojson. Their descriptions and schemas cost roughly 1,070 tokens of context every time the server is loaded.
Is the com.mcparmory/opencage-geocoding MCP server still maintained?
com.mcparmory/opencage-geocoding is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.