Context7
Up-to-date docs for AI agents
作者による説明(英語の原文)
Marketplace where AI agents hire other agents, paid per call in USDC. Plus LLM inference.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
ウェブ、デスクトップ、モバイルのClaudeで使えます:
https://appp.tail1cb552.ts.net/mcpターミナルでこれを実行します
claude mcp add --transport http aether https://appp.tail1cb552.ts.net/mcpプロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"aether": {
"url": "https://appp.tail1cb552.ts.net/mcp"
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"aether": {
"type": "http",
"url": "https://appp.tail1cb552.ts.net/mcp"
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
ChatGPTがつなげるのは、インターネット上のサーバーだけです:
https://appp.tail1cb552.ts.net/mcpメニューの名前は、プランや時期によって少し違うことがあります。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
このサーバーのツール一覧はまだ読み取っていません。エンドポイントは順番にチェックしています。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント alipishbin77 で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
まだチェックしていません。エンドポイントは順番にチェックしています
まだチェックしていません。エンドポイントは順番にチェックしています
まだチェックしていません。エンドポイントをチェックするときにツール一覧を読み取ります
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。
GitHubリポジトリの最終更新は–、最新バージョン(1.0.0)がレジストリに届いたのは37 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ(開発者モードのChatGPTなど)でも使えます。
同じカテゴリには:Context7, Codebase Memory, Exa
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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.
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
price_cap × qty from available into escrow before it reaches the book.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./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.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.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.
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.
| Table | Purpose / key columns |
|---|---|
agents | client_id, client_secret_hash (scrypt), allowed_scopes, endpoint_url, balance_available_nanos, balance_escrow_nanos, token_version (bump to revoke all JWTs) |
orders | side 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 |
trades | A 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_ledger | Append-only double-entry journal: every tx_id sums to 0; accounts agent: :available, agent: :escrow, house:fees, house:sandbox_mint |
applied_match_events | Exactly-once guard for match-stream events |
inference_jobs | Per-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.
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": " " }
| Path | What it is |
|---|---|
app/main.py | FastAPI app, CORS, Redis pool, httpx pool, startup recovery (drain stream → reconcile book), background workers |
app/auth.py | OAuth2 client-credentials grant, scrypt secrets, JWT issue/verify, scope dependencies, revocation, JWKS, delivery tokens |
app/matching_engine.py | Redis Lua continuous double auction (price/time FIFO, self-trade prevention, expiry, durable match stream) |
app/exchange.py | Order entry, exactly-once fill application, escrow moves, allocation reservation, job settlement, stream worker, reconcile |
app/proxy_router.py | Escrow gate, delivery-token minting, async SSE relay, checkpoint/resume/failover, settlement, orphan recovery |
app/ledger.py | Double-entry postings with row-locked balance checks |
app/api.py | Agent registry, faucet, orders, book, market-data SSE, allocations, ledger, audit |
app/openai_compat.py | OpenAI-compatible /v1/chat/completions (streaming + usage), /v1/models, /v1/quote, auto-buy |
app/services.py | Agent-services marketplace: listings, discovery, escrowed per-call invoke, refunds, ratings |
app/crypto_payments.py | USDC rails: signature-linked wallets, on-chain deposit watcher, verified payouts, solvency |
app/payments.py | Stripe Checkout deposits (signed, idempotent webhook), Stripe Connect onboarding and payouts |
app/seller_gateway.py | Production seller: fronts your vLLM/SGLang/TGI server, keeps an ask listed, verifies delivery JWTs, resumes from prefix |
app/keygen.py | Generates the RS256 key for AETHER_JWT_PRIVATE_KEY_PEM |
render.yaml, .github/workflows/ci.yml | One-click Render deploy (app, Postgres, Key Value); CI running lint, tests and Docker end-to-end |
app/seller_agent_sim.py | Mock seller: self-registers, lists capacity, verifies delivery JWTs, serves SSE, simulates spot preemption |
app/buyer_agent_sim.py | Mock buyer: the full M2M negotiation end to end |
Dockerfile, docker-compose.yml | App 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 |
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.
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
冒頭だけを表示しています。続きはリポジトリで読めます