原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Elevation MCP Server

作者:cyanheads版本 0.3.0i★ –i电脑或云端
注册名称io.github.cyanheads/elevation-mcp-server

安装

概览

作者提供的说明(英文原文)

Look up elevation worldwide, profile route ascent/descent, grid areas, check terrain line of sight.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在作者的服务器上运行:你向它提出的内容会经过他们的服务器。
  • 需要你自己填写: MCP_LOG_LEVEL, OPENTOPODATA_BASE_URL

你需要

  • 在云端运行无需安装任何东西,通过互联网连接
  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude:

  1. 打开 Settings → Connectors
  2. 点击 Add custom connector
  3. 粘贴下面的地址,然后点击 Add
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Add2https://…3
https://elevation.caseyjhand.com/mcp

或者在你的电脑上运行

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "elevation": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/elevation-mcp-server"
      ],
      "env": {
        "MCP_LOG_LEVEL": "your-value",
        "OPENTOPODATA_BASE_URL": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add --transport http elevation https://elevation.caseyjhand.com/mcp

或者在你的电脑上运行

claude mcp add elevation --env MCP_LOG_LEVEL=your-value --env OPENTOPODATA_BASE_URL=your-value -- npx -y @cyanheads/elevation-mcp-server

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "elevation": {
      "url": "https://elevation.caseyjhand.com/mcp"
    }
  }
}

或者在你的电脑上运行

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "elevation": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/elevation-mcp-server"
      ],
      "env": {
        "MCP_LOG_LEVEL": "your-value",
        "OPENTOPODATA_BASE_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "elevation": {
      "type": "http",
      "url": "https://elevation.caseyjhand.com/mcp"
    }
  }
}

或者在你的电脑上运行

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "elevation": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/elevation-mcp-server"
      ],
      "env": {
        "MCP_LOG_LEVEL": "your-value",
        "OPENTOPODATA_BASE_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

ChatGPT 只能连接互联网上的服务器:

  1. 打开网页版 ChatGPT → Settings → Connectors (Apps)
  2. 点击 Create 或 Add(部分套餐需要先在 Advanced 中开启 Developer mode)
  3. 粘贴下面的地址,起个名字,然后保存
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Create2https://…3
https://elevation.caseyjhand.com/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • MCP_LOG_LEVEL env
    Sets the minimum log level for output (e.g., 'debug', 'info', 'warn').
  • OPENTOPODATA_BASE_URL env
    Base URL of the Open Topo Data instance used outside USGS 3DEP coverage. Defaults to the public instance, paced to its published limits; any other URL is treated as a self-hosted instance, which must…

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 cyanheads 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    端点有响应

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    使用 OAuth 登录

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 32545 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 32545 个服务器的 79% 更新
  • 基础检查结果等于或优于此分类中其他 32545 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Elevation MCP Server 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

两种方式都可以:安装在你的电脑上,或者连接云端版本。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.3.0)于9天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, Python MCP

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者:formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新
安装

Python MCP

作者:Files-com

Local-only Python MCP server for the Files.com API.

在你的电脑上运行今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

@cyanheads/elevation-mcp-server Look up elevation worldwide, profile route ascent/descent, grid areas, check terrain line of sight via MCP. STDIO or Streamable HTTP. 4 Tools

Public Hosted Server: https://elevation.caseyjhand.com/mcp


Overview

Elevation and terrain analysis anywhere on Earth, from USGS 3DEP (1–30 m across the US) and Open Topo Data worldwide. Look up spot heights, measure a route's climbs and grades, find an area's high and low points, and check whether terrain blocks a line of sight. No API key required.

Tools
ToolDescription
elevation_get_pointsGround elevation at 1–100 coordinates, in meters and feet, with the dataset and resolution behind each value
elevation_get_profileSample a route at evenly spaced points and summarize distance, ascent, descent, elevation range, and steepest grades
elevation_get_gridSample a node grid over a bounding box and report its highest and lowest points, mean elevation, and relief
elevation_check_line_of_sightDecide whether terrain blocks the sightline between two points, with earth curvature and refraction, and check first Fresnel zone clearance for radio links
Agent skill

