原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

Provenote MCP

注册名称io.github.xiaojiou176-open/provenote-mcp

安装方法

能做什么

First-party Provenote MCP server for drafts, research threads, auditable runs, and knowledge search.

作者提供的原文

  • 连接方式 –
  • 账号或密钥 无需密钥
  • 分类 搜索与 AI 记忆

可搭配使用

教 AI 做这类工作的 Skill,可与本项一起使用

timesfm

TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.

作者:google-research★ 35,6381 个 skill

Skill · 操作手册

Shadowbroker

Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…

作者:BigBodyCobain★ 11,6051 个 skill

Skill · 操作手册

google-maps-scraper

scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place

作者:gosom★ 8,2361 个 skill

Skill · 操作手册

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度4/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度7/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分11/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

Claude 暂时无法连接 Provenote MCP

开发者尚未在 MCP 注册表中填写安装方式

ChatGPT 暂时无法连接 Provenote MCP

开发者尚未在 MCP 注册表中填写安装方式

你可以改用这些方式

B · 搜索与 AI 记忆 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 Provenote MCP

开发者尚未在 MCP 注册表中填写安装方式

Cursor 暂时无法连接 Provenote MCP

开发者尚未在 MCP 注册表中填写安装方式

VS Code 暂时无法连接 Provenote MCP

