DexSQL
SQL for Android APK and DEX files: classes, methods, strings, references and smali.
Market jargon in plain language: terms, official figures, crypto prices and charts, headlines.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 20/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 ATLAS Explain。按照 https://mcp.popnx.com/i/mishhf93-atlas-explain.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(atlas-explain-mcp.atlas-explain.workers.dev) · ✓ 命令已检查 2026年11月16日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
ATLAS Explainhttps://atlas-explain-mcp.atlas-explain.workers.dev/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsATLAS Explain
用 ATLAS Explain 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 ATLAS Explain,或回答中出现 ATLAS Explain 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
ATLAS Explainhttps://atlas-explain-mcp.atlas-explain.workers.dev/mcp开启新聊天,输入前先从插件列表中选择 ATLAS Explain
用 ATLAS Explain 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 ATLAS Explain,或回答中出现 ATLAS Explain 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user atlas-explain https://atlas-explain-mcp.atlas-explain.workers.dev/mcp应能看到 ATLAS Explain 在列表中并显示已连接
用 ATLAS Explain 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 ATLAS Explain,或回答中出现 ATLAS Explain 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 ATLAS Explain 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 ATLAS Explain,或回答中出现 ATLAS Explain 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 ATLAS Explain 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 ATLAS Explain,或回答中出现 ATLAS Explain 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://atlas-explain-mcp.atlas-explain.workers.dev/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user atlas-explain https://atlas-explain-mcp.atlas-explain.workers.dev/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"atlas-explain": {
"url": "https://atlas-explain-mcp.atlas-explain.workers.dev/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"atlas-explain": {
"type": "http",
"url": "https://atlas-explain-mcp.atlas-explain.workers.dev/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
工具名称和描述与服务器在 2026年11月16日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
explain_termLook up a trading or market term (for example 'stop-limit order', 'bid-ask spread', 'yield curve') in ATLAS Explain's plain-language glossary. Education only.
browse_glossaryList ATLAS Explain's learning path (topics in order, each with its terms) or every glossary term in one group. Use it to suggest what to learn next, or to find the right term to explain.
asset_detailsEverything ATLAS Explain shows about one asset: what it is, where and when it trades, its latest official figure or price (with source and time), or why no price is shown. Covers crypto, US stocks and ETFs, currencies, interest rates, energy, indices, futures and options.
official_figuresOfficial figures ATLAS Explain publishes from free government and regulator sources: US Treasury yields, ECB and Bank of Canada rates, EIA energy prices, and the latest SEC-filed figures (revenue, net income and more) for large US companies and ETFs. Each has its source and date.
crypto_pricesRecent prices for the ten major coins ATLAS Explain follows (Bitcoin, Ethereum, Solana, XRP, Cardano, Dogecoin, Litecoin, Polkadot, Chainlink, Avalanche), biggest moves first. Collected hourly by ATLAS Explain's data job from Kraken's public market data (CoinGecko as backup) and
price_historyHow a coin's price moved over the last 24 hours, 7 days or 30 days: start, end, change, high and low with their times, from the hourly closes on ATLAS Explain's own data site (refreshed hourly). Describes the past only; never a forecast.
todays_headlinesRecent market headlines ATLAS Explain collected from the GDELT Project, each with its publisher, link and time. Headlines older than 36 hours are never returned. Optional filter by company or coin.
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 MISHHF93 验证,该账户拥有此仓库
代码最后更新于前天
使用 Apache-2.0
在 71 毫秒内响应(HTTP 200)
无需登录
已读取 7 个工具描述,未发现针对 AI 的隐藏指令
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/mishhf93-atlas-explain)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于前天,最新版本(1.16.0)于今天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:DexSQL, PayRam, DexPaprika, Alchemy MCP Server, X402 List MCP
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
SQL for Android APK and DEX files: classes, methods, strings, references and smali.
Install, configure, operate and integrate self-hosted PayRam crypto payment gateways.
DEX and on-chain data: liquidity pools, token prices, swaps, and trading volume.
Blockchain data across 100+ chains: token prices, NFTs, transfers, simulation, traces, Solana DAS
Find and vet x402 payment APIs before your agent pays one: uptime, price, on-chain volume.
| 本项 ATLAS Explain | DexSQL | PayRam | DexPaprika | Alchemy MCP Server | X402 List MCP | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 2/3 | 3/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | Apache-2.0 | NOASSERTION | – | MIT | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Educational explanations of a market move. After a sharp drop, ATLAS Explain turns a structured move card into a balanced account of why a buyer might see opportunity and why a seller might see further risk. It is free to use, Apache-2.0, and it does not tell anyone to trade.
The model runs through Firebase AI Logic hybrid inference. Chrome uses Gemini Nano on the device when that model is available, and Gemini in the cloud when it is not. The screen names the path that actually ran.
ATLAS Explain comes two ways, from one codebase: an MCP connector that AI assistants (Claude, ChatGPT, Cursor, VS Code) add with one address, and a web app at https://atlas-explain.web.app/app. There is no Chrome extension (removed on 15 Nov 2026).
This is an entry for Google's #BuildHybridAI 2026 hackathon.
Educational explanations only. Not financial advice, not a recommendation, and not an offer to buy or sell any security.
A sharp move can support two careful readings at once. Someone might buy a dip because the drop looks larger than the new information. Someone else might sell because the same information can keep pressuring the price. ATLAS Explain makes both readings explicit from a move card the user supplies: symbol, percent move, volume versus normal, the market and sector that day, peers, volatility, upcoming events, and optional headlines.
Headline text is classified into a fixed taxonomy: AI capex, China / export rules, scandal / governance, earnings / guidance, rates / Fed, macro shock, or other. The answer is always three buyer reasons, three seller reasons, and what would change the picture.
Private notes and a watchlist can ride along only when the on-device model runs. They are omitted from cloud prompts and they are never written to Firestore.
The web client uses the Firebase JavaScript SDK (firebase@13.3.0) and the hybrid API documented here:
InferenceMode referenceChecked against @firebase/ai 3.1.0 typings shipped with that SDK. The calls are:
| Step | API | Where it runs |
|---|---|---|
| Gemini Developer API backend | getAI(app, { backend: new GoogleAIBackend() }) | src/platform/web/explainer.ts line 45 |
| Mode | InferenceMode.PREFER_ON_DEVICE, ONLY_ON_DEVICE, PREFER_IN_CLOUD, or ONLY_IN_CLOUD | src/platform/web/explainer.ts lines 37–41 |
| Model | getGenerativeModel(ai, { mode, inCloudParams, onDeviceParams }) | src/platform/web/explainer.ts lines 95–125 |
| On-device init, after the Explain click | model.initializeDeviceModel(onDownloadProgress) | src/platform/web/explainer.ts lines 127–132 |
| Inference | model.generateContent(prompt) | src/platform/web/explainer.ts line 144 |
| Which path ran | result.response.inferenceSource (on_device or in_cloud) | src/platform/web/explainer.ts lines 148 and 159–167 |
inCloudParams.generationConfig sets responseMimeType: "application/json" and a responseSchema built with Schema.object / Schema.enumString. The same schema is passed to the on-device model as onDeviceParams.promptOptions.responseConstraint, which is what the hybrid structured-output guide requires so both paths return the same shape.
The cloud model id defaults to gemini-3.5-flash-lite (the SDK 13 default) and can be changed with Remote Config. Temperature is not sent: the SDK marks it unsupported on Gemini 3.x and later.
Path selection before that call lives in src/core/inference-path.ts (selectInferencePath, line 20) and is applied in src/core/run-explanation.ts (lines 52 and 69):
inference_mode is the preference. The in-app default is prefer_on_device.ONLY_IN_CLOUD. On-device Gemini Nano's context is 9,216 tokens.ONLY_ON_DEVICE call. If the device model is unavailable and the preference was prefer_on_device, the app retries once in the cloud with those fields removed.App Check, Remote Config, and Firestore are started in src/platform/web/backend.ts:
ReCaptchaEnterpriseProvider: lines 58–61. A debug token is assigned just above that, and only in npm run dev.fetchAndActivate and getValue: lines 65–89. In-app defaults in src/core/settings.ts match remoteconfig.template.json.addDoc under users/{uid}/explanations: line 117. Anonymous Authentication supplies the uid.Without a Firebase web config and a reCAPTCHA Enterprise site key, src/main.ts lines 27–28 render a setup screen and do not initialize Firebase.
src/core has no Firebase and no DOM, so the MCP connector (src/mcp/) and a future Android shell reuse the glossary, the move card, the prompt, the taxonomy parser and the path decision. The web app (src/web/app.ts) mounts the wallet shell in src/wallet/ over a WebBackend.
flowchart TD
user[Move card, question, optional notes] --> desk[Web desk] desk --> core[src/core validation, prompt, path] core --> mode{Inference mode} mode -->|short card, prefer on-device| device[initializeDeviceModel then generateContent] mode -->|private notes| deviceOnly[ONLY_ON_DEVICE with notes] deviceOnly -->|Gemini Nano missing| cloudRetry[ONLY_IN_CLOUD without notes] mode -->|long input or cloud preference| cloud[ONLY_IN_CLOUD or PREFER_IN_CLOUD without notes] device --> source[response.inferenceSource] cloud --> source cloudRetry --> source source --> parse[Taxonomy parser] parse --> ui[On-device or cloud badge] parse --> store[Firestore users/uid/explanations] rc[Remote Config] --> core check[App Check reCAPTCHA Enterprise] --> device check --> cloud
Requirements: Node.js 22 or newer, a Firebase project on the Spark plan or above, and Chrome when you want the on-device path. npm install may print an engine warning from the firebase package, which declares a newer Node for running the SDK inside Node. This app bundles the SDK for the browser and does not run inference in Node.
npm install
npm run dev
The public web config for project atlas-explain is committed in src/platform/web/firebaseConfig.ts and is used when the VITE_ variables are unset. .env.example lists optional overrides for a different Firebase project. Copy it to .env.local only if you need those overrides. Do not commit service-account keys.
atlas-explain is on the Spark plan. AI Logic uses the Gemini Developer API with App Check enforced. Anonymous Authentication is on. Firestore is the (default) database in nam5, in production mode. App Check uses a score-based reCAPTCHA Enterprise key limited to atlas-explain.web.app and atlas-explain.firebaseapp.com. Localhost is not on that key.
npm run dev sets self.FIREBASE_APPCHECK_DEBUG_TOKEN = true before initializeAppCheck. A production build does not set it, even if VITE_APPCHECK_DEBUG_TOKEN is present.
npm run dev and open the local URL.AppCheck debug token: "...".VITE_APPCHECK_DEBUG_TOKEN in .env.local to that token. Set it to false to turn the debug provider off. Do not add localhost to the production reCAPTCHA key..env.local using the VITE_FIREBASE_* names in .env.example.VITE_RECAPTCHA_ENTERPRISE_SITE_KEY.users/{their uid}/explanations/*, and they reject documents that contain notes or watchlist.src/core/settings.ts until a template is published: inference_mode, cloud_model, prompt_template, topic_taxonomy, on_device_max_headlines, on_device_max_chars, long_document_chars, max_output_tokens. Prompt placeholders are {{TAXONOMY}}, {{QUESTION}}, {{MOVE_CARD}}, and {{PRIVATE_CONTEXT}}. Taxonomy ids are fixed in code; Remote Config can rename labels or hide an id, and other is always kept..firebaserc selects project atlas-explain. firebase.json publishes Hosting from dist/ with a single-page rewrite, Firestore rules from firestore.rules, and Remote Config from remoteconfig.template.json.
Sign in once:
npx firebase-tools login
Run the release gate, then deploy hosting, rules, and Remote Config:
npm run release:check # typecheck, lint, test, both builds, manifest, bundle budget, audit, trade-word scan
npx firebase-tools deploy --only hosting,firestore:rules,remoteconfig
Billing is shipped switched off. billing_enabled defaults to false, checkout is not shown, and the badge says "Free during beta". See docs/MONETIZATION.md before changing that.
ATLAS Explain can load a public move card from a link or from a message sent by an allowed page. It never auto-runs an explanation. The user still clicks Explain the move. Notes, watchlists, balances, and account fields are stripped on the way in and are not written into the editor.
The context envelope is version 1:
{
"v": 1, "kind": "move_card", "source": "atlas_desk", "card": { "symbol": "BTCUSDT", "asOf": "2026-11-12", "movePct": -6.2 }, "question": "Why might some traders buy this dip while others sell?", "concepts": ["shadow"] }
A bare public move card (the existing JSON shape) is also accepted. Allowed card fields are the public MoveCard keys in src/core/move-card.ts. Forbidden keys include notes, watchlist, balances, positions, account identifiers, and secrets.
Hash links keep the payload out of Hosting query logs:
https://atlas-explain.web.app/app/explain#c= (links made for / still work; they are forwarded here)https://atlas-explain.web.app/app/explain#card= for a small cardhttps://atlas-explain.web.app/app/explain#concept=shadow to open a glossary entry without a cardsrc/core/context-link.ts builds and parses these hashes. Concept ids live in src/core/glossary.ts: shadow, signal15, chart_layers, live_lock, paper_only, drop_study, hybrid_inference, and move_card.
postMessage, for a same-machine ATLAS desk tab:
otherWindow.postMessage(
{ type: "atlas-explain/v1/load", payload: envelope, concept: "chart_layers" }, "https://atlas-explain.web.app", );
The app accepts that type only from https://atlas-explain.web.app, https://atlas-explain.firebaseapp.com, http://localhost:3000, and http://127.0.0.1:3000. It replies with `atlas-explain/v1/load