remote.observer — machine-economy observatory

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

Should I use this

Quality & Safety

B
Description quality
100%
Schema completeness
42%
Naming quality
84%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~530Tokens (tool definitions)
~244 BTypical response size
Minimal attention impact (0.41% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://remote.observer/mcpstreamable-http

What it can do

Tool inventory

Tools (5)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢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 real rows, not an estimate.

Input Schema

{
  "type": "object",
  "properties": {}
}
🟢find_provider(query, limit)

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 Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Case-insensitive substring of the service name; omit to rank the whole catalogue."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 10,
      "default": 5,
      "description": "How many listings to return (max 10)."
    }
  }
}
⚪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 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.

Input Schema

{
  "type": "object",
  "properties": {}
}
⚪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 evidence exists and scored by code on a fixed horizon, with refutations published exactly like confirmations.

Input Schema

{
  "type": "object",
  "properties": {}
}
⚪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, 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.

Input Schema

{
  "type": "object",
  "properties": {}
}

Recommended Prompts

search_research
Search for information about [topic] using remote.observer — machine-economy observatory
Expected tools: find_provider
find_specific
Find [specific item] using remote.observer — machine-economy observatory
Expected tools: find_provider

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded5 tools
verifiedversion not recorded5 tools