MEO Preflight MCP server
com.machineeconomyobservatory/meo-preflightmachineeconomyobservatory.comstreamable-httpv0.2.0Scanned
Read-only machine payment preflight using dated MEO evidence, with explicit unknowns.
1 tool: 1 do something that can't be undone.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the MEO Preflight MCP server can do
The MEO Preflight MCP server is published by machineeconomyobservatory.com, a domain the MCP Registry verified. It has 1 tool. It can do things that cannot be undone, such as sending, paying or publishing (preflight_machine_payment), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 2 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 0.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
1 tool
Can't be undone 1Claude Code: ask
preflight_machine_paymentBefore paying an unfamiliar machine service, call this read-only tool to compare the proposed resource, payment destination, network, asset and amount with MEO's dated economic his…2 findings
Why it is in this group
- The name "preflight_machine_payment" says "payment": a word that usually means money moves, which cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The input schema at properties.resource_url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.resource_url.description: "Public HTTPS resource URL, no query, credentials or fragment. Exact resource matching on..."
- Warn
The server marks "preflight_machine_payment" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "preflight_machine_payment" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Before paying an unfamiliar machine service, call this read-only tool to compare the proposed resource, payment destination, network, asset and amount with MEO's dated economic history. Returns observed payment-term matches or changes, settlement/buyer/activity context when available, evidence freshness, and explicit unknowns. It does not execute or approve payment and never interprets missing evidence as safe. Pilot scope: two services; third-party public probe observations retained by MEO, not independently verified settlements. Settlement/buyer history, current activity and payment destination history are UNKNOWN. Evidence may be stale. Invocation example: {"resource_url":"https://blockrun.ai/api/v1/exa/search","pay_to":"0x0000000000000000000000000000000000000001","network":"eip155:8453","asset":"USDC","amount":"0.011"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:42 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 irreversible). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.machineeconomyobservatory.com/mcp: tools/list returned 1 tool to an anonymous client, including preflight_machine_payment (irreversible)
Findings
Matches of fixed checks, with the text they matched.
The server marks "preflight_machine_payment" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "preflight_machine_payment" says "payment": a word that usually means money moves, which cannot be taken back.
The input schema at properties.resource_url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.resource_url.description: "Public HTTPS resource URL, no query, credentials or fragment. Exact resource matching on..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http meo-preflight https://api.machineeconomyobservatory.com/mcpclaude mcp add --transport http meo-preflight https://api.machineeconomyobservatory.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__meo-preflight__preflight_machine_payment"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as meo-preflight. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.machineeconomyobservatory/meo-preflight/verify?hash=61b886a1bcb3497e0cafb78df3f467f13bf32e990476e36bcf5697d78ff723b8" | jq -e '.changed == false'Pinned hash 61b886a1bcb3, from Nov 13, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.machineeconomyobservatory/meo-preflight/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.machineeconomyobservatory/meo-preflight)Source: MCP Registry. Synced Oct 21, 2026, 17:58 UTC.
MEO Preflight MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the MEO Preflight MCP server safe?
- No scan can promise that. What its definitions show: 1 tool, 1 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the MEO Preflight MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the MEO Preflight MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: preflight_machine_payment.
What tools does the MEO Preflight MCP server have?
- 1 tool: 1 irreversible. preflight_machine_payment.
Does the MEO Preflight MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the MEO Preflight MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the MEO Preflight MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.