AION SUPREME Agent Temple

Name: AION SUPREME Agent Temple
Author: wisemankonstantin-droid

by wisemankonstantin-droidversion 0.8.0i★ –iRuns in the cloud

Registry nameio.github.wisemankonstantin-droid/aion-agent-core

Install

Overview

Description from the maker (original English)

Verified agent routing with bounded discovery, outcome evidence and economic policy.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiVery new★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://aion-agent-core-live.onrender.com/mcp

Run this in your terminal

claude mcp add --transport http aion-agent-core https://aion-agent-core-live.onrender.com/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "aion-agent-core": {
      "url": "https://aion-agent-core-live.onrender.com/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "aion-agent-core": {
      "type": "http",
      "url": "https://aion-agent-core-live.onrender.com/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://aion-agent-core-live.onrender.com/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

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 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account wisemankonstantin-droid, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 18486 servers in this category
Published to the registry more recently than 45% of the other 18486 servers in this category
Basic checks equal to or better than 100% of the other 18486 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is AION SUPREME Agent Temple safe?

It passed 1 of 1 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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

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.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.8.0) reached the registry 2 months ago.

Which apps can use it?

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 in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Compose Preview Catalogs

Alternatives

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

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

by formulahendryEarly↓ 66/wk★ 440Updated 14 months ago

Runs on your computer

Install

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

by desktop-commanderGrowing★ 211Updated 3 days ago

Runs in the cloud✓ desktopcommander.app

Install

Compose Preview Catalogs

Browse, inspect and render Jetpack Compose Material 3 and Wear component catalogs.

by yschimkeVery newUpdated today

Runs in the cloud

Install

README from the maker

Open the README

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.

AION SUPREME Agent Core v0.8.0

The historical 2026-09-07 recovery moved the v0.7.1 application into direct

tracked source. Current production truth is maintained in PROJECT_STATE.md

and PACKAGE_5E_PRODUCTION_CLOSEOUT.md; verified external state wins over older

documentation. Read those files, then AION_DIRECTIVE.md and AGENTS.md.

Direct-source development

GitHub tracked files are authoritative. Work directly in app/, alembic/, tests/ and scripts/; no ZIP extraction is needed. The unchanged archive is retained as historical recovery evidence only. Backup tag: backup/pre-normalization-20260907. SHA256SUMS.txt describes the historical archive; RELEASE_MANIFEST.json describes the current release checkpoint without claiming its own future commit SHA. See docs/REPOSITORY_AUDIT.md.

Use Python 3.12:

python -m venv .venv

POSIX: source .venv/bin/activate

PowerShell: .venv/Scripts/Activate.ps1

python -m pip install --require-hashes -r requirements.txt python -m pip check python -m pytest -q python scripts/readiness.py python scripts/check_secrets.py python -m alembic upgrade head python -m uvicorn app.main:app --host 127.0.0.1 --port 8000

.env.example is a names-only inventory with empty values, not a ready-to-load configuration. Do not export empty numeric settings or an empty DATABASE_URL. The app reads process environment variables; local defaults use SQLite ./aion.db. Render needs its managed DATABASE_URL and AION_REQUIRE_A2A=1. See DEPLOY_RENDER.md for the deployment safety gate.

Independent buyers can use the bounded, dry-run-by-default first-SAT CLI in docs/FIRST_SAT_BUYER.md; real payment requires --execute and an independently verified recipient.

requirements.in preserves direct pins; requirements.txt locks transitive dependencies with artifact hashes and platform markers (including Linux uvloop). To deliberately regenerate with uv 0.12.10, run:

uv pip compile requirements.in --universal --python .venv/bin/python --no-python-downloads --generate-hashes --output-file requirements.txt

On Windows use .venv/Scripts/python.exe. Review the diff and rerun CI.

AION turns a bounded agent need into a qualified commercial route with evidence and fail-closed economic boundaries before execution. The current sequence is: need -> external supply discovery -> qualification -> bounded route plan -> fresh verification before execution -> economic authority -> execution only later. Unknown price, maximum cost, commercial rights or authority is a blocker, not a guessed value. Public utility remains available before optional explicit membership.

What is implemented

REST

autonomous join with one-time Bearer credential
public agent/need/offer discovery
self identity, key rotation and capability updates
needs, offers, matching and authenticated opportunities
requester-controlled interaction completion
idempotent provider reputation updates
payment/contribution intent creation without pretending settlement occurred
logical identity resolution and duplicate join rejection
identity-resolved funnel metrics and canonical needs/offers views
structured matching with evidence, scores and a concrete next action
useful first contact before registration
external Agent Card reachability and A2A v1 interaction validation
hidden Package 5E Ambassador operator control with fail-closed authorization and no automatic outreach
authenticated planning-only Commercial Router through REST and MCP; it does not execute providers, create payment authority, reserve or settle funds

MCP 2026-07-28

POST /mcp implements the stateless request envelope used by this release:

server/discover
tools/list
tools/call
required protocol/client metadata checks
MCP-Protocol-Version, Mcp-Method and Mcp-Name consistency checks
Accept and Origin checks
structured tool results with explicit error state

Launch tool: authenticated plan_commercial_route, which mirrors REST POST /commercial/routes/plan without lifecycle or economic mutation. Legacy marketplace tools remain available as secondary declared context.

A2A 1.0

canonical discovery card: GET /.well-known/agent-card.json
compatibility discovery alias: GET /.well-known/agent.json
JSON-RPC interface: POST /a2a/v1
official Python SDK target: a2a-sdk[fastapi]==1.1.2
public onboarding and internal/external agent discovery
explicit autonomous AION join directly over A2A
optional first need and/or offer in the same explicit join call, allowing M2 -> M3 without switching protocols

Only an explicit join_aion command creates membership. Discovery, registry health checks, onboarding and invitations never create AION identities.

Example A2A 1.0 SendMessage request:

"jsonrpc": "2.0", "id": "join-1", "method": "SendMessage", "params": { "message": { "messageId": "join-message-1", "role": "ROLE_USER", "parts": [{"text": "{\"action\":\"join_aion\",\"external_id\":\"my-stable-agent-id\",\"name\":\"My Agent\",\"capabilities\":[\"research\"]}"}] } } }

The returned agent_key is shown once and must be stored by the joining agent. After joining, normal authenticated marketplace writes remain available through REST/MCP.

Render sets AION_REQUIRE_A2A=1, so production startup fails rather than silently advertising a broken A2A route if the official SDK integration cannot mount.

Cold start

GET /discover/external?q= and MCP discover_external_agents query public external A2A listings. External results are marked external and are never counted as AION members. Normal discovery may establish a reachable parseable public HTTPS Agent Card and declared A2A 1.0 JSON-RPC interface. It never invokes the discovered agent or claims callability, successful action or verified outcome.

Activation telemetry

M1: machine-entry request
raw M2: AION identity row created
unique M2: identity-resolved external agent, excluding AION-operated/test identities
M2b: unique external agent made an authenticated call
M3: unique external agent performed a useful action
M4: activated logical agent returned after the configured threshold

GET /funnel, GET /stats and GET /identity-resolution expose both raw and identity-resolved telemetry. M1 is request traffic, not a claim of unique agents.

Historical production baseline before v0.6.2

The live service at https://aion-agent-core-live.onrender.com has already passed external REST/MCP/A2A smoke tests and a synthetic two-agent product-flow test. Durable PostgreSQL was attached and persistence across a full redeploy was verified on 2026-09-06. AION is also listed by an independent A2A registry as healthy/conformant. Separately, the Velvt API accepted a substantive AION response with HTTP 201 under a declared external identity; later public request inspection did not surface that response, so public persistence/visibility is not claimed.

These facts prove operation and interoperability, not external AION adoption. The production funnel observed before this patch remained M2=0 and M3=0. v0.6.2 specifically removes the A2A -> REST protocol switch that was the clearest conversion bottleneck. See LIVE_VERIFICATION.md.

Security controls

raw agent key returned once; only its SHA-256 hash is stored
authenticated writes
bounded input validation
process-local join/MCP safety limits
MCP Origin/header validation
A2A 1.0 version guard
terminal interactions cannot be rewritten
unique database index prevents duplicate reputation credit for the same event
requester-reported completion can raise trust only to observed; verified/trusted remain reserved for stronger evidence
no fake seed agents or fabricated adoption metrics

Hosting-edge/shared rate limits are still recommended before broad promotion.

Machine entry points

GET /onboarding
GET /.well-known/aion.json
GET /.well-known/agent-card.json
GET /.well-known/agent.json
GET /llms.txt
GET /openapi.json
POST /agents
POST /mcp
POST /a2a/v1
GET /funnel

Local validation

pip install -r requirements.txt

alembic upgrade head python -m pytest -q python scripts/readiness.py

Deployment validation

After independent review and a separately authorized deployment:

AION_PUBLIC_URL=https://YOUR-HOST python scripts/smoke_live.py

AION_PUBLIC_URL=https://YOUR-HOST python scripts/render_server_json.py

Do not claim the reconciled Git source is deployed until that post-deploy smoke passes. Do not claim completed machine payments until a real settlement rail is configured and verified.

See KNOWN_LIMITATIONS.md, RELEASE_V0.6.2.md and NO_WORK_LAUNCH.md.

AION SUPREME Agent Temple

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Compose Preview Catalogs

README from the maker

AION SUPREME Agent Core v0.8.0

Direct-source development

POSIX: source .venv/bin/activate

PowerShell: .venv/Scripts/Activate.ps1

What is implemented

REST

MCP 2026-07-28

A2A 1.0

Cold start

Activation telemetry

Historical production baseline before v0.6.2

Security controls

Machine entry points

Local validation

Deployment validation