Location and Timezone MCP Server by RoxyAPI
REMOTE · ROXYAPI.COM · SCANNED SEP 20
City geocoding and timezone resolution for birth data, for AI agents, one API key.
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability83
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 858 tokens (~286/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Tools include usage examples.Pass
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
How do I install the Location and Timezone MCP Server by RoxyAPI server?
Location and Timezone MCP Server by RoxyAPI is a hosted endpoint at https://roxyapi.com/mcp/location, 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 · roxyapi.com
claude mcp add --transport http com-roxyapi-location 'https://roxyapi.com/mcp/location'
{
"mcpServers": {
"com-roxyapi-location": {
"url": "https://roxyapi.com/mcp/location"
}
}
} {
"servers": {
"com-roxyapi-location": {
"type": "http",
"url": "https://roxyapi.com/mcp/location"
}
}
} [mcp_servers.com-roxyapi-location] url = "https://roxyapi.com/mcp/location"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-roxyapi-location": {
"type": "remote",
"url": "https://roxyapi.com/mcp/location",
"enabled": true
}
}
} openclaw mcp add com-roxyapi-location --url 'https://roxyapi.com/mcp/location' --transport streamable-http
mcp_servers:
com-roxyapi-location:
url: "https://roxyapi.com/mcp/location" {
"McpServers": {
"com-roxyapi-location": {
"Transport": "http",
"Url": "https://roxyapi.com/mcp/location"
}
}
} assistant mcp add com-roxyapi-location -t streamable-http -u 'https://roxyapi.com/mcp/location'
{
"mcpServers": {
"com-roxyapi-location": {
"type": "http",
"url": "https://roxyapi.com/mcp/location"
}
}
} 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.
- 4 Sept 26 0
- Tool “get_location_countries” rewrote its description, which is the text the model reads security
- 2 Sept 26 +8
- Stability: fail → pass ▲ security
- 26 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
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 46.
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 39 to 43.
- 15 Aug 26 0
- Authorization: unverified → partial ▲ security
- Schema quality: 346 → 284 ▲ functional
- Schema quality: fail → pass ▲ functional
- “get_location_countries” reworded the description of “compact” cosmetic
- “get_location_countries_iso2” reworded the description of “compact” cosmetic
- “get_location_search” reworded the description of “compact” cosmetic
- 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
- 10 Aug 26 0
- Tool “get_location_search” rewrote its description, which is the text the model reads security
- Schema quality: 311 → 346 ▼ functional
- “get_location_search” reworded the description of “q” cosmetic
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://roxyapi.com/mcp/location
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=roxyapi.com | CN=WE1,O=Google Trust Services,C=US | 26 Jul 2026 | 24 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | fb04ac30ca01abb60e3558bdfadfe2f4 |
| SANs: roxyapi.com, *.roxyapi.com | ||||||
| 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 roxyapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| roxyapi.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'inline-speculation-rules' 'unsafe-eval' https://challenges.cloudflare.com https://cdn.jsdelivr.net https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net; img-src 'self' data: https:; font-src 'self' https://fonts.scalar.com; connect-src 'self' https://api.scalar.com https://challenges.cloudflare.com https://cloudflareinsights.com; frame-src https://challenges.cloudflare.com https://roxyapi.github.io; frame-ancestors 'none'; object-src 'none'; base-uri 'self'; form-action 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self), usb=(), bluetooth=(), accelerometer=(), gyroscope=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://roxyapi.com/mcp/location | Verified | 200 | |
| http (plaintext) | http://roxyapi.com/mcp/location | HTTPS enforced | 301 | https://roxyapi.com/mcp/location |
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 →
get_location_countries List all countries - ISO codes and city coverage ~180
Returns every country with ISO 3166-1 alpha-2 and alpha-3 codes, plus the number of searchable cities per country. Use this endpoint to build country dropdown menus, regional filters, or to check city coverage before querying a birth location. Countries are sorted alphabetically by name. Covers Europe, Americas, Asia, Middle East, Africa, and Oceania.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | – | Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens. |
| limit | integer | – | Maximum items to return per page. Range: 1-250, default 50. |
| offset | integer|null | – | Number of items to skip for pagination. Default 0. |
No output schema declared.
{}get_location_countries_iso2 Get cities in a country - Geocoding directory sorted by population ~262
Returns all cities for a specific country, identified by ISO 3166-1 alpha-2 code (e.g. DE for Germany, FR for France, GB for United Kingdom, US for United States). Each city includes geographic coordinates, IANA timezone, and DST-aware UTC offset for direct use in astrology birth chart, horoscope, transit, and panchang calculations. Cities sorted by population with the largest metropolitan areas first.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | – | Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens. |
| iso2 | string | yes | ISO 3166-1 alpha-2 country code, case-insensitive. Common codes: DE (Germany), FR (France), GB (United Kingdom), US (United States), ES (Spain), IT (Italy), NL (Netherlands), IN (India), BR (Brazil),… |
| limit | integer | – | Maximum items to return per page. Range: 1-100, default 20. |
| offset | integer|null | – | Number of items to skip for pagination. Default 0. |
No output schema declared.
{"iso2":"DE"}get_location_search Search cities worldwide - Geocoding autocomplete with coordinates and timezone ~416
Turn a place name into coordinates, an IANA timezone and a DST-aware UTC offset, across 235,000+ cities and towns in 240+ countries. Coverage reaches rural towns of a few hundred people and every administrative seat, so a birthplace outside a major metro resolves as reliably as a capital. Matching is case-insensitive, accent-insensitive and partial, so ber matches Berlin, Bern and Bergen, native scripts are transliterated, and historic names resolve to the current place, so bombay returns Mumbai and peking returns Beijing. Results are ordered by match quality first and population second, so an exactly named small town is never buried under a larger city that merely shares its opening letters. Built for birth chart location pickers, horoscope apps, event scheduling, and any feature that needs place-to-coordinates resolution.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | – | Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens. |
| limit | integer | – | Maximum items to return per page. Range: 1-50, default 10. |
| offset | integer|null | – | Number of items to skip for pagination. Default 0. |
| q | string | yes | Place to search for, written the way a person would. Accepts a bare city (berlin), a city plus country (berlin germany), a comma-qualified place (richfield, utah), a fully qualified place (richfield,… |
No output schema declared.
{"q":"berlin"}What is the Location and Timezone MCP Server by RoxyAPI server?
Location and Timezone MCP Server by RoxyAPI is listed in the public MCP registry as com.roxyapi/location. City geocoding and timezone resolution for birth data, for AI agents, one API key. This page covers its hosted endpoint (https://roxyapi.com/mcp/location).
Is the Location and Timezone MCP Server by RoxyAPI server safe to use?
Location and Timezone MCP Server by RoxyAPI scores 89 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 Location and Timezone MCP Server by RoxyAPI server expose?
Location and Timezone MCP Server by RoxyAPI exposes 3 tools: get_location_search, get_location_countries, get_location_countries_iso2. Their descriptions and schemas cost roughly 858 tokens of context every time the server is loaded.
Does the Location and Timezone MCP Server by RoxyAPI server require authentication?
No. We connected to Location and Timezone MCP Server by RoxyAPI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Location and Timezone MCP Server by RoxyAPI server still maintained?
Location and Timezone MCP Server by RoxyAPI 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.