プロトタイプ · プレビュー版:公式レジストリのすべてのサーバーを掲載し、30分ごとに同期しています。レビューとアカウント機能は今後のステップで始まります。
PopNx MCPAIを使う人のためのMCPサーバー · やさしい言葉で解説

Annalist

作者:ryanroskowskiバージョン 0.16.0i★ –iクラウドで動く
レジストリ名io.github.ryanroskowski/annalist

インストール

概要

作者による説明(英語の原文)

Signed data for agents: agentic-commerce census, dependency digest, x402/MCP checks, Hyperliquid

PopNx MCPの3つの柱

この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。

できること

このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。

  • 接続方法: クラウドで動く
  • トランスポート: Streamable HTTP
  • カテゴリ: ネットショップ・決済

インストール

使っているAIアプリを選んで、設定をコピーしてください。

インストールの前に

必要なもの

どのアプリを使っていますか?

上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。

ウェブ、デスクトップ、モバイルのClaudeで使えます:

  1. Settings → Connectors を開く
  2. Add custom connector を押す
  3. 下のアドレスを貼り付けて Add を押す
  4. サインインを求められたら、作者のサービスにサインインする
SettingsConnectors1+ Add2https://…3
https://api.annalist.dev/mcp

ターミナルでこれを実行します

claude mcp add --transport http annalist https://api.annalist.dev/mcp

Cursorで開く

または、設定を自分でコピーする

プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます

{
  "mcpServers": {
    "annalist": {
      "url": "https://api.annalist.dev/mcp"
    }
  }
}

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

VS Codeで開く

または、設定を自分でコピーする

プロジェクトの .vscode/mcp.json に貼り付けます

{
  "servers": {
    "annalist": {
      "type": "http",
      "url": "https://api.annalist.dev/mcp"
    }
  }
}

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

ChatGPTがつなげるのは、インターネット上のサーバーだけです:

  1. ウェブ版のChatGPTを開き → Settings → Connectors (Apps)
  2. Create または Add を押す(プランによっては、先に Advanced で Developer mode をオンにする必要があります)
  3. 下のアドレスを貼り付け、名前を付けて保存する
  4. サインインを求められたら、作者のサービスにサインインする
SettingsConnectors1+ Create2https://…3
https://api.annalist.dev/mcp

メニューの名前は、プランや時期によって少し違うことがあります。

選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。

この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。

できること

