프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 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의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

  • 연결 방식: 클라우드에서 실행
  • 전송 방식: 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

메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. 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월 9일 점검

  • ✓ 통과

    제작자와 저장소 일치

    레지스트리 이름이 GitHub 계정 ryanroskowski 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요

  • … 아직 점검 안 함

    계속 관리되고 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • … 아직 점검 안 함

    라이선스 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • ✓ 통과

    엔드포인트 응답

    167ms 만에 응답(HTTP 200)

  • – 해당 없음

    OAuth로 로그인

    로그인 필요 없음

  • ✓ 통과

    도구 설명에 숨겨진 지시 없음

    도구 설명 43개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

온라인 쇼핑몰 및 결제 카테고리의 다른 서버와 비교i

  • 이 카테고리의 다른 서버 2571개 중 0%보다 스타가 많아요
  • 이 카테고리의 다른 서버 2571개 중 55%보다 최근에 레지스트리에 공개됐어요
  • 기본 점검 결과가 이 카테고리의 다른 서버 2571개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

Annalist, 안전한가요?

해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.16.0)은 24일 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

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 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Stripe MCP

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

제작자: stripe널리 사용됨★ 2천13개월 전 업데이트

클라우드에서 실행✓ 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에게 묻기