# MEO Preflight (remote · api.machineeconomyobservatory.com)

Read-only machine payment preflight using dated MEO evidence, with explicit unknowns.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.machineeconomyobservatory.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-machineeconomyobservatory-meo-preflight/api.md), [page](https://verifymcp.io/servers/com-machineeconomyobservatory-meo-preflight/api)

## Channel facts

- Endpoint: `https://api.machineeconomyobservatory.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## 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-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 362 tokens (~362/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Tools include usage examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 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.

## Install

### How do I install the MEO Preflight MCP server?

MEO Preflight is a hosted endpoint at https://api.machineeconomyobservatory.com/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 com-machineeconomyobservatory-meo-preflight 'https://api.machineeconomyobservatory.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-machineeconomyobservatory-meo-preflight": {
      "url": "https://api.machineeconomyobservatory.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-machineeconomyobservatory-meo-preflight": {
      "type": "http",
      "url": "https://api.machineeconomyobservatory.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-machineeconomyobservatory-meo-preflight]
url = "https://api.machineeconomyobservatory.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-machineeconomyobservatory-meo-preflight": {
      "type": "remote",
      "url": "https://api.machineeconomyobservatory.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-machineeconomyobservatory-meo-preflight --url 'https://api.machineeconomyobservatory.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-machineeconomyobservatory-meo-preflight:
    url: "https://api.machineeconomyobservatory.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-machineeconomyobservatory-meo-preflight": {
      "Transport": "http",
      "Url": "https://api.machineeconomyobservatory.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-machineeconomyobservatory-meo-preflight -t streamable-http -u 'https://api.machineeconomyobservatory.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-machineeconomyobservatory-meo-preflight": {
      "type": "http",
      "url": "https://api.machineeconomyobservatory.com/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-09-20 (score 68, +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-09-19 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-18 (score 67)

First indexed and scored.

## MCP tools (1)

### `preflight_machine_payment` (~319 tokens)

Preflight a machine payment

Before paying an unfamiliar machine service, call this read-only tool to compare the proposed resource, payment destination, network, asset and amount with MEO's dated economic history. Returns observed payment-term matches or changes, settlement/buyer/activity context when available, evidence freshness, and explicit unknowns. It does not execute or approve payment and never interprets missing evidence as safe. Pilot scope: two services; third-party public probe observations retained by MEO, not independently verified settlements. Settlement/buyer history, current activity and payment destination history are UNKNOWN. Evidence may be stale. Invocation example: {"resource_url":"https://blockrun.ai/api/v1/exa/search","pay_to":"0x0000000000000000000000000000000000000001","network":"eip155:8453","asset":"USDC","amount":"0.011"}

Input parameters:

- `amount` (string, required): Nonnegative decimal asset units, maximum six decimal places. Not atomic units. No exponent notation.
- `asset` (string, required): v0.1 supports source-reported USDC currency label only; no token contract validation.
- `network` (string, required): CAIP-style network; v0.1 supports eip155:8453 only.
- `pay_to` (string, required): Proposed recipient; EVM networks require a 0x-prefixed 40-hex-character address. Never logged or interpreted as wallet ownership.
- `resource_url` (string, required): Public HTTPS resource URL, no query, credentials or fragment. Exact resource matching only; never fetched.

Output parameters:

- `current_activity` (object)
- `economic_history` (object)
- `evidence` (object)
- `evidence_confidence` (object)
- `evidence_freshness` (object)
- `evidence_outcome`
- `limitations` (array)
- `match_status` (string)
- `material_findings` (array)
- `payment_term_comparisons` (object)
- `request_id` (string)
- `resolved_service`
- `result_state` (string)
- `version`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-machineeconomyobservatory-meo-preflight/api#diagnostics

## Score history

- 2026-09-20: 68
- 2026-09-19: 67
- 2026-09-18: 67

## Common questions

### What is the MEO Preflight MCP server?

MEO Preflight is an MCP server listed in the public MCP registry as com.machineeconomyobservatory/meo-preflight. Read-only machine payment preflight using dated MEO evidence, with explicit unknowns. This page covers its hosted endpoint (https://api.machineeconomyobservatory.com/mcp).

### Is the MEO Preflight MCP server safe to use?

MEO Preflight scores 68 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 MEO Preflight MCP server expose?

MEO Preflight exposes 1 tool: preflight_machine_payment. Their descriptions and schemas cost roughly 319 tokens of context every time the server is loaded.

### Does the MEO Preflight MCP server require authentication?

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

### Is the MEO Preflight MCP server still maintained?

MEO Preflight 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.

## Links

- Remote endpoint: https://api.machineeconomyobservatory.com/mcp
- Website: https://meo-preflight2.twooscoops.workers.dev/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/com-machineeconomyobservatory-meo-preflight/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-machineeconomyobservatory-meo-preflight/api.json
- HTML version of this page: https://verifymcp.io/servers/com-machineeconomyobservatory-meo-preflight/api