ツールの名前と説明は、サーバーが2026年11月8日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。

  • perp_full

    One call, one payment for everything on a Hyperliquid perpetual: crowd state with base rates for what usually followed (as /v1/crowd/perp), smart-money positioning (as /v1/smart/perp) and liquidation levels with order-book depth (as /v1/liq/perp), each with its own as_of. Cheaper

  • crowd_perp

    Use before acting on a Hyperliquid perpetual to see whether it is crowded or in a hype state and what historically followed. Returns 7-day move, funding (hourly, APR, percentile vs its own 90 days and vs all perps), open interest and its 24h/7d change, premium, Wikipedia attentio

  • crowd_states

    Every Hyperliquid perp currently in a crowd state (7-day moves of +50/+100/+200%, funding in its own top or bottom 5%, Wikipedia attention spikes, new listings), ranked by 7-day move, each with base rates for what followed similar states historically. Optional ?state= filter. Sig

  • crowd_market

    Market-wide crowding on Hyperliquid: breadth of 7-day moves, how many perps are up 50%+/100%+ in a week, share of perps with funding in their own top/bottom 5%, total open interest and its 24h change, BTC and ETH funding percentiles, and Wikipedia attention to cryptocurrency. Sig

  • crowd_changes

    For bots that poll: crowd-state events (a perp entering or leaving a state) since a timestamp, newest first, up to 7 days back. Each event is signed with the mark price at the time. Not investment advice. Price: $0.005 USDC per call via x402 (Base or Solana).

  • crowd_history

    Signed historical crowd-state events for backtesting: up to 30 days per call, optionally filtered by coin and state. The archive is append-only and its daily hashes are published and Bitcoin-timestamped. Price: $0.05 USDC per call via x402 (Base or Solana).

  • smart_perp

    Use before acting on a Hyperliquid perpetual to see how its most profitable traders are positioned: how many wallets in a 200-wallet smart-money cohort are long vs short, long, short and net USD, the 24h change, concentration, leverage settings, share of open interest, and how th

  • smart_market

    Where Hyperliquid's most profitable traders are positioned across all perps: the cohort's overall net long or short, the coins it is most net long and most net short, the biggest 24-hour changes, and coins where smart money is positioned against the crowd. Cohort definition inclu

  • liq_perp

    Use before opening, sizing or holding a Hyperliquid perpetual position to see where forced selling or buying would hit: known longs liquidating within 1 to 20% below the mark and shorts above it, the biggest clusters, and coverage of open interest, set against order-book depth, s

  • liq_market

    Liquidation pressure across Hyperliquid's largest perps: for each, the known longs liquidating within 5% below the mark and shorts within 5% above it, cascade ratios against order-book depth, 2% depth, how much of open interest the known positions cover, and flags; plus the coins

  • hip3_perp

    Use before trading a stock, index, commodity or FX perpetual on Hyperliquid (builder-deployed, HIP-3; coins like xyz:NVDA, xyz:GOLD, xyz:SP500): price and 1h, 24h, 7d and 30d moves, volume, open interest and its 24h change, how close it is to its open-interest cap, funding (hourl

  • hip3_market

    Overview of every builder-deployed (HIP-3) perpetual on Hyperliquid, mostly 24/7 stock, index, commodity and FX markets: each exchange's markets, open interest and volume; the largest and most traded markets; the biggest 24h moves; funding extremes; markets near their open-intere

  • outcomes_list

    Every live Hyperliquid outcome (prediction) market: readable title, category (sports, price, ipo, policy_rate, awards), deadline, each side's price as implied probability with its 24h change, and 24h volume, most traded first. Filter with category and q (text search). On-chain da

  • outcomes_market

    One Hyperliquid outcome (prediction) market by id: readable title, structured details (teams, thresholds, deadlines, official source), each side's implied probability, 24h change, volume and outstanding value, its question, and a week of hourly prices per side. Ids come from /v1/

  • checks_service

    Use before paying an x402 service: independent checks by host or URL. Uptime and latency from repeated unpaid probes, whether the quoted price and payout wallet match the listing, real on-chain usage over 30 days with fake volume removed (self-funded payers, crawler bots, one-wal

  • checks_seller

    Checks for an x402 seller wallet on Base: the services that pay out to it and their grades, and USDC received over 30 days with payers, repeat payers and fake-volume signals (payers the seller funded, crawler bots, one-wallet dominance). Signed. Price: $0.01 USDC per call via x40

  • checks_top

    Leaderboards from our independent checks of x402 services: most real (wash-adjusted) paying customers, most reliable, and flagged services (price or wallet mismatches, outages, mostly bot traffic, self-funded volume), with the method. With category= (shopping, ai-inference, crypt

  • checks_changes

    What changed in x402 service listings, from daily snapshots of Coinbase's Bazaar: price raises and cuts, endpoints added and dropped, new and departed services, and payout-wallet changes (worth checking before paying: a hijacked listing looks the same as a rotated wallet). Market

  • mcp_server

    Use before connecting a remote MCP server: independent checks by registry name or URL. Uptime and connect time from daily probes (initialize and tools/list; no tool is ever called), sign-in mode, protocol version, tool count, and tool-definition changes in 30 days (how 'rug pull'

  • mcp_top

    Leaderboards from our independent checks of remote MCP servers in the Official MCP Registry: most reliable (up in 99%+ of probes, fastest first), servers whose tool definitions changed in the last 7 days, flagged servers (often down, new domains), and counts by sign-in mode, with

  • mcp_changes

    Tool changes across remote MCP servers in the Official MCP Registry, newest first: tools added, removed or redefined (description, input schema or annotations), from our daily fingerprints. A tool that changes after you approved it is how 'rug pull' attacks work, so check before

  • web_readiness

    One site's agent readiness from our weekly census of 65,000 top sites: UCP and ACP agent checkout (its MCP endpoint, capabilities, payment handlers), A2A and MCP cards, a real llms.txt, robots.txt rules for 15 AI agents, x402, store and platform, Shopify store facts (ships-to cou

  • web_census

    Our weekly census of 65,000 top sites: how many sites and stores publish UCP or ACP agent-checkout profiles, agent and MCP cards and llms.txt, which AI crawlers stores block, store platforms, and changes in the last 30 days. With signal=, the stores that have it (for example sign

  • deps_digest

    One call for all of an agent's dependencies: npm, PyPI, crates.io and Go packages (new publishers, install scripts, license changes), public API contracts (breaking changes), AI models (retirement dates, price changes), MCP servers (tool changes, uptime) and x402 services (wallet

  • commerce_stores

    Stores from our weekly census of 65,000 top sites, filtered by what a shopping agent needs: ships to a country, UCP agent checkout and its capabilities, payment handlers (Google Pay, Shop Pay), currency, return window. Facts from each store's own machine-readable files, never its

  • apis_changes

    Dated contract changes in widely used public APIs (Stripe, GitHub, OpenAI, Twilio, Slack, Plaid, Datadog and more), from their published OpenAPI descriptions read daily: operations, parameters and request fields added, removed or newly required, each change marked breaking or not

  • apis_api

    One watched public API's contract record: current version, operation count and keys, deprecated operations, security schemes, and every dated change in the last 90 days with what broke. From the provider's published OpenAPI description, read daily. Without name=, lists the APIs w

  • ai_retirements

    Retirement calendar for AI models across platforms: shutdown dates, 'not sooner than' floors, states and recommended replacements from the official Anthropic, OpenAI and Amazon Bedrock deprecation pages, plus Azure, Vertex, Gemini and others, recorded daily so moved dates show. T

  • ai_prices

    AI model prices per million tokens (input, output, cache, batch) with context window, for about 4,000 models across providers. With model=: its price history and the same model on other providers. Without: a list filtered by provider, mode, min_context and max_input price, sorted

  • ai_changes

    Recent changes to AI model prices and availability across providers, newest first: price cuts and raises per field (with the change), models added and removed, context-window changes and deprecation dates, for the last 1 to 90 days, optionally by provider or model name. Source: L

  • packages_check

    Supply-chain check of a popular package (the 8,000 most used on each of npm, PyPI, crates.io and Go): latest version and release activity, maintainers or owners, install scripts, provenance, deprecation, retractions, and what changed since we began tracking it daily: releases by

  • packages_watch

    Supply-chain watch across the 8,000 most-used packages on each of npm, PyPI, crates.io and Go, newest first: releases by a new publisher account, maintainer and owner changes, install scripts added, provenance dropped, source repositories moved, retractions, deprecations and yank

  • prices_service

    Price history of an x402 service by host or URL: each listed endpoint's price, first-seen date and changes, price changes in 30 days (raised, lowered, delisted), the prices it actually quoted when we called it, and where it sits against similar services by category (market median

  • prices_benchmarks

    Price benchmarks for x402 services by category (seller tags such as search, llm, weather, market-data): how many services, price percentiles (each service counted once, at its median), and 7- and 30-day trends. Add price= to see where a price sits. Without tag: every category. Si

  • hlp_vault

    Hyperliquid's own market-making vault (HLP), which takes over liquidated positions: account value, APR, PnL over a day, week, month and all time, and its net position per coin across all its sub-vaults, with the most long, most short and biggest 24h changes. Shows where the excha

  • annalist_about

    Free. What Annalist is, every tool and its price, how payment works (x402, USDC on Base), and how fresh the data is.

  • annalist_baserates

    Free. Historical base rates for every crowd state: sample size, median and spread of later returns, chance of further run-ups. Optional state filter.

  • annalist_market_sample

    Free. The crowd_market view as it was 24 hours ago, to evaluate the data before paying.

  • annalist_verify_service

    Free. Before paying an x402 service, get its signed Annalist check: grade, key facts (uptime, price and wallet match its listing, organic paying customers, test purchases) and reasons. The statement is signed; verify it with the key at /.well-known/annalist-key.json.

  • annalist_verify_mcp

    Free. Before connecting an MCP server, get its signed Annalist check: grade, uptime over 7 days, connect time, sign-in mode, tool count, whether its tools changed recently (the 'rug pull' pattern) and reasons. By registry name (io.github.user/server) or URL. Verify the signature

  • annalist_verify_store

    Free. Before an agent shops on a website, get its signed Annalist check from our weekly commerce census: is it a store, does it take agent checkout (UCP or ACP) and at which MCP endpoint, which payment handlers, how many countries it ships to, and which AI agents its robots.txt b

  • annalist_weekly_report

    Free. This week in the agent economy and the markets agents trade: x402 services listed, new and gone, price changes, typical prices by category, the services with the most real paying customers, MCP server health and tool changes, and a Hyperliquid summary. Optional date (YYYY-M

  • annalist_track_record

    Free. Every crowd-state event's later outcome, compared with its backtest base rate.

基本チェックi

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月8日にチェック

  • ✓ 合格

    作者とリポジトリが一致

    レジストリ名は、リポジトリを所有するGitHubアカウント ryanroskowski で確認済みです

  • … 未チェック

    今もメンテナンスされている

    このリポジトリはまだGitHubから読み取っていません

  • … 未チェック

    ライセンスがある

    このリポジトリはまだGitHubから読み取っていません

  • ✓ 合格

    エンドポイントが応答する

    167ミリ秒で応答(HTTP 200)

  • – 対象外

    OAuthでサインイン

    サインイン不要

  • ✓ 合格

    ツールの説明に隠れた指示がない

    43件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした

ネットショップ・決済のほかのサーバーとの比較i

  • このカテゴリのほかの2554件のうち0%よりスターが多い
  • このカテゴリのほかの2554件のうち55%より最近レジストリに公開
  • 基本チェックの結果が、このカテゴリのほかの2554件のうち100%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

よくある質問

Annalistは安全ですか?

当てはまる基本チェック3項目のうち3項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。

どんなキーやコードが必要ですか?

レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。

パソコンで動きますか、それともクラウドですか?

作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。

今もメンテナンスされていますか?

GitHubリポジトリの最終更新は–、最新バージョン(0.16.0)がレジストリに届いたのは23 日前です。

どのアプリで使えますか?

Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ(開発者モードのChatGPTなど)でも使えます。

代わりに使えるものは?

同じカテゴリには:Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i

Stripe MCP

MCP server integrating with Stripe - tools for customers, products, payments, and more.

作者:stripe成長中★ 204312 か月前更新

クラウドで動く✓ stripe.com

MCP Cn Commerce

8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending

作者:TonyWang-hub初期↓ 73/週★ 9629 日前更新

パソコンで動く

作者のREADME

READMEを開く

作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。

Annalist ledger

Annalist (annalist.dev) keeps an append-only archive of crowd-state data for AI agents. This public repository is its ledger: once a day it records a fingerprint of everything the archive wrote the day before, signed and timestamped in Bitcoin. It lets anyone check that a record existed on a given date, so the history cannot have been backfilled or quietly edited later.

What is in it

  • ledger/YYYY/MM/YYYY-MM-DD.json: one entry per UTC day.
  • entry.manifests: every run manifest written that day, each with the sha256 of the manifest file.
  • entry.root: sha256 of the manifest hashes joined by newlines, in the listed order.
  • signature: Ed25519 over the canonical JSON of entry (keys sorted, no spaces, UTF-8).
  • ledger/YYYY/MM/YYYY-MM-DD.json.ots: an OpenTimestamps proof that the entry file existed at that time. Proofs start as pending and are upgraded to full Bitcoin attestations within a day or two.
  • keys/ .json: public signing keys. The current key is 187e49f200625a2f.

Each run manifest in turn lists every archive file written by that run with its sha256 and size, and is signed with the same key. Data responses served by the Annalist API carry the same kind of signature.

Verifying

  1. Check the timestamp: ots verify ledger/2026/10/2026-10-13.json.ots (needs the OpenTimestamps client and a Bitcoin block source, or use opentimestamps.org).
  2. Check the signature: verify signature against the canonical JSON of entry with the public key in keys/.
  3. Given a manifest from the archive, hash its file bytes with sha256 and find that hash in the day's entry.

Contact

Open an issue on this repository.

PopNxに聞く