Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Location and Timezone MCP Server by RoxyAPI

REMOTE · ROXYAPI.COM

City geocoding and timezone resolution for birth data, for AI agents, one API key.

Available components

0 this week 88 Trust /100

Last scanned (1 hour ago)

Scores higher than 96% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 888 tokens (~296/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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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 current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 28 Oct 26 −1
    • Tool “get_location_search” rewrote its description, which is the text the model reads security
  • 21 Oct 26 +8
    • Stability: fail → pass ▲ security
  • 20 Oct 26 0
    • Stability: unverified → fail ▼ security
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 19 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 3 Oct 26 0
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
  • 28 Sept 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 Sept 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
  • 21 Sept 26 0
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 2.0.0 ▼ security
    • “get_location_countries” changed the type of “offset”: integer|null → integer ▼ functional
    • “get_location_countries_iso2” changed the type of “offset”: integer|null → integer ▼ functional
    • “get_location_search” changed the type of “offset”: integer|null → integer ▼ functional
    • Tool “get_location_countries” now declares an output schema ▲ functional
    • Tool “get_location_countries_iso2” now declares an output schema ▲ functional
    • Tool “get_location_search” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
Diagnostics

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 · 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 23 Sept 2026 22 Dec 2026 ECDSA 256 ECDSA-SHA256 b253589252f3f4620e758a7554771c71
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'; img-src 'self' data: https:; font-src 'self'; connect-src 'self' https://challenges.cloudflare.com https://cloudflareinsights.com; frame-src 'self' 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
MCP tools · 3 exposed · ~888 tokens

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 →

Tool Tokens
get_location_countries ~179

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.

NameTypeReqDescription
compactboolean–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.
limitinteger–Maximum items to return per page. Range: 1-250, default 50.
offsetinteger–Number of items to skip for pagination. Default 0.
NameTypeReqDescription
countriesarrayyes–
limitnumberyes–
offsetnumberyes–
totalnumberyes–
{}
get_location_countries_iso2 ~261

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.

NameTypeReqDescription
compactboolean–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.
iso2stringyesISO 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),…
limitinteger–Maximum items to return per page. Range: 1-100, default 20.
offsetinteger–Number of items to skip for pagination. Default 0.
NameTypeReqDescription
citiesarrayyes–
limitnumberyes–
offsetnumberyes–
totalnumberyes–
{"iso2":"DE"}
get_location_search ~448

Turn a place name into coordinates, an IANA timezone and a DST-aware UTC offset, across 5,180,000+ cities, towns and villages in 240+ countries. Coverage reaches every village on record, whatever its population, 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. A full name typed ranks above its smaller namesakes, a few letters reach the best-known city first, and a state, province or country in the query picks the right one of many places with the same name. A town name that matches nothing returns no match, never the largest town in the region it names. Built for birth chart location pickers, horoscope apps, event scheduling, and any feature that needs place-to-coordinates resolution.

NameTypeReqDescription
compactboolean–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.
limitinteger–Maximum items to return per page. Range: 1-50, default 10.
offsetinteger–Number of items to skip for pagination. Default 0.
qstringyesPlace 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,…
NameTypeReqDescription
citiesarrayyes–
limitnumberyes–
offsetnumberyes–
totalnumberyes–
{"q":"berlin"}
Install

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

# add to Claude Code
claude mcp add --transport http com-roxyapi-location 'https://roxyapi.com/mcp/location'
Common questions

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 88 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 888 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.