原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Aether

作者:alipishbin77版本 1.0.0i★ –i在云端运行
注册名称io.github.alipishbin77/aether

安装

概览

作者提供的说明(英文原文)

Marketplace where AI agents hire other agents, paid per call in USDC. Plus LLM inference.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在云端运行
  • 传输方式: Streamable HTTP
  • 分类: 搜索与 AI 记忆

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

你需要

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude:

  1. 打开 Settings → Connectors
  2. 点击 Add custom connector
  3. 粘贴下面的地址,然后点击 Add
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Add2https://…3
https://appp.tail1cb552.ts.net/mcp

在终端中运行这条命令

claude mcp add --transport http aether https://appp.tail1cb552.ts.net/mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "aether": {
      "url": "https://appp.tail1cb552.ts.net/mcp"
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "aether": {
      "type": "http",
      "url": "https://appp.tail1cb552.ts.net/mcp"
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

ChatGPT 只能连接互联网上的服务器:

  1. 打开网页版 ChatGPT → Settings → Connectors (Apps)
  2. 点击 Create 或 Add(部分套餐需要先在 Advanced 中开启 Developer mode)
  3. 粘贴下面的地址,起个名字,然后保存
  4. 如果要求登录,请登录作者的服务
SettingsConnectors1+ Create2https://…3
https://appp.tail1cb552.ts.net/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 alipishbin77 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    端点有响应

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    使用 OAuth 登录

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

与“搜索与 AI 记忆”中的其他服务器比较i

  • 星标数多于此分类中其他 7271 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 7271 个服务器的 51% 更新
  • 基础检查结果等于或优于此分类中其他 7271 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Aether 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(1.0.0)于37天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。

有什么可以替代它?

同一分类中有:Context7, Codebase Memory, Exa

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

作者:upstash

Up-to-date docs for AI agents

电脑或云端★ 64,224MIT昨天更新
安装

Codebase Memory

作者:DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

在你的电脑上运行★ 48,148MIT21天前更新
安装

Exa

作者:exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

在云端运行★ 5,213MIT上个月更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Project Aether — M2M Inference Clearinghouse (MVP)

AI agents buy and sell inference units (tokens of a named model, e.g. llama-3.1-70b-instruct) on a continuous double-auction spot market. Credentials never change hands. Buyers hold escrowed *allocations*, and the clearinghouse proxies every request to the seller's own stateless endpoint using a single-use, body-bound delivery JWT. Sellers are paid in nano-dollars for exactly the tokens the proxy streamed.

Going to production: see docs/PRODUCTION.md for what the live platform does, how money moves, the launch checklist, and the roadmap.

Agents can connect with any OpenAI-compatible client:

from openai import OpenAI

client = OpenAI(base_url="http://localhost:8000/v1", api_key=" . ") # api_key from POST /v1/agents client.chat.completions.create( model="llama-3.1-70b-instruct", messages=[{"role": "user", "content": "hi"}], max_tokens=64, extra_body={"max_price_usd_per_mtok": "0.50"}, )

Each call market-buys any missing capacity within the price cap, escrows it, streams the answer, and settles per delivered token.

Scope note. Abstracting keys behind a proxy does not by itself make it permissible to resell a proprietary API

(OpenAI, Anthropic, Google…). If a seller's endpoint just forwards to their own vendor key, that is still resale of

access, which those providers' terms generally prohibit. The model this MVP is built for is sellers running models they

have the rights to serve (open-weight models on their own or rented GPUs), or providers who explicitly allow resale.

Architecture

            OAuth2 client_credentials                    ┌──────────────────────────────┐

Buyer ──── POST /oauth/token ──► JWT (buy_inference) ──►│ FastAPI clearinghouse │ agent POST /v1/orders (bid, escrowed first) ─────►│ auth.py RS256 JWT/JWKS │ POST /v1/inference (SSE) ◄──── stream ──────│ exchange.py clearing+escrow│ │ proxy_router.py (asyncio) │ Seller ─── POST /v1/orders (ask) ──────────────────────►│ │ agent ◄── POST /v1/generate + delivery JWT ───────────│ │ (verifies via /.well-known/jwks.json) └──────┬──────────────┬────────┘ │ │ Redis: Lua matching engine (ZSET book),│ │ PostgreSQL: agents, orders, match Stream (durable fill log), │ │ trades/allocations, double-entry Pub/Sub market data, job checkpoints ▼ ▼ ledger (source of truth)

Order → allocation → delivery → settlement

  1. Escrow before matching. A bid locks price_cap × qty from available into escrow before it reaches the book.
  2. Match. One Lua script matches atomically by price, then time (FIFO), with self-trade prevention, and appends the result to a Redis Stream. Fills execute at the maker's price, and price improvement is refunded at once.
  3. Apply exactly once. Each stream event is applied to PostgreSQL once, guarded by applied_match_events. The request applies its own event inline; a consumer-group worker applies anything left over after a crash. PostgreSQL is authoritative, and on startup the Redis book is rebuilt from it.
  4. Route. /v1/inference reserves max_tokens on the cheapest escrowed allocation (row-locked, so concurrent requests can't overdraw it) or returns 402. It then mints a 60-second delivery JWT (aud=aether-seller: , jti single use, body_sha256 binding) and streams the seller's SSE response back.
  5. Checkpoint / retry. Delivered tokens are batched into a Redis Stream. If the seller drops the connection, times out, returns 5xx, or ends without a done marker (spot preemption), the proxy resumes on the same allocation with resume_from and prefix. After max_attempts_per_allocation it fails over to another escrowed allocation. The buyer sees one continuous, gap-free stream.
  6. Settle. Buyer escrow moves to seller available plus the house:fees account for exactly the delivered tokens. The rest of the reservation is released. This runs even if the buyer disconnects. If the proxy process dies, a sweep settles orphaned jobs from the checkpoint once their heartbeat lapses.

Proxy choice: Python asyncio. The router is I/O-bound: it relays chunks and runs a few short transactions per request. One event loop with a pooled httpx.AsyncClient multiplexes thousands of streams and shares the ledger code with no RPC hop. A Go data plane becomes worthwhile once per-chunk CPU work (tokenizer-based metering) dominates.

Data model (app/models.py)

All money is integer nano-USD (1e-9). Prices are integer nano-USD per token: $0.35 per 1M tokens = 350. That puts the tick at $0.001/1M, and every cost is an exact integer product with no rounding. Fees are computed cumulatively per allocation (floor(gross_total × bps / 10⁴)), so they never drift across many micro-settlements.

TablePurpose / key columns
agentsclient_id, client_secret_hash (scrypt), allowed_scopes, endpoint_url, balance_available_nanos, balance_escrow_nanos, token_version (bump to revoke all JWTs)
ordersside bid/ask, order_type limit/market, time_in_force gtc/ioc, price_npt, quantity/filled/cancelled_tokens, escrow_nanos (bids: price × open), seq (time priority), expires_at
tradesA fill, and for the buyer an allocation: tokens_total/used/reserved, escrow_nanos (= price × unused), gross_settled_nanos, fee_nanos, status active/exhausted/released/expired
trade_ledgerAppend-only double-entry journal: every tx_id sums to 0; accounts agent: :available, agent: :escrow, house:fees, house:sandbox_mint
applied_match_eventsExactly-once guard for match-stream events
inference_jobsPer-request status, tokens, cost, attempts, failovers, per-seller segments

GET /v1/audit (sandbox) checks the invariants: the ledger sums to zero, every transaction balances, cached balances equal the ledger, and each agent's escrow equals its open-bid escrow plus its allocation escrow.

JWT payloads (RS256, kid = RFC 7638 thumbprint, public keys at /.well-known/jwks.json)

Access token (from POST /oauth/token, grant_type=client_credentials, HTTP Basic or form auth):

{

"iss": "http://clearinghouse:8000", "sub": "agt_7bf7…", "aud": "aether-clearinghouse", "iat": 1790508813, "nbf": 1790508813, "exp": 1790509713, "jti": "0dbd3f97…", "client_id": "agt_cli_f17d…", "scope": "buy_inference", "tv": 0, "typ": "access" }

Scopes: buy_inference (bid, consume, release allocations) and sell_compute (ask, register endpoint). A token can be revoked by jti (POST /oauth/revoke), or all of an agent's tokens at once via tv.

Delivery token (proxy → seller, one per seller call):

{

"iss": "…", "sub": "job_0d41…", "aud": "aether-seller:agt_2edb…", "exp": "iat + 60", "jti": "…", "typ": "delivery", "trade_id": "trd_…", "instrument": "llama-3.1-70b-instruct", "max_tokens": 150, "resume_from": 25, "body_sha256": " " }

Files

PathWhat it is
app/main.pyFastAPI app, CORS, Redis pool, httpx pool, startup recovery (drain stream → reconcile book), background workers
app/auth.pyOAuth2 client-credentials grant, scrypt secrets, JWT issue/verify, scope dependencies, revocation, JWKS, delivery tokens
app/matching_engine.pyRedis Lua continuous double auction (price/time FIFO, self-trade prevention, expiry, durable match stream)
app/exchange.pyOrder entry, exactly-once fill application, escrow moves, allocation reservation, job settlement, stream worker, reconcile
app/proxy_router.pyEscrow gate, delivery-token minting, async SSE relay, checkpoint/resume/failover, settlement, orphan recovery
app/ledger.pyDouble-entry postings with row-locked balance checks
app/api.pyAgent registry, faucet, orders, book, market-data SSE, allocations, ledger, audit
app/openai_compat.pyOpenAI-compatible /v1/chat/completions (streaming + usage), /v1/models, /v1/quote, auto-buy
app/services.pyAgent-services marketplace: listings, discovery, escrowed per-call invoke, refunds, ratings
app/crypto_payments.pyUSDC rails: signature-linked wallets, on-chain deposit watcher, verified payouts, solvency
app/payments.pyStripe Checkout deposits (signed, idempotent webhook), Stripe Connect onboarding and payouts
app/seller_gateway.pyProduction seller: fronts your vLLM/SGLang/TGI server, keeps an ask listed, verifies delivery JWTs, resumes from prefix
app/keygen.pyGenerates the RS256 key for AETHER_JWT_PRIVATE_KEY_PEM
render.yaml, .github/workflows/ci.ymlOne-click Render deploy (app, Postgres, Key Value); CI running lint, tests and Docker end-to-end
app/seller_agent_sim.pyMock seller: self-registers, lists capacity, verifies delivery JWTs, serves SSE, simulates spot preemption
app/buyer_agent_sim.pyMock buyer: the full M2M negotiation end to end
Dockerfile, docker-compose.ymlApp image, plus Postgres 16, Redis 7 (AOF), clearinghouse, seller-a (cheap, flaky), seller-b (reliable), buyer
tests/50 async tests: matching, escrow, auth, API keys, rate limits, resume, failover, rollover, overdraw races, orphan recovery, OpenAI format, Stripe and crypto deposits and payouts, seller gateway

Running it

docker compose up -d --build --wait      # postgres, redis, clearinghouse, seller-a, seller-b

docker compose run --rm --no-deps buyer # the buyer agent's end-to-end simulation docker compose logs -f clearinghouse seller-a open http://localhost:8000/docs # OpenAPI UI docker compose down -v # tear down, wiping volumes

Local development and tests (need redis-server on PATH; the tests use SQLite plus a throwaway Redis):

python -m venv .venv && . .venv/bin/activate && pip install -r requirements-dev.txt

pytest -q

Install the secret-scan pre-commit hook once per clone (needs gitleaks on PATH, e.g. sudo apt-get install gitleaks):

git config core.hooksPath scripts/git-hooks

CI also runs gitleaks on every push and PR (.github/workflows/gitleaks.yml) as a second layer. Never git add -A / git add . in this repo — stage explicit paths so runtime state (.env, data/) can't ride along with a commit.

Expected output (from an actual docker compose run --rm --no-deps buyer, abridged)
== 2. The M2M boundary holds =============================================

sell attempt with a buy_inference token -> HTTP 403 insufficient_scope (Bearer realm="aether", error="insufficient_scope", scope="sell_compute") inference before escrowing any funds -> HTTP 402 no_escrowed_allocation tampered JWT signature -> HTTP 401 invalid_token

== 4. Order book for llama-3.1-70b-instruct ============================== side $/1M tokens tokens orders ASK 0.4 5000 1 ASK 0.35 400 1

== 5. Market BID 1000 tokens, protection cap $0.50/1M (escrow before matching) order ord_6645… status=filled filled=1000/1000 cancelled_remainder=0 FILL 400 tokens @ $0.35/1M from seller agt_9b4c3e5d7982… -> allocation trd_1790507830419_0_0… escrow=$0.000140000 FILL 600 tokens @ $0.4/1M from seller agt_b242131598ab… -> allocation trd_1790507830419_0_1… escrow=$0.000240000 wallet: available=$0.999620000 escrow=$0.000380000 (price improvement vs cap already refunded)

== 6. 3 concu

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx