Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Geomelon is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
MCP server for the Geomelon geographic API — stdio and remote HTTP transports
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user geomelon-mcp '--' npx -y geomelon-mcp
# 2 — ask your agent for something these tools do
# search_cities_autocomplete, search_cities, get_city and 19 more
Geomelon costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Geomelon as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user geomelon-mcp '--' npx -y geomelon-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take GEOMELON_API_KEY (Your RapidAPI key for Geomelon. Optional: without it the server runs in keyless demo mode, exposing only the free search_cities_autocomplete tool.), PORT (Port to run HTTP MCP on) if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
22 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Fast country-scoped, language-specific city name prefix search backed by pre-built static files.
No parameter schema on file.
Search cities by name, country, population range, and more. Returns matching cities with geographic and translation data.
No parameter schema on file.
Get full details for a single city by its UUID.
No parameter schema on file.
Get all available name translations for a city by its UUID.
No parameter schema on file.
Get settlement-type classifications for a city (e.g. city, town, village) by its UUID.
No parameter schema on file.
Find cities nearest to given coordinates, ordered by distance.
No parameter schema on file.
Find the largest cities near given coordinates, ordered by population.
No parameter schema on file.
Calculate the distance in kilometres between two cities.
No parameter schema on file.
List countries with optional filtering by name prefix or telephone code. Supports localized names via preferredLanguages.
No parameter schema on file.
Get full details for a single country by its UUID, including translations and regions.
No parameter schema on file.
Get name translations for a country by its UUID.
No parameter schema on file.
Get all administrative regions belonging to a country by its UUID.
No parameter schema on file.
List administrative regions, optionally filtered by country.
No parameter schema on file.
Get full details for a single region by its UUID.
No parameter schema on file.
Get name translations for a region by its UUID.
No parameter schema on file.
Find cities near a given city. Resolves the city\
No parameter schema on file.
Get a city together with its full country and region details in one call.
No parameter schema on file.
Get a country\
No parameter schema on file.
Fetch full details for two cities and the distance between them in one call.
No parameter schema on file.
Search cities using a country name instead of an ISO code. Resolves the country first, then searches cities within it.
No parameter schema on file.
List languages available in the Geomelon database.
No parameter schema on file.
Get details for a single language by its UUID.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Geomelon or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (22 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
21 of the 22 recovered tools are registered only when !apiKey is false (dist/http.js:70) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 1.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
1 tool is registered unconditionally · 21 more only when !apiKey is false (dist/http.js:70) — typically when a key or option is configured. All 22 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_cities_autocomplete | no tags | |
| search_cities conditional | no tags | |
| get_city conditional | no tags | |
| get_city_translations conditional | no tags | |
| get_city_settlement_types conditional | no tags | |
| cities_by_coordinates_closest conditional | no tags | |
| cities_by_coordinates_largest conditional | no tags | |
| cities_distance conditional | no tags | |
| list_countries conditional | no tags | |
| get_country conditional | no tags | |
| get_country_translations conditional | no tags | |
| get_country_regions conditional | no tags | |
| list_regions conditional | no tags | |
| get_region conditional | no tags | |
| get_region_translations conditional | no tags | |
| find_cities_near_city conditional | no tags | |
| city_context conditional | no tags | |
| country_overview conditional | no tags | |
| compare_cities conditional | untrusted-input | untrusted-input: keyword "fetch" |
| search_cities_in_country conditional | no tags | |
| list_languages conditional | no tags | |
| get_language conditional | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.1.1. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Geomelon can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.