开发者尚未在 MCP 注册表中填写安装方式

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Provenote MCP 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
连接方式
–
最新版本i
1.8.5
发布到注册中心i
2026年4月9日
代码最后更新i
2026年8月25日
作者
xiaojiou176-open
注册状态
活跃

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 xiaojiou176-open 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于3个月前

  • ✓ 通过

    有许可证

    使用 MIT

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/xiaojiou176-open-provenote-mcp.svg)](https://mcp.popnx.com/en/servers/xiaojiou176-open-provenote-mcp)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“搜索与 AI 记忆”中的其他服务器比较i

  • 星标数多于此分类中其他 6447 个服务器的 76%
  • 发布到注册中心的时间比此分类中其他 6447 个服务器的 7% 更新
  • 基础检查结果等于或优于此分类中其他 6447 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Provenote MCP 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于3个月前,最新版本(1.8.5)于7个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。

有什么可以替代它?

同一分类中有:OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

OpenSEO

Keyword research, site audits, rank tracking and AI visibility for your AI agent.

作者:every-app广泛使用★ 2.8万6天前更新

在云端运行✓ everyapp.com

Exa

Official Exa MCP for web search, content fetching, and multi-step research.

作者:exa-labs广泛使用★ 5245今天更新

在云端运行✓ 服务方 · exa.aiPopNx 团队已实际试用

Microsoft Learn MCP

Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.

作者:MicrosoftDocs广泛使用★ 200012个月前更新

在云端运行✓ 服务方 · microsoft.comPopNx 团队已实际试用

Docs

Search and read Empryo's documentation. Read-only, no auth, no local access.

作者:proxysoul正在增长★ 16282个月前更新

在云端运行✓ empryo.com
与相似项目对比
本项
Provenote MCP
OpenSEOExaMicrosoft Learn MCPDocsCOTAL actions (cotal.ai)
运行位置需要安装在电脑上在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否是是是否否
基础检查3/35/52/44/44/44/4
许可证MITMITMITCC-BY-4.0NOASSERTIONApache-2.0
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Notebooklab

Teach agents and operators to turn messy long context into structured outcomes they can carry into notes, research threads, drafts, and inspectable results.

Quick Result Path · Long Context · Public Proof · Project Status · Docs

Second ring: MCP & Integrations · Companion Host Bundles · Distribution · FAQ · Discussions

Star Notebooklab if you want a source-heavy AI workbench that stays inspectable after the chat scrollback is gone.

This illustrated overview is a repo-authored summary of the shortest documented path. It is intentionally not presented as a live product recording.

Canonical product path:

messy long context -> structured insight -> note / research thread / draft -> inspectable outcome

That is the first door. MCP, starter bundles, distribution pages, and promotion assets are valuable second-ring surfaces, but they should not outrank the product path.

Agent-facing truth comes first: Notebooklab teaches an agent to read messy context, structure it, move it into note / research-thread / draft lanes, and only then carry that outcome workflow forward through the first-party notebooklab-mcp server. Public skills, host bundles, and registry packs are companion surfaces around that workbench, not the product root.

At A Glance

If you only want the shortest truthful filter before reading deeper, use this table first:

What you need to knowCurrent answer
Product thesisturn messy long context into structured insight and inspectable outcomes you can carry into notes, research threads, and drafts
Fastest result pathimport one source -> run Auditable Markdown -> download one inspectable result
First proofthe quick-result overview plus the public proof page
Second ring onlyMCP, host bundles, public skills, and distribution surfaces
What it must never be reduced toa hosted one-minute trial or a generic chat wrapper

Start Here In 10 Seconds

If you only want the fastest honest map, use this:

QuestionOpen this firstWhy
"Can this help with messy long context?"Long ContextThis is the product center, not a side use case.
"Can I get one real result quickly?"Quick Result PathThis is the shortest repo-documented local proof loop.
"Is this real or just copywriting?"Public ProofThis is the evidence layer.
"What is still intentionally unclaimed?"Project StatusThis is the boundary page.

Judge the workbench before you judge the side doors. MCP pages, starter bundles, distribution packs, and promotion assets matter, but they are second-layer surfaces around the main product path.

Why Notebooklab Exists

Most AI note tools make it easy to generate words and hard to verify where those words came from.

That gets even worse when the raw material is long and messy: a huge chat log, a copied forum thread, a meeting recap, or a web page pile you do not want to flatten into one more throwaway summary.

Notebooklab is built for the opposite direction:

  • collect notes, documents, audio, and web content in one place
  • structure long context before it disappears into another chat turn
  • search and ask across that material without losing the source trail
  • turn high-value source work into auditable markdown with integrity counters
  • keep the whole workflow repository-documented and reproducible

Think of it like moving from a loose pile of research tabs to a workbench with labeled drawers, measuring tools, and a clean export lane.

If your problem starts as "I have too much messy context," the strongest current repo-backed answer is not another empty chat box. It is the path from long context to structured notes and then into reusable outcome objects.

Fastest Result Path

If you want one visible outcome before learning the whole workbench, keep the order this short:

  1. import or open one source
  2. open the source detail surface
  3. run Auditable Markdown
  4. download the inspectable result

That is the shortest repo-documented result path today. MCP, starter bundles, podcasts, and distribution surfaces stay second ring until this outcome path already makes sense.

If You Start With Messy Long Context

The strongest current first-entry path is:

Import the source

-> Run Chat Knowledgeization -> Inspect the structured insight -> Continue it as a note or notebook research thread -> Keep draft work inside the notebook lane

In plain language: first turn the pile into labeled folders, then decide whether it belongs in your notes, your active research lane, or your notebook draft workflow.

What You Can Do In One Workbench

  • Collect grounded context: bring in text, files, audio, and web sources instead of starting every session from a blank chat box.
  • Structure long context before chatting more: use built-in transformations such as Chat Knowledgeization when the material starts as long chat logs, forum threads, meeting notes, or copied web discussions.
  • Keep structured results moving: after long-context structuring, continue the result into a note, a notebook research thread, or the notebook draft lane instead of leaving the insight stranded.
  • Search and think with structure: move between notebooks, ask/search flows, transformations, and model settings without hopping across disconnected tools.
  • Create outputs with receipts: use the auditable markdown lane when you need stronger traceability than ordinary chat alone, or create notebook-level drafts plus export bundles when you need a reusable outcome object you can hand off.
  • Hand outcomes off cleanly: download draft markdown when you only need the text, or export a richer draft bundle when you need metrics, claim/section review data, PID summaries, and source manifest context together.
  • Go beyond text-only workflows: generate podcast-ready outputs and reusable transformations from the same source base.
  • Bring it into coding agents through MCP: expose notebooks, sources, drafts, research threads, and auditable runs to Claude Code, OpenAI Codex, Cursor, and other MCP-capable hosts through a first-party MCP server.
  • Run the same outcome lanes from a terminal/operator surface: use the first-party notebooklab CLI when you want notebook outcome inspection, auditable markdown, or research-thread-to-draft handoffs without treating MCP host setup as the only operator path.

If you only remember one first-entry rule, make it this:

messy long context

-> structured insight -> note / seeded research lane / notebook research thread -> draft-adjacent notebook work

That is the product center. MCP host pages come after that path, not before it.

Ecosystem Boundary

Think of these surfaces like rooms around the main workshop:

  • host guides are the side doors
  • the CLI is the tool cart
  • the main workbench is still the path from messy context to reusable outcomes
SurfaceWhat it is todayWhat it is not
Claude Code / Codex / Cursor / OpenCode pagesrepo-backed compatibility guides through the first-party MCP server, with public-ready starter bundles under examples/hosts/official partnership, bundled integration, plugin, or marketplace listing
notebooklab CLIa first-party local operator surface for outcome inspection and research_thread -> draft -> verify/download workflowsa separate distributed product line or a renamed MCP server
public skills surfacetracked public-ready skill packets now exist under public-skills/ for host-specific submission flowsa public skills catalog, live marketplace listing, or host-specific skills program endorsement
OpenClawa live ClawHub skill listing now exists at https://clawhub.ai/xiaojiou176/notebooklab-mcp-outcome-workflows, and public-ready OpenClaw-compatible bundles still live under examples/hosts/openclawofficial OpenClaw partnership, vendor endorsement, or every other marketplace surface being live
Official MCP Registrya live websiteUrl-backed notebooklab-mcp entry already points to the repo-owned MCP docs/install surfacea package-backed public artifact, official host marketplace listing, or vendor endorsement
release / listing / domain / trademark / partnershipexternal decision and publication workcompleted repo-side truth

If you want the shortest public page that keeps those boundaries honest, start with docs/project-status.md.

If you want repo-owned install artifacts instead of prose-only setup pages, start with examples/hosts/README.md. That index points to the public-ready Claude Code, Codex, Cursor, and OpenCode starter bundles plus the OpenClaw-compatible bundles and the ClawHub submission pack.

If you want the standalone host-facing skill folders used for OpenHands/extensions or ClawHub-style submissions, start with public-skills/README.md.

If you want the full claim ladder instead of inferring it from scattered host pages, use docs/distribution.md.

Second-Layer Surfaces

Once the product path is clear, use one second-ring page instead of reading every host, registry, and distribution page in order.

If you need...Open this firstWhy it stays second-ring
a host-compatible MCP pathdocs/mcp.mdcoding-agent carry-forward matters, but it is not the product center
checked-in bundle artifactsexamples/hosts/README.md and examples/hosts/packet-index.jsonbundle installs are packaging truth, not the first doorway
public claim ladder and listing boundarydocs/distribution.mdit is a truth ledger, not the main product story
what is still intentionally unclaimeddocs/project-status.mdthis is the boundary page, not the first impression

| terminal/operator workflows | docs/runbooks/operator-cli.md | the CL

只显示了开头部分;其余内容请在仓库中阅读