DexSQL
SQL for Android APK and DEX files: classes, methods, strings, references and smali.
Free Bitcoin catalogue for AI agents: blocks, inscriptions, trails, fee advice that scores itself
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 2/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 2/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
用 Agent Blockhall 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Agent Blockhall,或回答中出现 Agent Blockhall 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Agent Blockhall
Agent Blockhall 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Agent Blockhall 的应用
B · 加密货币与区块链 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
Claude Code 暂时无法连接 Agent Blockhall
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Agent Blockhall 的应用
Cursor 暂时无法连接 Agent Blockhall
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Agent Blockhall 的应用
VS Code 暂时无法连接 Agent Blockhall
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Agent Blockhall 的应用
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 bitmap22 验证,该账户拥有此仓库
代码最后更新于昨天
GitHub 无法识别许可证类型;请打开文件自行查看
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/bitmap22-agent-blockhall)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于昨天,最新版本(1.15.0)于4天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有: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.
| 本项 Agent Blockhall | DexSQL | PayRam | DexPaprika | Alchemy MCP Server | X402 List MCP | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 2/3 | 2/3 | 3/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | NOASSERTION | NOASSERTION | – | MIT | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Agent Blockhall's free Bitcoin catalogue, for AI agents. Always free. No keys, no accounts.
Agent Blockhall is a 3D Bitcoin block explorer world for players and agents. This tool gives an AI agent the same catalogue without opening a browser. It runs on your own computer and reads free public sites (mempool.space and its copies, ordpool.space, ordinals.com and its back-ups), gently: at most 30 asks at once, then 6 a second per site, and it rests any site that asks it to slow down and uses a back-up instead.
| Tool | What it gives |
|---|---|
about | What Agent Blockhall is, where to open it, and how agents use it in a browser |
chain | The newest block, the last blocks mined, the blocks waiting to be mined, the next halving |
feeAdvice | The big screen's advice from Agent Blockhall's common room: the usual wait, whether now is a cheap time, and the fee to make the next block (plus patient and cheap fees). It keeps score of itself: it says how often its way of working the fee out would have been right on blocks it was not tuned on |
block | A block (its number is its bitmap): hash, time, size, transactions and every inscription made in it |
blockManifest | The Block Manifest: every transaction in a block, sorted into the same kinds as the game's hall shelves (inscriptions and their file types, bitmaps, BRC-20, TAP, runes etched, minted and moved, Alkanes, Stamps, SRC-20, CAT-21, Atomicals, payments and more), with its fee, size and what it carries. Counts for every kind, then the items a page at a time, or only one kind |
inscription | An inscription by number (#1000) or ID: what it is, when and where it was made, its sat, who holds it, its parents and children |
provenanceCheck | The Provenance Check: proof of where an inscription came from. It is read out of its own transaction's bytes (file type, size, parents, delegate) and matched with ordinals.com, its content's fingerprint (SHA-256) is matched with the file shown, its block, number and sat are checked with second sites, and every move is followed back to where it was made, each step spending the one before |
collectionCheck | The Collection Check: proof of which pieces of a collection are its parent's real children. For each child ord lists: is it on two ord sites' lists, does its own transaction name the parent, and was the parent spent to make it (the parent's trail is followed back, each move worked out to its own ID). A big collection carries on over several calls. Or give ids (a collection without a parent): does each piece name a parent at all |
recursionMap | The Recursion Map: everything an inscription loads from the chain, a few levels deep. Its code is read (never run) for the inscriptions it uses (loads, named, child, delegate), then those are read the same way; each is checked on ordinals.com and a second ord site. It lists the /r/ endpoints the code asks (each asked of ordinals.com today) and addresses outside the chain, and says whether everything it names is on the chain (allOnChain) |
secondOpinion | The Second Opinion: a claim about Bitcoin, in plain words ("block 840000 has 3,050 transactions", "#1000 is a PNG", "#126750483 is a child of #126744012") or as kind, subject and value, checked against ord sites, mempool sites and the chain's own bytes. Claims about a rune too ("DOG•GO•TO•THE•MOON was etched in block 840,000"): its etching's own bytes and ordinals.com, the only free rune site; counts like its mints and supply come from ordinals.com alone, and the answer says so. The answer (true, false, mixed or unknown), and what each source says and how it knows |
children | The children of a parent inscription (a collection), a page at a time |
followBack | An inscription's trail: where it was made and each place it moved |
search | A block, bitmap, parcel (12.840000.bitmap), inscription, transaction ID or address, as the tablet in the game finds them |
watch | Watch: says when something happens on the chain, each alert checked: the next block, the next-block fee at or under a level, an inscription moving (as soon as the move is in the mempool, and again once it is in a block), an address sending or getting a transaction, or a kind of transaction in a new block. The first call gives a since token; call again with it to hear what changed, and add wait (up to 240 seconds) to keep looking until something happens |
dailyData | Daily Data, made each night by GitHub: every block of a UTC day, read the Block Manifest way, with what was in it, its fees, who mined it and its checks. No day: the list of days; a day: every block; a block: that one |
sourceHealth | Source Health: which data sites these tools read are answering, how fast, and whether they are up to date, for Bitcoin and Dogecoin. Each site is asked one small thing now, from your computer (most: the newest block's height), and GitHub's computers ask the same about once an hour and keep a week: each site's last day and week. With what it means, in words |
truthLeague | Truth League: which data sites these tools read tell the truth. Every few hours GitHub's computers prove one Bitcoin block (its hash from its header with at least 70 zero bits of proof of work, its transactions to the merkle root, its height in its first transaction) and one Dogecoin block from their own bytes, ask each site facts about them, and mark each answer right or wrong against the bytes, never against another site; 30 days are kept. Gives the league, every wrong answer with what the site said and what the bytes say, and findings. chain, site, days (7 or 30), now: true to check from this computer. Its check link works with checkAgain. |
tradeCheck | Trade Check: before buying or trading a Bitcoin inscription or a Doginal, GO, STOP or NOT SURE, with every reason in plain words. It runs provenanceCheck (its file, transaction and block from the chain's own bytes, and who holds it), checks the seller's address if given, the Second Opinion's parent check for its collection (named, or the parent it names), and for code codeRead and recursionMap; for a Doginal, dogeProvenanceCheck. GO is never advice on price or whether to buy. Give id, and if you like seller, collection and chain. |
stuckTx | The Stuck Transaction Doctor: give a transaction ID (or none, for one waiting now). Its state (stuck, waiting, not stuck, mined, not found), why it waits, the fees aimed for (next block, about an hour, about three hours, keeping score of itself) and both fixes: replace it (the new fee under Bitcoin Core's replacement rules) or a child that pays for it (for each output). Nothing is sent or signed |
codeRead | Code Read: an inscription's code (and the code it loads) read without running it. Whether it asks a wallet to connect, sign or send, loads things from outside the chain, could send data out, tracks you, hides what it does, or asks your browser for things; each finding with where it is and that piece of code (untrusted). It can't prove code is safe, only say what it found |
runeProof | Rune Proof: give a rune (its name, ID, number) or a transaction. Its etching transaction's own bytes are read with ord's own rules and proved to be that transaction, in its block at the rune ID's place; the name's rules are checked (not reserved, unlocked, committed to six blocks before); then ordinals.com is checked against it, field by field. For a transaction that tried and failed, it says why. Mints, supply now and burned come from ordinals.com alone, checked to add up |
checkAgain | Citable checks: every check gives cite, a link that carries when it was made, which sites it asked, its main facts and a fingerprint of its core (what comes from the chain itself). Give checkAgain such a link and it makes the same check again now and says whether it is the same, or what changed (each fact then and now). The same link opened in a browser does the same on the portal's page |
rareSats | The rare sats board: each kind of rare sat and the price listed for one sat |
provenanceCheck and dogeProvenanceCheck also say what is in the file (whatIsInIt), read from the file's own bytes by the Media Reader (server/media.js): a picture's resolution, colours used, colour depth, palette and frames; a sound's length, samples a second and channels; a video's resolution, length and frames a second; a 3D model's points, triangles, real size, textures and animations. Every number is read or counted from the bytes, never guessed.
Doge Cube is Agent Blockhall's Dogecoin twin. These five tools are the same tools for Dogecoin and its Doginals. They read the same files as the portal's Doge pages.
| Tool | What it gives |
|---|---|
dogeBlockManifest | Every transaction in a Dogecoin block, sorted into Doge Cube's kinds (Doginals and their file types, dogemaps, names, DRC-20, TAP, dunes etched, minted and moved, and the kinds of payment), with its fee (koinu) and size. Checked: the block's hash worked out from its own header and asked of Bitcore, its transaction list proved by the merkle root in that header, sizes and fees matched on Bitcore, and the transactions that carry something read from their own bytes |
dogeProvenanceCheck | Proof of where a Doginal came from: read from its own transactions' bytes (a Doginal can be written over many transactions, and each is followed), the file put back together and fingerprinted, matched with the explorer's copy and Doggy Market's copy, its block checked on Bitcore, and its trail of moves, each step checked on two sites |
dogeCollectionCheck | Doge Collection Check: give a Dogecoin collection (or your own list of Doginals). Doginals have no parents, so which pieces belong can't be proven on the chain: the pieces are the ones thedoginalsexplorer.com lists. Each one is checked on separate sites: a real Doginal, its first transaction in a block on Bitcore, the same file on the explorer and Doggy Market, held where the explorer says (lost ones confirmed). Up to 100 pieces a call, in the collection's order |
dogeWatch | Alerts when something happens on Dogecoin, each checked: the next block, a Doginal moving, an address getting or sending DOGE, or a kind in a new block. Same since tokens as watch. There is no fee watch for Dogecoin: its fees barely move |
dogeDailyData | Doge Daily Data, made each night by GitHub: every Dogecoin block of a UTC day, with its hash checked from its own header and on Bitcore, its transaction list proved by its header, its size, fees, who mined it (where the coinbase names a pool) and its Doginals by file type |
They read thedoginalsexplorer.com (the one Doginals list), Bitcore, Blockchair (a transaction's own bytes) and Doggy Market's copy of each file, at the pace each site says it allows.
The same checks, for people, with the same readers: blockManifest: Block Manifest, provenanceCheck: Provenance Check, collectionCheck: Collection Check, recursionMap: Recursion Map, secondOpinion: Second Opinion, sourceHealth: Source Health, truthLeague: Truth League, tradeCheck: [Trade Check](https://b