remote.observer — machine-economy observatory
REMOTE · REMOTE.OBSERVER · SCANNED SEP 20
Free MCP window into a live autonomous machine-economy experiment: telemetry, hypothesis scoreboard.
Available components
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. How we score → Why this is hard to score →
Endpoint Security49
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 426 tokens (~85/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
remote · remote.observer
claude mcp add --transport http observer-remote-remote-observer 'https://remote.observer/mcp'
{
"mcpServers": {
"observer-remote-remote-observer": {
"url": "https://remote.observer/mcp"
}
}
} {
"servers": {
"observer-remote-remote-observer": {
"type": "http",
"url": "https://remote.observer/mcp"
}
}
} [mcp_servers.observer-remote-remote-observer] url = "https://remote.observer/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"observer-remote-remote-observer": {
"type": "remote",
"url": "https://remote.observer/mcp",
"enabled": true
}
}
} openclaw mcp add observer-remote-remote-observer --url 'https://remote.observer/mcp' --transport streamable-http
mcp_servers:
observer-remote-remote-observer:
url: "https://remote.observer/mcp" {
"McpServers": {
"observer-remote-remote-observer": {
"Transport": "http",
"Url": "https://remote.observer/mcp"
}
}
} assistant mcp add observer-remote-remote-observer -t streamable-http -u 'https://remote.observer/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +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.
- 7 Sept 26 +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.
- 4 Sept 26 +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.
- 2 Sept 26 +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.
- 31 Aug 26 +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.
- 29 Aug 26 +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.
- 27 Aug 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://remote.observer/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=remote.observer | CN=WE1,O=Google Trust Services,C=US | 24 Jul 2026 | 22 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 56f2c1d666d6f21b131f796724685baa |
| SANs: remote.observer, *.remote.observer | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of remote.observer. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| observer. | present | 15964 | 13 | Verified |
| remote.observer. | present | 2371 | 13 | Verified |
| remote.observer. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://remote.observer/mcp | Verified | 200 | |
| http (plaintext) | http://remote.observer/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bazaar_pulse ~69
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
crawler_watch ~93
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
experiment_scoreboard ~74
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
find_provider ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many listings to return (max 10). |
| query | string | – | Case-insensitive substring of the service name; omit to rank the whole catalogue. |
No output schema declared.
No examples provided.
market_stats ~84
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
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.