# Flat Earth Science (remote · flatearthscience.org)

Earth curvature, horizon, flight, Sun and daylight calculators plus tested flat-earth claims.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `flatearthscience.org`: 78/100 (this document), [markdown](https://verifymcp.io/servers/org-flatearthscience-flatearthscience-org/api-mcp.md), [page](https://verifymcp.io/servers/org-flatearthscience-flatearthscience-org/api-mcp)

## Channel facts

- Endpoint: `https://flatearthscience.org/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1855 tokens (~206/item across 9 items; 8 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Flat Earth Science MCP server?

Flat Earth Science is a hosted endpoint at https://flatearthscience.org/api/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.

### Claude

```bash
claude mcp add --transport http org-flatearthscience-flatearthscience-org 'https://flatearthscience.org/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-flatearthscience-flatearthscience-org": {
      "url": "https://flatearthscience.org/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-flatearthscience-flatearthscience-org": {
      "type": "http",
      "url": "https://flatearthscience.org/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-flatearthscience-flatearthscience-org]
url = "https://flatearthscience.org/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-flatearthscience-flatearthscience-org": {
      "type": "remote",
      "url": "https://flatearthscience.org/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-flatearthscience-flatearthscience-org --url 'https://flatearthscience.org/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-flatearthscience-flatearthscience-org:
    url: "https://flatearthscience.org/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-flatearthscience-flatearthscience-org": {
      "Transport": "http",
      "Url": "https://flatearthscience.org/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-flatearthscience-flatearthscience-org -t streamable-http -u 'https://flatearthscience.org/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-flatearthscience-flatearthscience-org": {
      "type": "http",
      "url": "https://flatearthscience.org/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 74)

First indexed and scored.

## MCP tools (8)

### `calculate_curvature` (~278 tokens)

Earth curvature calculator

Calculates how much of a distant target the Earth's curvature hides, from the surface distance, the observer's eye height, the target's height and an assumed refraction coefficient. Returns the hidden and visible height, the tangent-plane drop, the horizon distance and dip, the maximum mutual sight-line range and the midpoint bulge on a smooth sphere of radius 6,371.0084 km.

Input parameters:

- `distance` (number, required): Surface distance between the observer and the target, along the ground: 0 to 1000 km, or 0 to 621 miles when units is imperial.
- `eyeHeight` (number): Height of the observer's eye above the surface: 0 to 1000 m, or feet when units is imperial. Defaults to 2 m (6.56 ft).
- `refraction` (number): Assumed refraction coefficient k from -0.3 to 0.3: 0 is straight rays and positive values bend rays toward the surface. Defaults to 0.
- `targetHeight` (number): Height of the target's top above the same surface: 0 to 1000 m, or feet when units is imperial. Defaults to 10 m (32.8 ft).
- `units` (string): Metric uses kilometres and metres; imperial uses miles and feet. Metric without it.

Output parameters:

- `item` (object)
- `request` (object)
- `view` (string)

### `get_horizon_distance` (~163 tokens)

Horizon distance

Gives the distance to the horizon from an eye height above a smooth sphere, and how far a taller object such as a mast stays in straight sight. Returns the observer's horizon distance, the range added by the target height and the maximum shared sightline.

Input parameters:

- `eyeHeight` (number, required): Height of the observer's eye above the water or ground: 0.1 to 1000 m, or feet when units is imperial.
- `targetHeight` (number): Height of the taller object's top above the same surface: 0 to 1000 m, or feet when units is imperial. Defaults to 10 m (32.8 ft).
- `units` (string): Metric uses kilometres and metres; imperial uses miles and feet. Metric without it.

Output parameters:

- `item` (object)
- `request` (object)
- `view` (string)

### `compare_flat_map_distance` (~180 tokens)

Flat map against the sphere

Compares the distance between two cities on a north-polar flat-Earth map with their great-circle distance over a sphere. Returns both distances and the factor by which the map stretches or shrinks the pair.

Input parameters:

- `from` (string, required): First city, one of the website's 20 cities: Anchorage, Auckland, Buenos Aires, Cape Town, Dubai, Johannesburg, Lima, London, Los Angeles, Mexico City, Moscow, Mumbai, Nairobi, New York, Perth, Santia…
- `to` (string, required): Second city, one of the website's 20 cities: Anchorage, Auckland, Buenos Aires, Cape Town, Dubai, Johannesburg, Lima, London, Los Angeles, Mexico City, Moscow, Mumbai, Nairobi, New York, Perth, Santi…

Output parameters:

- `item` (object)
- `request` (object)
- `view` (string)

### `get_flight_distance` (~271 tokens)

Flight distance

Calculates the great-circle distance between two places in kilometres, miles and nautical miles, with the initial and final compass bearings. Each end is one of the website's 20 cities or a latitude and longitude.

Input parameters:

- `from` (string): Departure city, one of Anchorage, Auckland, Buenos Aires, Cape Town, Dubai, Johannesburg, Lima, London, Los Angeles, Mexico City, Moscow, Mumbai, Nairobi, New York, Perth, Santiago, São Paulo, Singap…
- `fromLatitude` (number): Departure latitude in degrees, north positive: -90 to 90.
- `fromLongitude` (number): Departure longitude in degrees, east positive: -180 to 180.
- `to` (string): Arrival city, one of Anchorage, Auckland, Buenos Aires, Cape Town, Dubai, Johannesburg, Lima, London, Los Angeles, Mexico City, Moscow, Mumbai, Nairobi, New York, Perth, Santiago, São Paulo, Singapor…
- `toLatitude` (number): Arrival latitude in degrees, north positive: -90 to 90.
- `toLongitude` (number): Arrival longitude in degrees, east positive: -180 to 180.

Output parameters:

- `item` (object)
- `request` (object)
- `view` (string)

### `get_sun_position` (~243 tokens)

Sun position

Calculates the Sun's altitude and compass bearing at a place, date and UTC time, with the shadow of a 1 m upright and the day's sunrise and sunset in UTC. A place is one of the website's 20 cities or a latitude and longitude; without a date and time the result is for the current moment.

Input parameters:

- `date` (string): UTC date as YYYY-MM-DD, from 1900 to 2100. Defaults to today in UTC.
- `latitude` (number): Latitude in degrees, north positive: -90 to 90.
- `longitude` (number): Longitude in degrees, east positive: -180 to 180.
- `place` (string): City, one of Anchorage, Auckland, Buenos Aires, Cape Town, Dubai, Johannesburg, Lima, London, Los Angeles, Mexico City, Moscow, Mumbai, Nairobi, New York, Perth, Santiago, São Paulo, Singapore, Sydne…
- `time` (string): UTC time as HH:MM on a 24-hour clock. Defaults to the current time when no date is given, otherwise to 12:00.

Output parameters:

- `item` (object)
- `request` (object)
- `view` (string)

### `get_daylight_hours` (~207 tokens)

Daylight hours

Calculates the length of daylight at a place on a date, with sunrise and sunset in UTC, for the UTC day from midnight to midnight. A place is one of the website's 20 cities or a latitude with an optional longitude.

Input parameters:

- `date` (string): UTC date as YYYY-MM-DD, from 1900 to 2100. Defaults to today in UTC.
- `latitude` (number): Latitude in degrees, north positive: -90 to 90.
- `longitude` (number): Longitude in degrees, east positive: -180 to 180. Defaults to 0 when only a latitude is given; it sets the UTC sunrise and sunset times.
- `place` (string): City, one of Anchorage, Auckland, Buenos Aires, Cape Town, Dubai, Johannesburg, Lima, London, Los Angeles, Mexico City, Moscow, Mumbai, Nairobi, New York, Perth, Santiago, São Paulo, Singapore, Sydne…

Output parameters:

- `item` (object)
- `request` (object)
- `view` (string)

### `compare_true_size` (~132 tokens)

True size on a Mercator map

Shows how much a Mercator map distorts a country's area, from its real area and the latitude it is drawn at. Returns the real area, the area multiplier at the country's own latitude and at a chosen latitude, and the size it appears at each. Covers the nine countries and regions in the website's size table.

Input parameters:

- `country` (string, required): Greenland, Alaska, Russia, Canada, United Kingdom, Australia, India, Brazil or Africa.
- `latitude` (number): Latitude in degrees to move the country to, north positive: -85 to 85. Defaults to the equator, 0.

Output parameters:

- `item` (object)
- `request` (object)
- `view` (string)

### `find_claims` (~109 tokens)

Tested claims

Searches the website's tested claims and flat-earth investigations, or returns one by id. Each result gives the claim, the verdict, the key evidence and the link to its page; an empty query lists all of them.

Input parameters:

- `id` (string): Exact claim id returned by an earlier search, for the full claim, verdict and evidence.
- `query` (string): Words to look for in a claim's title, topic or summary, such as moon landing or horizon. Empty lists every claim.

Output parameters:

- `item` (object)
- `items` (array)
- `nextCursor` (string|null)
- `pageSize` (integer)
- `query` (string)
- `request` (object)
- `total` (integer)
- `view` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-flatearthscience-flatearthscience-org/api-mcp#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 75
- 2026-11-13: 75
- 2026-11-12: 74
- 2026-11-11: 74

## Common questions

### What is the Flat Earth Science MCP server?

Flat Earth Science is an MCP server listed in the public MCP registry as org.flatearthscience/flatearthscience-org. Earth curvature, horizon, flight, Sun and daylight calculators plus tested flat-earth claims. This page covers its hosted endpoint (https://flatearthscience.org/api/mcp).

### Is the Flat Earth Science MCP server safe to use?

Flat Earth Science scores 78 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 Flat Earth Science MCP server expose?

Flat Earth Science exposes 8 tools: calculate_curvature, get_horizon_distance, compare_flat_map_distance, get_flight_distance, get_sun_position, and 3 more. Their descriptions and schemas cost roughly 1,583 tokens of context every time the server is loaded.

### Does the Flat Earth Science MCP server require authentication?

No. We connected to Flat Earth Science without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Flat Earth Science MCP server still maintained?

Flat Earth Science is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Flat Earth Science MCP server?

VerifyMCP ran 14 checks on Flat Earth Science, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://flatearthscience.org/api/mcp
- Repository: https://github.com/pyxlino/flatearthscience-mcp
- Website: https://flatearthscience.org/
- Changelog RSS feed: https://verifymcp.io/servers/org-flatearthscience-flatearthscience-org/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-flatearthscience-flatearthscience-org/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/org-flatearthscience-flatearthscience-org/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/org-flatearthscience-flatearthscience-org/api-mcp
