Geocoding & Weather
REMOTE · GEO.MEMORYAPI.ORG · SCANNED SEP 20
Geocoding, weather forecasts, and timezone lookups
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 250 tokens (~83/item across 3 items; 3 tools + 0 resources), lean.Pass
- 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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Geocoding & Weather MCP server?
Geocoding & Weather is a hosted endpoint at https://geo.memoryapi.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · geo.memoryapi.org
claude mcp add --transport http org-memoryapi-geo 'https://geo.memoryapi.org/mcp'
{
"mcpServers": {
"org-memoryapi-geo": {
"url": "https://geo.memoryapi.org/mcp"
}
}
} {
"servers": {
"org-memoryapi-geo": {
"type": "http",
"url": "https://geo.memoryapi.org/mcp"
}
}
} [mcp_servers.org-memoryapi-geo] url = "https://geo.memoryapi.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-memoryapi-geo": {
"type": "remote",
"url": "https://geo.memoryapi.org/mcp",
"enabled": true
}
}
} openclaw mcp add org-memoryapi-geo --url 'https://geo.memoryapi.org/mcp' --transport streamable-http
mcp_servers:
org-memoryapi-geo:
url: "https://geo.memoryapi.org/mcp" {
"McpServers": {
"org-memoryapi-geo": {
"Transport": "http",
"Url": "https://geo.memoryapi.org/mcp"
}
}
} assistant mcp add org-memoryapi-geo -t streamable-http -u 'https://geo.memoryapi.org/mcp'
{
"mcpServers": {
"org-memoryapi-geo": {
"type": "http",
"url": "https://geo.memoryapi.org/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 2026 · Probed https://geo.memoryapi.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=memoryapi.org | CN=WE1,O=Google Trust Services,C=US | 23 Aug 2026 | 21 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 71f1f8df938ee0ac1305e33fd796b527 |
| SANs: memoryapi.org, *.memoryapi.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of geo.memoryapi.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| memoryapi.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://geo.memoryapi.org/mcp | Verified | 200 | |
| http (plaintext) | http://geo.memoryapi.org/mcp | HTTPS enforced | 301 | https://geo.memoryapi.org/mcp |
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 →
geocode_address ~98
Forward or reverse geocoding using OpenStreetMap Nominatim. Forward: convert an address to lat/lon. Reverse: convert lat/lon to an address.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | Latitude for reverse geocoding |
| limit | number | – | Number of results (max 5) |
| lon | number | – | Longitude for reverse geocoding |
| q | string | – | Address or place name to forward geocode |
No output schema declared.
No examples provided.
get_timezone ~70
Get timezone and country information by coordinates, country code/name, or IP address.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO country code (US, DE) or country name |
| ip | string | – | IP address for timezone lookup |
| lat | number | – | Latitude |
| lon | number | – | Longitude |
No output schema declared.
No examples provided.
get_weather ~82
Current weather and multi-day forecast for any location. Provide coordinates or a city name.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Forecast days (1-7, default 3) |
| lat | number | – | Latitude |
| location | string | – | City name (geocoded automatically) |
| lon | number | – | Longitude |
| units | string | – | metric or imperial |
No output schema declared.
No examples provided.
What is the Geocoding & Weather MCP server?
Geocoding & Weather is an MCP server listed in the public MCP registry as org.memoryapi/geo. Geocoding, weather forecasts, and timezone lookups. This page covers its hosted endpoint (https://geo.memoryapi.org/mcp).
Is the Geocoding & Weather MCP server safe to use?
Geocoding & Weather scores 75 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 Geocoding & Weather MCP server expose?
Geocoding & Weather exposes 3 tools: geocode_address, get_weather, get_timezone. Their descriptions and schemas cost roughly 250 tokens of context every time the server is loaded.
Does the Geocoding & Weather MCP server require authentication?
No. We connected to Geocoding & Weather without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Geocoding & Weather MCP server still maintained?
Geocoding & Weather is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.