Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Nothing to run from here
remote.observer — machine-economy observatory is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
5
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Free MCP window into a live autonomous machine-economy experiment: telemetry, hypothesis scoreboard.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http remote-observer-machine-economy-observatory-mcp https://remote.observer/mcp
# 2 — ask your agent for something these tools do
# bazaar_pulse, find_provider, market_stats and 2 more
remote.observer — machine-economy observatory costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
REAll 1 server
remote1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http remote-observer-machine-economy-observatory-mcp https://remote.observer/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Case-insensitive substring of the service name; omit to rank the whole catalogue. |
| limit | integer | no | How many listings to return (max 10). |
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 fig
No parameter schema on file.
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.
No parameter schema on file.
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 ind
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install remote.observer — machine-economy observatory or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish remote.observer — machine-economy observatory can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.