The elevation-guide covers route geometry, candidate high-point refinement, and visual or radio sightline assessment. Plugin installs discover it in root skills/; npm, Docker, and MCPB distributions include it. MCP clients can read skill://elevation-guide/SKILL.md as a resource or use the Skills extension.

Capability reference

Every successful result includes vertical_reference on both response surfaces. Public SRTM uses EGM96; NAVD88 is typical for 3DEP in the conterminous US, but the returned raster reference is unverified and can vary elsewhere. Mapzen and self-hosted Open Topo Data references are unknown/variable. No-data-only results establish no height reference. Heights are returned without transformation; mixed datasets are not normalized to a common datum. water_surface_m needs a compatible terrain reference; zero or source: opentopodata alone does not establish compatibility.

elevation_get_points tool
  • points: 1–1,000 {lat, lon} objects in decimal degrees (WGS84), or a single point. Only the first 100 are validated and sampled; the remainder stays unvalidated
  • requested_points, processed_points, and remaining_points count submitted positions, including duplicates and misses. next_offset is the index after this call's processed prefix, or null when exhausted; continue with originalPoints.slice(next_offset), where originalPoints is the array submitted in that call. Use each newly submitted array for the next slice
  • Each point comes back ok or no_data (a miss never fails the call), with elevation_m / elevation_ft, dataset, and resolution_m (omitted for mapzen); 3DEP answers add raster_id and acquisition_date. points_with_data counts the hits

elevation_get_profile tool
  • path: 2–1,000 vertices in travel order (consecutive duplicates dropped); samples: 2–250 evenly spaced points along it, endpoints included (default 100)
  • summary carries total_distance_m, ascent_m / descent_m (and feet), start, end, min, and max elevation, highest_point / lowest_point, and max_grade_pct / min_grade_pct with where each occurs; ascent depends on the reported sample_interval_m. Fails as degenerate_path (under 1 m of route), antipodal_path (add an intermediate waypoint between the identified zero-based input vertices), or no_coverage (no sample has data)
  • include_samples (default true) returns samples[] (distance, position, elevation, grade, dataset, and resolution per sample); false omits it and the sample table, and the rest of the result is unchanged

