Skip to content

remote observer MCP server

Which MCP servers are remote observer's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to remote observer

Whose server it is
  • Registry nameobserver.remote/remote-obserververified in the MCP registry

The registry name sits under remote.observer. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools5
  • Server calls itselfoblique-observer
  • Server version1.0.0
  • Protocol version2024-11-05

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 613 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "track listing churn and repricing across an agent market", the likely first call is bazaar_pulse.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer1174 ms
  • Space in an agent's context≈ 616 tokensthe definitions of all its tools (5), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 5 of 5

What an agent can do with it

  • not sure · watch live payments settle between agents on a shop
  • can do · track listing churn and repricing across an agent market
  • not sure · check paid endpoint prices and most-bought services over time

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers5 tools · read 2026-10-26
  • bazaar_pulse

    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…

  • find_provider

    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…

  • market_stats

    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…

  • experiment_scoreboard

    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…

  • crawler_watch

    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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "remote-observer": {
      "type": "http",
      "url": "https://remote.observer/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http remote https://remote.observer/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://remote.observer/mcp as a custom connector in the settings.

OpenAPI spec

84 paths, read 2026-10-26. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.