World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 104 tools.
Read-only verification evidence for paid machine services and buyer policy checks.
Pick the AI app you use, then copy the settings.
Passed 2/3 checks · What you ask goes through the maker’s server (verify.atinamos.co.uk)
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
Atinamos Evidencehttps://verify.atinamos.co.uk/mcpLeave Authentication as Claude detected it, then click Add
+ConnectorsAtinamos Evidence
Use Atinamos Evidence and tell me what you can do for me, then show me one thing✓ If Claude says it is using Atinamos Evidence or shows a Atinamos Evidence tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT on business plans only
ChatGPT Business, Enterprise or Edu on the web, added by a workspace admin or owner · On Free, Plus or Pro: your ChatGPT plan cannot connect MCP yet
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
Atinamos Evidencehttps://verify.atinamos.co.uk/mcpStart a new chat and pick Atinamos Evidence from your plugins before typing
Use Atinamos Evidence and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using Atinamos Evidence or shows a Atinamos Evidence tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user evidence https://verify.atinamos.co.uk/mcpYou should see Atinamos Evidence listed as connected
Use Atinamos Evidence and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Atinamos Evidence or shows a Atinamos Evidence tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use Atinamos Evidence and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Atinamos Evidence or shows a Atinamos Evidence tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use Atinamos Evidence and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Atinamos Evidence or shows a Atinamos Evidence tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://verify.atinamos.co.uk/mcpJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user evidence https://verify.atinamos.co.uk/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"evidence": {
"url": "https://verify.atinamos.co.uk/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"evidence": {
"type": "http",
"url": "https://verify.atinamos.co.uk/mcp"
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
The server did not answer when we last checked, so we could not read its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 12, 2026
The registry name was verified against the domain atinamos.co.uk (the registry checks domain ownership)
Code last changed 2 months ago
We have not read this repo from GitHub yet
Did not respond within 6 seconds when we checked
Did not respond within 6 seconds when we checked
Not checked yet; we read the tool list when we check the endpoint
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed 2 months ago, and the latest version (1.0.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT Business and above.
In the same category: World Monitor, Claude Flow, Windmill
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 104 tools.
AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Public research, schemas and technical evidence for Atinamos independent verification of paid AI-agent and machine services.
Human-readable research: https://verify.atinamos.co.uk Technical evidence: this repository
You can pay to be tested. You cannot pay to be trusted.
Atinamos produces scoped evidence. The buyer decides what that evidence means under its own policy.
Atinamos does not issue a universal trust score, certification, approval, safe/unsafe verdict or permanent provider rating.
Read the canonical public status first:
The main technical milestone is now the first unattended generic external Assurance execution from an already-frozen plan.
service: POST https://keyronne.com/api/json-repair
run: 1b5bc844-368c-445a-8f84-e62be6d88baa adapter: generic-transaction-fulfilment v1.0 state: PLAN_FROZEN → COMPLETE spend: 0.001 USDC
One internal production coordinator invocation handled the routine paid execution stages without an operator manually stepping x402 challenge acquisition, payment signing, paid dispatch, settlement observation, fulfilment evaluation or Verification publication.
Independent Base settlement:
transaction: 0xc42bb177c41d21a56e9d3c02546fa8ebeda911cff3bc1139169a61c89f7b495c
block: 50996015
Signed evidence:
atinamos:receipt:10e40afd-f6b1-57bd-9c1e-0a4a1695a428
Observed evidence layers:
PAYMENT SETTLED
FULFILMENT FULFILLED CORRECTNESS NOT_EVALUATED QUALITY NOT_EVALUATED
The service returned the advertised kind of JSON deliverable. Atinamos did not infer semantic correctness or quality from that fulfilment.
The Keyronne run began at PLAN_FROZEN.
It proves:
frozen independent plan
→ real bounded external purchase → independent Base settlement observation → fulfilment evidence → immutable Verification package → signed receipt → COMPLETE
It does not yet prove the complete public seller journey:
raw seller URL
→ non-spending discovery → scope explanation → independent frozen plan → seller funding → durable queue → proven Runner → signed evidence
That seller product journey is now the main development lane.
PROVEN ENGINE
↓ SELLER PRODUCT ↓ FIRST USERS ↓ REVENUE / MARKET FEEDBACK
Human seller productisation comes first. A later AI-seller API/MCP should use the same underlying Assurance run/order model rather than introducing another execution engine.
On 6 September 2026, Atinamos completed the first end-to-end external deterministic commissioning of the current Assurance Runner → Verification publication path against:
POST https://api.ibanforge.com/v1/iban/validate
Two bounded x402 calls were made at 0.005 USDC each. Settlement was independently observed on Base, useful fulfilment returned, and the returned valid field matched independently derived ISO 13616 MOD-97 expectations for one valid and one invalid fixture.
total observed test spend: 0.010 USDC
Base settlements observed: 2 successful fulfilments: 2 independent controls passed: 2 / 2 signed Assurance receipts: 2
That run was human-triggered commissioning. It remains an important earlier milestone and should not be retroactively described as unattended.
On 28 August 2026, an Atinamos-operated bounded buyer was given a task, maximum spend and buyer policy. It independently searched an external x402 marketplace, checked exact-route viability, queried published Atinamos evidence, applied its own policy, selected an external seller without the human naming the seller, made a bounded payment, consumed the result and validated the purchased output.
Final clean run:
selected seller: Keyronne JSON Repair
payment: 0.001 USDC on Base x402: v2 / exact paid HTTP: 200 proof3_complete: true
This proves the controlled Atinamos buyer experiment. It does not establish widespread external-agent adoption of Atinamos evidence.
Also on 28 August 2026, Atinamos observed an unrelated external client purchase Atinamos JSON Repair for 0.005 USDC through x402 and receive successful HTTP fulfilment.
This establishes external commercial use of an Atinamos machine service. It does not establish that the purchaser was definitely an autonomous AI agent.
The repository deliberately retains successful and unsuccessful observations, including:
See EVIDENCE_INDEX.md for the current consolidated index.
Atinamos keeps these evidence layers separate:
PAYMENT
Did payment settle?
FULFILMENT Did the advertised kind of deliverable return?
CORRECTNESS Was the returned content independently checked?
QUALITY Was subjective quality independently evaluated?
Guardrails:
UNKNOWN != UNSAFE
SETTLED != FULFILLED FULFILLED != CORRECT CORRECT != HIGH QUALITY SIGNED RECEIPT != PERMANENT TRUST SAMPLE COUNT != RELIABILITY PERCENTAGE
Endpoint and HTTP method are material evidence identity where applicable.
AI agents and developers can query selected published Atinamos evidence through the read-only Atinamos Evidence MCP:
https://verify.atinamos.co.uk/mcp
The MCP exposes published evidence and buyer-supplied policy evaluation. It does not expose wallet access, payment signing, verification-triggering writes or a universal trust verdict.
Atinamos exposes a bounded read-only projection of machine-service discovery observations:
GET https://verify.atinamos.co.uk/v1/market/search?q=<query>&limit=<1-50>
GET https://verify.atinamos.co.uk/v1/market/service/
Market Search reports observed listings and provenance. A market listing is not verification evidence.
Current signed Assurance evidence can be read using:
GET https://verify.atinamos.co.uk/v1/assurance/receipts/<receipt_id>
GET https://verify.atinamos.co.uk/v1/assurance/evidence?endpoint= &method=
Endpoint and HTTP method are material evidence identity.
Historical evidence should remain valid in the format in which it was issued rather than being silently rewritten.
This repository is the deliberately sanitised public technical publication layer for Atinamos Verification and Assurance research.
It may contain:
It does not contain:
GitHub is not where Atinamos Verification runs. It is where Atinamos publishes selected technical evidence and documentation for public scrutiny and machine consumption.
Copyright © 2026 MotionFil-AI.
See LICENSE.md for details.