Atinamos Evidence

uk.co.atinamosPublished by atinamos.co.ukOfficial publisherv1.0.0Updated Oct 24, 2026

Read-only verification evidence for paid machine services and buyer policy checks.

The publisher's own server: Atinamos Agent Shop

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

A read-only remote MCP server for querying Atinamos's published verification evidence on paid machine services and evaluating it against a buyer's own policy.

What you can do
Query published Atinamos verification evidence for machine services, identified by endpoint and HTTP method, and read signed receipts by receipt ID. Evaluate that evidence against a buyer-supplied policy, leaving the verdict to the buyer. Search a bounded, read-only projection of observed machine-service market listings with their provenance. Read the published methodology, receipt specifications and schemas behind the evidence.
When to use it
Useful when an assistant or developer needs to check what independent evidence exists for a paid machine or AI-agent service before buying, or wants to apply a buyer policy to that evidence. It is not a trust score or a safe/unsafe verdict.
Requirements
A remote streamable HTTP endpoint; no package, account, API key or environment variable is declared. Network access to the Atinamos verification host is needed.
Before you install
Read-only: the server states it exposes no wallet access, payment signing, verification-triggering writes or universal trust verdict. Evidence layers are kept separate, so settled payment does not mean fulfilled, and fulfilled does not mean correct or high quality. A market listing is not verification evidence, and a signed receipt is not permanent trust.

Installation

In SourceWeft

  1. Open Atinamos Evidence in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/uk.co.atinamos%2Fevidence/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "atinamos-evidence": {
      "type": "http",
      "url": "https://verify.atinamos.co.uk/mcp"
    }
  }
}

README

Atinamos Agent Verification Research

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.

Current state — 7 September 2026

Read the canonical public status first:

The main technical milestone is now the first unattended generic external Assurance execution from an already-frozen plan.

Keyronne JSON Repair

text
service: POST https://keyronne.com/api/json-repairrun:     1b5bc844-368c-445a-8f84-e62be6d88baaadapter: generic-transaction-fulfilment v1.0state:   PLAN_FROZEN → COMPLETEspend:   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:

text
transaction: 0xc42bb177c41d21a56e9d3c02546fa8ebeda911cff3bc1139169a61c89f7b495cblock:       50996015

Signed evidence:

text
atinamos:receipt:10e40afd-f6b1-57bd-9c1e-0a4a1695a428

Observed evidence layers:

text
PAYMENT       SETTLEDFULFILMENT    FULFILLEDCORRECTNESS   NOT_EVALUATEDQUALITY       NOT_EVALUATED

The service returned the advertised kind of JSON deliverable. Atinamos did not infer semantic correctness or quality from that fulfilment.

Important boundary

The Keyronne run began at PLAN_FROZEN.

It proves:

text
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:

text
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.

Current development priority

text
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.

Earlier production milestone — IBANforge deterministic commissioning

On 6 September 2026, Atinamos completed the first end-to-end external deterministic commissioning of the current Assurance Runner → Verification publication path against:

text
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.

text
total observed test spend:    0.010 USDCBase settlements observed:    2successful fulfilments:       2independent controls passed:  2 / 2signed Assurance receipts:    2

That run was human-triggered commissioning. It remains an important earlier milestone and should not be retroactively described as unattended.

Earlier autonomous buyer milestone — Proof #3

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:

text
selected seller: Keyronne JSON Repairpayment:         0.001 USDC on Basex402:            v2 / exactpaid HTTP:       200proof3_complete: true

This proves the controlled Atinamos buyer experiment. It does not establish widespread external-agent adoption of Atinamos evidence.

First confirmed external commercial purchase of an Atinamos service

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.

Other published direct evidence

The repository deliberately retains successful and unsuccessful observations, including:

See EVIDENCE_INDEX.md for the current consolidated index.

Evidence semantics

Atinamos keeps these evidence layers separate:

text
PAYMENTDid payment settle?
FULFILMENTDid the advertised kind of deliverable return?
CORRECTNESSWas the returned content independently checked?
QUALITYWas subjective quality independently evaluated?

Guardrails:

text
UNKNOWN != UNSAFESETTLED != FULFILLEDFULFILLED != CORRECTCORRECT != HIGH QUALITYSIGNED RECEIPT != PERMANENT TRUSTSAMPLE COUNT != RELIABILITY PERCENTAGE

Endpoint and HTTP method are material evidence identity where applicable.

Public Evidence MCP

AI agents and developers can query selected published Atinamos evidence through the read-only Atinamos Evidence MCP:

text
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.

Public Market Search

Atinamos exposes a bounded read-only projection of machine-service discovery observations:

text
GET https://verify.atinamos.co.uk/v1/market/search?q=<query>&limit=<1-50>GET https://verify.atinamos.co.uk/v1/market/service/<service_id>

Market Search reports observed listings and provenance. A market listing is not verification evidence.

Assurance evidence reads

Current signed Assurance evidence can be read using:

text
GET https://verify.atinamos.co.uk/v1/assurance/receipts/<receipt_id>GET https://verify.atinamos.co.uk/v1/assurance/evidence?endpoint=<service-url>&method=<HTTP_METHOD>

Endpoint and HTTP method are material evidence identity.

Methodology and specifications

Historical evidence should remain valid in the format in which it was issued rather than being silently rewritten.

Repository purpose

This repository is the deliberately sanitised public technical publication layer for Atinamos Verification and Assurance research.

It may contain:

  • public evidence schemas;
  • sanitised verification receipts;
  • methodology suitable for technical scrutiny;
  • deliberately published experiment records;
  • public research notes;
  • machine-interface documentation;
  • examples and specifications.

It does not contain:

  • Atinamos operational source code;
  • private signing/wallet material;
  • private infrastructure credentials;
  • the private operational database;
  • unpublished anti-abuse techniques;
  • material that would materially assist gaming of Assurance tests.

GitHub is not where Atinamos Verification runs. It is where Atinamos publishes selected technical evidence and documentation for public scrutiny and machine consumption.

Licensing

Copyright © 2026 MotionFil-AI.

  • Research, methodology, written evidence, findings, specifications and datasets are licensed under CC BY 4.0 unless a file states otherwise.
  • Schemas, machine-readable receipts/examples and future source code are licensed under the MIT License unless a file states otherwise.

See LICENSE.md for details.

Source: README.md at commit 8c620d9

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Atinamos integrations

Atinamos Agent Shop

uk.co.atinamosOfficial publisher

A remote catalogue of machine services that lets an assistant browse, inspect and prepare paid x402 invocations, plus search an observed market registry.

Streamable HTTPWeb executable
Web Search & Scraping5 toolsOct 24, 2026