Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Nothing to run from here
Getnote is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
98/100
trust score
91
downloads a day
local
runs on your machine
3k
downloads in 30d
What it does
MCP server for Dedao Brain (Get Notes) — manage notes and knowledge bases from AI assistants
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user getnote-mcp '--' npx -y @getnote/mcp
# 2 — ask your agent for something these tools do
# list_notes, get_note, get_note_original and 42 more
Getnote costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GEAll 1 server
@getnote1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Getnote as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user getnote-mcp '--' npx -y @getnote/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
45 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
获取笔记列表（每次固定返回 20 条，服务端不支持 limit 参数）。用游标翻页：首次请求不传 cursor；后续把上一次响应返回的 cursor 字段原样传入，直到 has_more 为 false。响应里的 total 是全库笔记总数，不是本页条数。
No parameter schema on file.
获取指定笔记的详细内容，包括正文、标签、附件、音频转录、网页链接等。 字段语义说明（AI Agent 重要参考）：
No parameter schema on file.
直接读取笔记原文。链接笔记返回网页原文，录音笔记返回转写原文，文字笔记返回正文；不要把 AI 摘要冒充原文。
No parameter schema on file.
直接读取录音、会议或课堂笔记的转写原文；没有转写时明确返回不可用。
No parameter schema on file.
直接列出笔记中的图片、音频和文件附件，不需要从完整详情中猜字段。
No parameter schema on file.
直接读取录音或会议笔记的结构化时间线和原文资源；没有时间线时明确返回不可用。
No parameter schema on file.
直接读取录音笔记的快捷笔记；没有快捷笔记时明确返回不可用。
No parameter schema on file.
读取从会议总结中明确的待办章节按规则解析出的条目。返回 source 和 items；空列表表示未识别到明确待办章节，不应让模型自由补写。
No parameter schema on file.
新建笔记（⚠️ 仅支持新建，不支持编辑已有笔记）。支持纯文本笔记（plain_text）、链接笔记（link）和图片笔记（img_text）。 🔗 笔记内链：Get笔记正文支持链接到其他笔记，格式为
No parameter schema on file.
查询创建笔记任务的处理进度。用于链接笔记（note_type=link）创建后，通过 save_note 返回的 task_id 轮询任务状态，直到 status 变为 success（可获取 note_id）或 failed（可获取 error_msg）。建议每 10~30 秒轮询一次，约 3 分钟内完成。需要 note.content.read scope。
No parameter schema on file.
删除笔记（移入回收站）。需要 note.content.trash scope。
No parameter schema on file.
更新已有笔记的标题、内容或标签。⚠️ 仅支持 plain_text 类型笔记，链接笔记、图片笔记等暂不支持更新。至少需要传 title、content、tags 中的一个。tags 是替换操作，会覆盖原有标签。
No parameter schema on file.
为指定笔记添加标签。
No parameter schema on file.
删除笔记的指定标签（系统标签不可删除）。
No parameter schema on file.
获取用户创建、拥有或加入的知识库列表，包含普通、书籍、客户档案和团队知识库（TEAMSPACE）。返回 topics[]、has_more、total；保存前可按 name/scope 选择 topic_id。
No parameter schema on file.
创建新的知识库。⚠️ 限制：每天最多创建 50 个知识库，北京时间自然日 00:00 重置。
No parameter schema on file.
获取指定知识库内的笔记列表（每页 20 条）。 AI Agent 提示：列表返回的
No parameter schema on file.
批量将笔记添加到知识库（每批最多 20 个）。
No parameter schema on file.
浏览知识库文件夹结构及当前目录下的笔记等资源。支持个人、书籍、客户档案和团队知识库。
No parameter schema on file.
在知识库中创建文件夹。
No parameter schema on file.
重命名或移动知识库文件夹。未提供的字段保持不变。
No parameter schema on file.
删除空的知识库文件夹。属于破坏性操作，调用前必须取得用户确认。
No parameter schema on file.
将笔记从知识库中移除。
No parameter schema on file.
获取图片上传配置，包括支持的文件类型、大小限制等。上传图片前先调用此接口了解约束。
No parameter schema on file.
获取 OSS 图片上传凭证。返回 accessid/host/policy/signature 等字段，用于 multipart/form-data POST 上传图片到阿里云 OSS。上传成功后获取 image_id，再用 save_note 创建图片笔记。⚠️ mime_type 必须与实际文件格式一致，否则 OSS 签名失败。
No parameter schema on file.
上传图片到 OSS。返回 image_url（用于创建图片笔记的 image_urls 参数）。
No parameter schema on file.
获取知识库订阅的博主列表。需要 topic.blogger.read scope。
No parameter schema on file.
把抖音博主订阅到指定知识库，后续可读取该博主内容。
No parameter schema on file.
获取知识库中某个博主发布的内容列表（摘要，不含原文）。需要 topic.blogger.read scope。
No parameter schema on file.
获取博主内容详情，包含完整原文（post_media_text）。需要 topic.blogger.read scope。
No parameter schema on file.
获取知识库中已完成且 AI 已处理的直播列表。需要 topic.live.read scope。
No parameter schema on file.
获取直播详情，包含 AI 摘要（post_summary）和完整原文转写（post_media_text）。需要 topic.live.read scope。
No parameter schema on file.
订阅一个得到 App 直播到知识库。直播结束后经 AI 处理即可通过 list_topic_lives 查看。目前仅支持得到 App 直播链接。需要 topic.live.write scope。
No parameter schema on file.
生成笔记的公开分享链接。幂等接口，多次调用返回同一个 share_url。需要 note.sharing.write scope。
No parameter schema on file.
获取当前用户订阅的知识库列表（他人公开的，非自己创建）。返回 topics[]、has_more、total。
No parameter schema on file.
查询当前 API Key 的调用配额，包括 read/write/write_note 三类的日/月剩余次数。
No parameter schema on file.
全局语义搜索：在所有笔记中进行语义召回。适用场景：「搜一下」「找找我哪些笔记提到了 XX」。返回结果按相关度从高到低排序。需要 note.recall.read scope。
No parameter schema on file.
知识库语义搜索：在指定知识库范围内进行语义召回。适用场景：「在我的 XX 知识库搜一下 XX」。返回结果按相关度从高到低排序。需要 note.topic.recall.read scope。
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Getnote or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 98 / 100
Release 1.9.1 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score98
Findings1 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationnone
Surface digest9944a8e771feb1ee61fa95df87c4a6ae3658859d2c24abfd35f88ee847f9808a
Score vectorthreat 100 → client 98
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (45 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_notes | no tags | |
| get_note | no tags | |
| get_note_original | no tags | |
| get_note_transcript | no tags | |
| get_note_attachments | no tags | |
| get_note_timeline | no tags | |
| get_note_chapters | no tags | |
| get_note_quick_note | no tags | |
| get_note_todos | no tags | |
| save_note | no tags | |
| get_note_task_progress | no tags | |
| delete_note | no tags | |
| update_note | no tags | |
| add_note_tags | no tags | |
| delete_note_tag | no tags | |
| list_topics | no tags | |
| create_topic | no tags | |
| list_topic_notes | no tags | |
| batch_add_notes_to_topic | no tags | |
| list_topic_directories | no tags | |
| create_topic_directory | no tags | |
| update_topic_directory | no tags | |
| delete_topic_directory | no tags | |
| remove_note_from_topic | no tags | |
| get_note_marks | no tags | |
| list_sprouts | no tags | |
| get_sprout | no tags | |
| get_knowledge_file_capabilities | no tags | |
| get_knowledge_file_upload_token | no tags | |
| upload_knowledge_file | no tags | |
| get_upload_config | no tags | |
| get_upload_token | no tags | |
| upload_image | no tags | |
| list_topic_bloggers | no tags | |
| follow_topic_blogger | no tags | |
| list_topic_blogger_contents | no tags | |
| get_blogger_content_detail | no tags | |
| list_topic_lives | no tags | |
| get_live_detail | no tags | |
| follow_topic_live | no tags | |
| share_note | no tags | |
| list_subscribe_topics | no tags | |
| get_quota | no tags | |
| recall | no tags | |
| recall_knowledge | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest9944a8e771feb1ee
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.9.1. Pin a release below and the command asks for exactly that one.
1.9.1
13 Oct 2026
latestNo release note was published with this version.
1.8.0
24 Sep 2026
No release note was published with this version.
1.7.2
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Getnote can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.