elevation_get_grid tool
  • south, west, north, east edges in decimal degrees (a box can't cross longitude 180); rows and cols 2–25 each (default 10), with rows × cols at most 250
  • elevations_m and cell_datasets matrices indexed row (row 0 north, column 0 west, null without data), plus summary.highest, summary.lowest, mean_elevation_m, and relief_m. Fails as invalid_bbox, too_many_cells, or no_coverage
  • Nodes are point samples with the edges included, not cell averages

elevation_check_line_of_sight tool
  • observer and target points, at most 1,000 km apart; observer_height_m (default 1.7) and target_height_m (default 0), each 0–10,000 m above ground; earth_model flat, geometric, optical (default, κ 0.13), or radio (κ 0.25); samples 3–250 (default 100); optional water_surface_m (-500 to 9,000) and frequency_mhz (30–300,000)
  • verdict is clear, blocked, or indeterminate (samples without data leave the line unconfirmed), with min_clearance_m / min_clearance_ft, the limiting_point, and the first_obstruction when blocked. Fails as same_endpoints (under 1 m apart), sightline_too_long (over 1,000 km apart), or endpoint_no_data
  • frequency_mhz adds fresnel: a sufficient, insufficient, or indeterminate verdict against the 60% free-space bar of the first Fresnel zone, min_clearance_ratio (clearance over zone radius), and the sample that limits it, which is often not limiting_point
  • Terrain only: buildings and vegetation count only as far as the elevation source captures them. Where Mapzen reports sea-floor depth, clearance is measured to the sea surface; USGS 3DEP values below 0 m (bay floor in some bays, or dry land) count as received unless water_surface_m sets a water level, which then applies to every sample

Failures shared by every tool
ReasonCodeWhen
usgs_unavailableServiceUnavailableUSGS 3DEP did not answer or rejected the request; data.retryable says whether retrying can help
opentopodata_unavailableServiceUnavailableOpen Topo Data did not answer, rejected the request, or sent an unusable response; data.retryable as above
opentopodata_rate_limitedRateLimitedOpen Topo Data kept answering HTTP 429, or asked for a wait over 8 s; data.retryAfter in seconds when it sent one of at most a day
opentopodata_daily_limitRateLimitedPublic instance only: this server already sent 1,000 requests in the trailing 24 hours, so none was sent; data.retryAfter is the seconds until a slot frees
opentopodata_config_rejectedConfigurationErrorThe instance at OPENTOPODATA_BASE_URL answered 401, 403, or 404, redirected (self-hosted only; never followed), lacks srtm30m or mapzen, caps locations below 100, or answered from a dataset this server didn't request; the operator must fix it
sampling_deadline_exceededTimeoutThe 45 s sampling budget ran out (data.provider names the provider it was waiting on), or other calls' queued USGS 3DEP lookups left no time for this call's, so it sent none and data.retryAfter is the seconds until they drain

A coverage miss is never an error: that point has no data. Any provider failure fails the whole call with no partial result.

Features

Built on @cyanheads/mcp-ts-core: stdio and Streamable HTTP transports, pluggable auth (none / jwt / oauth), swappable storage (in-memory, filesystem, Supabase, Cloudflare KV/R2/D1), structured logging with optional OpenTelemetry tracing.

Elevation-specific:

  • source on every tool: auto (default) queries USGS 3DEP inside its coverage and sends 3DEP misses and everything outside it to Open Topo Data; usgs_3dep and opentopodata pin one provider. Only a coverage miss falls back, never an outage
  • Open Topo Data answers from SRTM GL1 v3 (about 30 m, land between 60°N and 56°S), then Mapzen terrain tiles where SRTM has no tile: high latitudes, Antarctica, and ocean bathymetry
  • Per-call caps of 100 points or 250 samples or grid cells, inside a 45 s sampling budget; each 3DEP point is its own request (6 concurrent, 10 per second), while Open Topo Data takes 100 points per request
  • The public Open Topo Data instance is paced under its published limits: one request at a time, starts at least 1.1 s apart, at most 1,000 in any trailing 24 hours per server process
  • Profiles, grids, and sightlines are computed locally from point samples, with great-circle distances and resampling and earth curvature with standard refraction

Agent-friendly output:

  • Provenance on every value: each point, profile sample, grid cell, and sightline point names its dataset (usgs_3dep, srtm30m, mapzen) and, except for Mapzen, its resolution_m (resolution_m_range on profiles and grids); computed results add datasets_used counts, and a Sources: line credits every dataset that answered
  • Absent stays absent: a point or sample without data omits its elevation and a grid cell is null, never 0; summaries report how many values had data
  • Notices flag what changes interpretation: results mixing 3DEP and Open Topo Data, Mapzen values below 0 m (sea-floor depths), 3DEP values below 0 m on a sightline, sample spacing coarser or finer than the source, thin clearance margins, and a clear radio path short of 60% Fresnel clearance

Getting started

Connect to the public instance:

claude mcp add --transport http elevation-mcp-server https://elevation.caseyjhand.com/mcp

Every hosted caller shares one Open Topo Data allowance of 1,000 requests a day. Under auto, 3DEP answers inside its coverage and Open Topo Data handles the rest. For sustained global use, run your own instance:

claude mcp add elevation-mcp-server -- npx -y @cyanheads/elevation-mcp-server

Other MCP clients use this local configuration:

`json

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx