# remote.observer — machine-economy observatory (remote · remote.observer)

Free MCP window into a live autonomous machine-economy experiment: telemetry, hypothesis scoreboard.

- Trust score: 73/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `remote.observer`: 73/100 (this document), [markdown](https://verifymcp.io/servers/observer-remote-remote-observer/remote.md), [page](https://verifymcp.io/servers/observer-remote-remote-observer/remote)

## Channel facts

- Endpoint: `https://remote.observer/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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**: 49/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 426 tokens (~85/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the remote.observer — machine-economy observatory MCP server?

remote.observer — machine-economy observatory is a hosted endpoint at https://remote.observer/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 observer-remote-remote-observer 'https://remote.observer/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "observer-remote-remote-observer": {
      "url": "https://remote.observer/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "observer-remote-remote-observer": {
      "type": "http",
      "url": "https://remote.observer/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.observer-remote-remote-observer]
url = "https://remote.observer/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add observer-remote-remote-observer --url 'https://remote.observer/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  observer-remote-remote-observer:
    url: "https://remote.observer/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "observer-remote-remote-observer": {
      "Transport": "http",
      "Url": "https://remote.observer/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add observer-remote-remote-observer -t streamable-http -u 'https://remote.observer/mcp'
```

### Other

```json
{
  "mcpServers": {
    "observer-remote-remote-observer": {
      "type": "http",
      "url": "https://remote.observer/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-11 (score 73, +1)

- [security] Stability: 0.97 → pass

### 2026-09-09 (score 72, +1)

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

### 2026-09-07 (score 71, +1)

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

### 2026-09-04 (score 70, +1)

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

### 2026-09-02 (score 69, +1)

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

### 2026-08-31 (score 68, +1)

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

### 2026-08-29 (score 67, +1)

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

### 2026-08-27 (score 66, +1)

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

## MCP tools (5)

### `bazaar_pulse` (~69 tokens)

What changed in the x402 Bazaar catalogue in the last day — listings added, removed and repriced, with catalogue totals. Computed from full-catalogue snapshots taken daily since July 2026 and diffed by resource URL, so every count is of real rows, not an estimate.

### `find_provider` (~106 tokens)

Find x402 endpoints worth calling — ranked by the catalogue's own reported paying buyers and call volume, how many days they have stayed listed and whether their price held. Built from 30 days of daily catalogue snapshots and returned as a positive-only shortlist: absence is missing evidence, never a bad review.

Input parameters:

- `limit` (integer): How many listings to return (max 10).
- `query` (string): Case-insensitive substring of the service name; omit to rank the whole catalogue.

### `market_stats` (~84 tokens)

Ecosystem-wide x402 totals from the daily market scan, next to the live challenge, payment and revenue counters of one shop that actually runs paid endpoints and publishes what they earn. The market figures come from that scan; the shop figures are our own endpoints' meter, published as one seller's instrument — self-test settlements counted and published separately, never folded into the paid figure.

### `experiment_scoreboard` (~74 tokens)

The running scoreboard of an autonomous agent's market hypotheses — each claim, its target, its verdict, the value actually measured, and the creative lens (or control) it was drawn under. Every hypothesis is pre-registered before the evidence exists and scored by code on a fixed horizon, with refutations published exactly like confirmations.

### `crawler_watch` (~93 tokens)

Who is actually crawling the x402 economy — the top networks and countries behind payment challenges on a live paid endpoint, with that day's challenge, paid-call and disclosed self-test totals. Straight from one shop's edge telemetry, where measured new-listing pickup latency runs about 45 minutes, self-tests are counted apart from paid calls rather than netted out of them, and the traffic is indexers reading prices, not buyers.

## Diagnostics

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

## Score history

- 2026-09-20: 73
- 2026-09-19: 73
- 2026-09-18: 73
- 2026-09-17: 73
- 2026-09-16: 73
- 2026-09-15: 73
- 2026-09-14: 73
- 2026-09-13: 73
- 2026-09-12: 73
- 2026-09-11: 73
- 2026-09-10: 72
- 2026-09-09: 72
- 2026-09-08: 71
- 2026-09-07: 71
- 2026-09-06: 70
- 2026-09-05: 70
- 2026-09-04: 70
- 2026-09-03: 69
- 2026-09-02: 69
- 2026-09-01: 68
- 2026-08-31: 68
- 2026-08-30: 67
- 2026-08-29: 67
- 2026-08-28: 66
- 2026-08-27: 66
- 2026-08-26: 65
- 2026-08-25: 63
- 2026-08-24: 63
- 2026-08-23: 62
- 2026-08-22: 62

## Common questions

### What is the remote.observer — machine-economy observatory MCP server?

remote.observer — machine-economy observatory is an MCP server listed in the public MCP registry as observer.remote/remote-observer. Free MCP window into a live autonomous machine-economy experiment: telemetry, hypothesis scoreboard. This page covers its hosted endpoint (https://remote.observer/mcp).

### Is the remote.observer — machine-economy observatory MCP server safe to use?

remote.observer — machine-economy observatory scores 73 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 remote.observer — machine-economy observatory MCP server expose?

remote.observer — machine-economy observatory exposes 5 tools: bazaar_pulse, find_provider, market_stats, experiment_scoreboard, crawler_watch. Their descriptions and schemas cost roughly 426 tokens of context every time the server is loaded.

### Does the remote.observer — machine-economy observatory MCP server require authentication?

No. We connected to remote.observer — machine-economy observatory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the remote.observer — machine-economy observatory MCP server still maintained?

remote.observer — machine-economy observatory 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://remote.observer/mcp
- Repository: https://github.com/oblique-markets/oblique-core
- Website: https://remote.observer/
- Changelog RSS feed: https://verifymcp.io/servers/observer-remote-remote-observer/remote.xml
- Changelog JSON feed: https://verifymcp.io/servers/observer-remote-remote-observer/remote.json
- HTML version of this page: https://verifymcp.io/servers/observer-remote-remote-observer/remote