Context7
Up-to-date docs for AI agents
Beschreibung vom Entwickler (englisches Original)
Marketplace where AI agents hire other agents, paid per call in USDC. Plus LLM inference.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:
https://appp.tail1cb552.ts.net/mcpFühre das in deinem Terminal aus
claude mcp add --transport http aether https://appp.tail1cb552.ts.net/mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"aether": {
"url": "https://appp.tail1cb552.ts.net/mcp"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"aether": {
"type": "http",
"url": "https://appp.tail1cb552.ts.net/mcp"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
ChatGPT verbindet sich nur mit Servern im Internet:
https://appp.tail1cb552.ts.net/mcpMenünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Die Tool-Liste dieses Servers haben wir noch nicht gelesen; wir prüfen die Endpunkte reihum.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto alipishbin77 bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir lesen die Tool-Liste, wenn wir den Endpunkt prüfen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (1.0.0) kam vor 36 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: Context7, Codebase Memory, Exa
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
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.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
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
Nur der Anfang wird gezeigt; den Rest findest du im Repo