MinerU
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Recovers intent from imperfect AI output: JSON, tool calls, names, paths and Markdown edits.
教 AI 做这类工作的 Skill,可与本项一起使用
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
ChatGPT 暂时无法连接 PurRAssist
开发者尚未在 MCP 注册表中填写安装方式
Claude Code 暂时无法连接 PurRAssist
开发者尚未在 MCP 注册表中填写安装方式
Cursor 暂时无法连接 PurRAssist
开发者尚未在 MCP 注册表中填写安装方式
VS Code 暂时无法连接 PurRAssist
开发者尚未在 MCP 注册表中填写安装方式
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 Blackcat-Informatics 验证,该账户拥有此仓库
代码最后更新于4天前
使用 Apache-2.0
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/blackcat-informatics-purrassist)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于4天前,最新版本(0.1.0)于37天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Rust。
同一分类中有:Puter MCP, XcodeBuildMCP, Vexa, Atlassian Rovo MCP Server, Anki MCP Server
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
MCP server for Anki flashcards: adaptive review, notes, media, and deck management via AnkiConnect.
| 本项 PurRAssist | Puter MCP | XcodeBuildMCP | Vexa | Atlassian Rovo MCP Server | Anki MCP Server | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 需要安装在电脑上 |
| 需要密钥 | 否 | 否 | 否 | 是 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 3/3 | 4/4 | 3/3 | 2/4 | 4/4 | 3/3 |
| 许可证 | Apache-2.0 | AGPL-3.0 | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Assistance for AIs that get the details almost right.
PurRAssist recovers intent from imperfect JSON, names, paths, and text. Give a decoder a schema and an effort level: it searches composed corrections, validates the complete result, and returns evidence of what changed. A schema-valid guess is still a guess. Ambiguous alternatives remain visible. Use it as a Rust crate, an MCP server, or a CLI.
Version 0.1.0. Published as rust-v0.1.0: the six crates are on crates.io, with documentation on docs.rs. Read the changelog, the implementation contract for the accepted scope, and the qualification record for executable evidence. Its known limitations are not release blockers. The release procedure records the package and registry gates.
One recovery engine, three equal ways to use it: as a Rust crate, as an MCP server, and as a command-line tool. They share the same engines and the same evidence receipts.
cargo add purrassist
use purrassist::{Outcome, RecoveryRequest, Schema};
let schema = Schema::compile(r#"{ "type": "object", "required": ["temperature"], "properties": {"temperature": {"type": "number"}}, "additionalProperties": false }"#)?;
let answer = schema.recover("[[{temperatur: '42',}]]", RecoveryRequest::default()); match answer.outcome { Outcome::Resolved(value) => assert_eq!(value.to_json(), r#"{"temperature":42}"#), Outcome::BestGuess(value) => println!("inferred: {}", value.to_json()), Outcome::Ambiguous(values) => println!("{} interpretations", values.len()), Outcome::Unresolved => println!("{}", answer.receipt.stopped), }
<!-- three-interfaces-rust:end -->
The purrassist crate is the Rust interface: it re-exports the pure engines, the syntax integration and the derives.
cargo install purrassist-cli
purrassist mcp --root /path/to/workspace
Add the server to any MCP client that launches stdio servers:
{
"mcpServers": { "purrassist": { "command": "purrassist", "args": ["mcp", "--root", "/path/to/workspace"] } } }
The server speaks newline-delimited JSON-RPC over stdio. Every tool is listed in the tool reference. Starting the server creates a .purrassist/ directory in the root, where the file tools keep their transaction journals; the call command below does the same.
purrassist decode --schema schema.json --input response.txt
purrassist call match_strings --root DIR < args.json
purrassist call TOOL --root DIR reads a JSON argument object from stdin and invokes the same operation used by MCP: for every registered tool the CLI and MCP results are identical, which the test every_registry_entry_has_a_fixture_validated_through_cli_and_mcp checks tool by tool. The convenience commands decode and match are shortcuts with their own output, not the tools' output. purrassist validate prints exactly the validate_json tool's output.
Six crates make up the release set, published in this order:
| Crate | Role |
|---|---|
purrassist-core | Shared engine: the pure recovery, matching, schema, Markdown and tool-call engines, with zero third-party runtime dependencies. |
purrassist-derive | Shared engine: zero-dependency #[derive(ToolDefinition)] and #[derive(ToolEnum)] for typed tool definitions. |
purrassist-syntax | Shared engine: isolated Tree-sitter grammar integration for source inspection and validated repairs. |
purrassist | The Rust interface: the facade that re-exports the engines and the derives. |
purrassist-host | Filesystem and helper integration behind both the CLI and the MCP server: root-scoped files, journaled replacement, the shared tool registry. |
purrassist-cli | The CLI and stdio MCP server: the purrassist executable. |
Three workspace crates are internal and not published: wasm-harness (native, WASI and browser-WASM acceptance transcripts), purrassist-helper-census (the duplicate-functionality census), and purrassist-toolgraph (validated caller-owned vocabulary, loss profiles, context masks and exact output byte bounds, with a direct consumer of the supported upstream plain FnO schema profile; plain-number support, graph loading and execution remain planned).
The pure core owns its JSON parser, exact decimal arithmetic, schema validator, Unicode normalization, edit distances, phonetic matching, semantic rules, recovery search, and receipts. It has zero third-party runtime dependencies. The isolated syntax crate uses the pinned Tree-sitter grammar family; see the dependency inventory. Each tool is described in the tool reference.
Prepared grammars also support grammar::print::canonical_governed for complete canonical call, result and declaration output with borrowed bindings. The canonical_print example prepares its grammar separately and exercises semantic and resource refusals. Cold grammar compilation, higher-level emitter preparation and full seeded/witness generation remain outside this operation; tool-graph integration remains under #36.
Current surfaces include:
patternProperties/additionalProperties/dependentSchemas fills, propertyNames-conformant key repairs) produced by a first-party witness-generation algebra rather than a schema-blind heuristic.OpenAI/MCP/Anthropic declarations (Draft 2020-12 or Draft-07 schemas), per-call outcomes with itemized repairs, conservative guards for mutating tools, and re-emission as any dialect or the OpenAI tool_calls array. Call markup of a dialect that is not built in yet, or not in the request's allow-list, is reported as a rejected attempt (unsupported_dialect), never silent content. Twenty-three dialects are built in: qwen3-coder-xml.v1, hermes.v1, openai-tool-calls.v1, llama3-json.v1, mistral-v3.v1, mistral-v11.v1, deepseek-v3.1.v1, deepseek-v3.v1, kimi-k2.v1, anthropic-tool-use.v1, harmony.v1, gemma3-tool-code.v1, glm-4.5.v1, bare-json.v1, pythonic.v1, deepseek-v3-stripped.v1, deepseek-v3.1-stripped.v1, harmony-stripped.v1, hermes-stripped.v1, kimi-k2-stripped.v1, llama3-json-stripped.v1, mistral-v11-stripped.v1, and mistral-v3-stripped.v1. The marker-suppressed variants use derived grammar recipes; callers add their own with the grammar DSL. Typed tool definitions derive from Rust structs and enums with #[derive(ToolDefinition)] and #[derive(ToolEnum)] (the zero-dependency purrassist-derive crate, re-exported by the facade; see the example below). Streaming recognition (#16) is implemented. Of provider streaming events (#17), Anthropic Messages event logs are read and reassembled by the Rust API; the OpenAI delta reading, CLI and MCP inputs, provider-log fixtures, fuzz seeds and WASM parity remain tracked. See tool-call recovery.prepare_helper and complete_helper; see helpers). No model is required, loaded, or contacted by default.A tool's schema and its typed arguments can come from one Rust struct:
use purrassist::json;
use purrassist::tool_call::{FromNode, ToolArguments};
#[derive(purrassist::ToolEnum, Debug, PartialEq)] enum Order { Asc, Desc, }
/// Search the index. #[derive(purrassist::ToolDefinition, Debug, PartialEq)] #[tool(effects = read_only)] struct Search { /// What to look for. query: String, #[param(default = 10)] limit: u32, order: Option , }
assert_eq!(Search::tool_definition().name(), "search"); let arguments = json::parse(r#"{"query": "cats", "order": "Desc"}"#)?; assert_eq!( Search::from_node(&arguments), Ok(Search { query: "cats".into(), limit: 10, order: Some(Order::Desc) }), );
<!-- derive-example:end -->
Schema::generate_witness/generate_witness_governed separately implement a witness-generation algebra (canonicalize, eliminate not by De Morgan duality, merge allOf constraints, and generate a type-directed value, recursing over $ref/$dynamicRef): its result is a validated Witness, a closed-form Unsatisfiable proof (never inferred from search exhaustion), or an honest Exhausted, and recovery invents every guessed value through this same algebra. Schema::compile_governed and with_resources_governed return typed CompilationError values separating invalid schemas from resource failures. Pass the same governor to recover_governed to share the total preparation and recovery budget. The decode_json tool does this automatically. The convenience compilation methods use the default finite budget.
purrassist_core::patch::Patch (an ordered, non-overlapping, source-digest- bound set of byte-range replacements) is the crate's single edit representation; edits::EditPlan/TextEdit are aliases for it. Beyond apply, it exposes a governed invert, compose, commute, rebase, and diff algebra; apply_edit/apply_file use rebase/diff to reconcile a stale plan against an intervening change through an explicit rebase_from input. See plan application. The Rust markdown::Document API's structural operations — insert_section, remove_section, move_section (with optional re-leveling of the moved section's own heading), rename_heading, ListItemEdit::Move, renumber_list, TableRowEdit::Move, TableColumnEdit::Move, and add_reference/relabel_reference/remove_reference/unlink_reference (which rewrite every shortcut/collapsed/full-reference use resolving to the affected definition) — are exposed through the host tool plan_markdown_structure, selected by a typed op (section_insert, `section_remove