Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ESQ Builder

PYPI · ESQ-BUILDER-MCP

ESQ 1.0 题库包工具链(墨题刷题机):build(auto_fix) → validate(双轨校验) → upload/publish + kajweb 词表解析与热点词统计

Available components

−15 this week 73 Trust /100

Last scanned (12 hours ago)

Scores higher than 66% of PyPI servers

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency74
  • Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
  • Cryptographically verified build provenance (signed, bound to mo9652962-ai/esq-builder-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 52 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 925 tokens (~185/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "esq_upload_and_publish" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 20 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −16
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → 0.97 functional
  • 13 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 11 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed pypi/esq-builder-mcp@0.1.4

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo mo9652962-ai/esq-builder-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/mo9652962-ai/esq-builder-mcp/.github/workflows/publish.yml@refs/tags/v0.1.4
Rekor log index 3013545845
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:b88413e8691c4e9f331d159ef9b98f01046e62140a41cd9229b57882973eea61

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 22 packages
Packages resolved 22
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~789 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
esq_build_package ~354

校验并构建 ESQ 1.0 题库包 ZIP。

NameTypeReqDescription
answersobjectyes{paperKey: {questionKey: {correctOption:"B", score: 2}}} —— 每空必填, correctOption 必须存在于该题选项
auto_fixboolean–true 时先自动修复机械性坑再构建——含中文的 externalKey 重建为 cn.xxx.y2021.u1 风格(answers 键同步改名)、单花括号 {blank:N} 转双花括号、 缺失 sequence 补默认值。修复明细在返回值 fixes 数组; 判断性问题(空位数≠题数、 答案不在选项中)仍会报错。默认 false(拒绝 + 可行动错误)。
manifestobjectyes{packageId, contentVersion, title, subject, publisher, license:{notice}, source:{description}}
output_pathstringyes输出 ZIP 绝对路径
papersarrayyes[{paperKey, year, units:[{unitKey, type(cloze|reading|part_b), title, sequence, passage?, candidates?, questions:[...]}]}] - cloze: passage.blocks[].text 用 {{blank:N}} 双花括号标记空位(不是单花括号!); 词库题用 unit.ca…

Structured output declared, but exposes no named fields.

No examples provided.

esq_hot_words ~132

真题 passage 文本 → 热点词频统计(去停用词, [a-zA-Z][a-zA-Z'-]{3,})。

NameTypeReqDescription
extra_stopwords––额外停用词
since_yearinteger–只统计该年份之后的真题(默认 2023, 即"近两年热点")
textsarrayyes[{year: 2024, text: "passage 正文"}, ...](或纯字符串列表)
top_ninteger–取前 N 个(默认 300)

Structured output declared, but exposes no named fields.

No examples provided.

esq_parse_wordlist ~94

解析 kajweb/dict 高频词表 JSONL(wordRank=真题词频排序)。

NameTypeReqDescription
jsonl_pathstringyeskajweb book/*.zip 解压后的 JSONL 文件路径
level––标注级别名(如 "四级·高频")
top_n––只取前 N 个(如四级核心词取 1162)

Structured output declared, but exposes no named fields.

No examples provided.

esq_upload_and_publish ~114

上传 ESQ 包到刷题机后端并(可选)发布。上传前先 esq_validate_package。

NameTypeReqDescription
base_urlstring–后端地址(默认 http://127.0.0.1:8765, 需先启动后端)
profile_id––题库 profile(不传则用后端当前激活级别)
publishboolean–是否发布(默认 true)
zip_pathstringyesESQ 包路径

Structured output declared, but exposes no named fields.

No examples provided.

esq_validate_package ~95

校验 ESQ 包(默认内置校验器, 与刷题机官方 esq.py 同规则)。

NameTypeReqDescription
validator_path––可选, 指定后改用官方校验器 CLI(backend/tools/validate_question_bank.py) subprocess 对账——默认内置实现已与其保持一致并由一致性测试守护
zip_pathstringyesESQ 包路径

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the ESQ Builder MCP server?

ESQ Builder runs locally as a PyPI package, launched with uvx esq-builder-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · esq-builder-mcp

# add to Claude Code
claude mcp add mo9652962-ai-esq-builder-mcp -- uvx esq-builder-mcp
Common questions

What is the ESQ Builder MCP server?

ESQ Builder is an MCP server listed in the public MCP registry as io.github.mo9652962-ai/esq-builder-mcp. ESQ 1.0 题库包工具链(墨题刷题机):build(auto_fix) → validate(双轨校验) → upload/publish + kajweb 词表解析与热点词统计. This page covers its PyPI package (esq-builder-mcp).

Is the ESQ Builder MCP server safe to use?

ESQ Builder scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ESQ Builder MCP server expose?

ESQ Builder exposes 5 tools: esq_build_package, esq_validate_package, esq_upload_and_publish, esq_parse_wordlist, esq_hot_words. Their descriptions and schemas cost roughly 789 tokens of context every time the server is loaded.

Is the ESQ Builder MCP server still maintained?

ESQ Builder is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the ESQ Builder MCP server under?

ESQ Builder declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the ESQ Builder MCP server?

VerifyMCP ran 15 checks on ESQ Builder, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about ESQ Builder: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.