MinerU
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Check Assura contracts with Z3. Returns Verified, Counterexample, or Unknown.
教 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)排序,由以下部分组成
| 热度 | 12/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 24/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
ChatGPT 暂时无法连接 Assura
开发者尚未在 MCP 注册表中填写安装方式
Claude Code 暂时无法连接 Assura
开发者尚未在 MCP 注册表中填写安装方式
Cursor 暂时无法连接 Assura
开发者尚未在 MCP 注册表中填写安装方式
VS Code 暂时无法连接 Assura
开发者尚未在 MCP 注册表中填写安装方式
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 assura-lang 验证,该账户拥有此仓库
代码最后更新于前天
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/assura-lang-assura)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于前天,最新版本(0.8.2)于前天进入注册中心。
支持 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.
| 本项 Assura | Puter MCP | XcodeBuildMCP | Vexa | Atlassian Rovo MCP Server | Anki MCP Server | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 需要安装在电脑上 |
| 需要密钥 | 否 | 否 | 否 | 是 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 3/3 | 4/4 | 3/3 | 2/4 | 4/4 | 3/3 |
| 许可证 | MIT | AGPL-3.0 | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Write what it should do. AI proves it does.
A contract-first language for the AI era. You write behavioral contracts. AI writes the implementation. An SMT solver proves it correct, or hands you the exact input that breaks it. Ships as Rust.
Docs · Getting started · Try in browser · What we prove · Contributing
Here is a real invariant from the zip crate's central-directory parser. The archive offset is computed as cd_offset - relative_cd_offset, an unchecked subtraction on a u64:
contract FindCdSubtractSafe {
input(cd_offset: Nat, relative_cd_offset: Nat, eocd_offset: Nat)
requires { cd_offset <= 18446744073709551615 } requires { relative_cd_offset <= 18446744073709551615 } requires { eocd_offset <= 18446744073709551615 } requires { cd_offset <= eocd_offset }
// archive_offset = cd_offset - relative_cd_offset (unchecked) ensures { cd_offset >= relative_cd_offset } }
Run it:
$ assura check demos/zip-crate-audit.assura
FindCdSubtractSafe: ensures ... COUNTEREXAMPLE | cd_offset = 0, eocd_offset = 0, relative_cd_offset = 1
That table is the single-file check. assura check on a directory prints one line per failure, with the path and a cleaned summary:
src/zip.assura: FindCdSubtractSafe::ensures ... counterexample: cd_offset = 0; eocd_offset = 0; relative_cd_offset = 1
This file has no implementation body. The check asks whether those preconditions imply the ensures. They do not. For this linear query the solver returns one input inside the preconditions that underflows: a crafted archive whose central directory claims a relative offset larger than its absolute one. A fuzzer might find this. A complete decision procedure for this fragment does not miss it. Where the encoding is incomplete, the result is Unknown, not a green check.
The human line keeps the raw digits. A value on a width bound, within 32 of one, or an exact power of two from 2^8 up also gets a note, for example 18446744073709551586 (u64::MAX - 29). --json leaves variables as the raw digits.
You get Verified, a Counterexample, or an honest Unknown.
*Regenerate: vhs assets/demo/assura-check.tape (requires VHS and assura on PATH).*
The devcontainer installs Rust and libz3-dev. The first build takes a few minutes. A warm start needs Codespaces prebuilds enabled in the repo settings. Without that, the build still runs when the container is created. After the build:
cargo run --bin assura -- check demos/zip-crate-audit.assura # counterexamples (intentional)
cargo run --bin assura -- check demos/heartbleed.assura # a clean proof
cargo install assura --locked
Needs a Rust toolchain (edition 2024 / rustc 1.88+). Z3 comes prebuilt via the z3 crate. No manual Z3 install for a normal build. See Getting started for Homebrew, the LSP, and the unpublished VS Code extension.
Prefer a binary? Use the shell installer (Linux x86_64, macOS arm64/x64):
curl --proto '=https' --tlsv1.2 -LsSf \
https://github.com/assura-lang/assura/releases/latest/download/assura-installer.sh | sh
Then:
assura init my-project
cd my-project assura check contracts/lib.assura # prove the scaffold (add --json for agents) assura build contracts/lib.assura # emit Rust
Full command reference, LSP, VS Code extension, and library embedding: [Getting started](docs/GETTING-STARTED.md) · Cheatsheet
This repository contains the MCP server. The implementation is the Rust crate crates/assura-mcp. It uses the rmcp SDK with the server and transport-io features. There is no separate assura-mcp binary. The assura command starts that server on stdio:
assura mcp
{
"mcpServers": { "assura": { "command": "assura", "args": ["mcp"] } } }
The process speaks MCP on stdin and stdout. With no host attached, the terminal looks idle.
crates/assura-mcp registers these tools:
| Tool | What it does |
|---|---|
assura_check | Parse, type-check, and verify a contract. Pass source or file. |
assura_infer | Infer skeleton contracts from Rust source. |
assura_explain | Explain an Assura error code. |
assura_type_map | Map a Rust type such as Vec to an Assura type. |
assura_ir_prompt | Render a prompt that asks for Implementation IR. |
assura_ir_verify | Check that IR against the contract with Z3 or CVC5. |
A check returns Verified, a Counterexample, or Unknown. Unknown means the solver did not decide. Stop when there is no Counterexample. Do not keep rewriting because a clause is Unknown.
The official MCP Registry name is io.github.assura-lang/assura. Agent details: For AI agents.
AI writes a lot of new code, and reviewing it is the bottleneck. AI-generated tests are especially weak here: they tend to mirror the implementation. If divide(10, 0) returns 0 because of a bug, the generated test asserts == 0. The test passes. The bug ships.
Assura replaces that trust with proof. Contracts state *what* must hold. With an implementation (IR, synthesized body, or check-rust), Z3/CVC5 checks that body against the contract. With no body, as in the zip example above, it checks whether the ensures follows from the requires. Either way you get a counterexample the AI can fix against, for the fragments the solver can model. A loop can close without a human guessing at edge cases.
Property tests and fuzzing sample the input space. A solver reasons over all of it, for the fragments it can model. Where it cannot, Assura says Unknown rather than pretending. The honest map of that boundary is What we prove.
contracts (.assura) ──► AI generates implementation
│ ▼ Assura verifies (Z3 / CVC5) │ ┌─────────────────────┴──────────────────────┐ │ │ counterexample ──► back to the AI proof holds ▲ │ │ └────────────────────┘ ▼ Rust source ──► rustc ──► binary / WASM
Three tiers, fastest first:
| Tier | Time | Checks |
|---|---|---|
| Structural | < 10ms | Types, syntax, names |
| Decidable SMT | < 200ms | Refinement types, flow analysis, effects |
| Heavy SMT | < 10s | Full invariants, temporal properties |
| Demo | Models |
|---|---|
heartbleed.assura | CVE-2014-0160, TLS heartbeat over-read |
libwebp-huffman.assura | CVE-2023-4863, CVSS 9.8 heap overflow that hit every major browser |
zip-crate-audit.assura | Offset arithmetic in a real Rust crate |
More in demos/ and one worked example per feature in examples/. Case studies: docs/CASE-STUDIES.md.
New here? [Good first issues](https://github.com/assura-lang/assura/labels/good%20first%20issue) are kept stocked and scoped. Each one names the file to open and how to verify it.
Bug reports are just as valuable as patches. If assura check gives you a wrong answer, a confusing counterexample, or an Unknown you think should verify, open an issue. Those reports are how the solver encoding gets better.
Start with CONTRIBUTING.md. Architecture and crate map: docs/INTERNALS.md.
Site: assura-lang.github.io/assura (not assura.dev, a different product)
| Getting started | Install → check → build |
| Tutorial | Your first contract |
| Cheatsheet | Types, clauses, effects, CLI on one page |
| Cookbook | Ready-to-copy contract patterns |
| What we prove | The honesty map: Verified / Unknown / Counterexample |
| Compared to other tools | Dafny, Verus, Liquid Haskell, tests |
| For AI agents | JSON output and IR acceptance. The MCP server in this repo is above. |
| Scenarios | Greenfield, retrofit, audit, CI, onboarding |
| FAQ | Z3 timeouts, counterexamples, common errors |
| Internals | Architecture, crate map, SMT encoding |
| Specification | EBNF, 50 verification features, error codes |
| Roadmap | Phased implementation plan |
| Competitive analysis | How Assura compares in the survey |
| Preferred URLs | Canonical links, including installers |
The 50 verification features, by category
| Category | Features |
|---|---|
| CORE Verification Infrastructure | Ghost code, lemmas, frame conditions, axiomatic definitions, quantifier triggers, opaque functions, prophecy variables, liveness contracts |
| MEM Memory Safety | Memory regions, fixed-width integers, allocator contracts, circular buffer contracts |
| TYPE Types and Contracts | Interface contracts, recursive structural invariants, error propagation |
| SEC Trust and Security | Taint tracking, dependent types, constant-time execution, secure erasure, cryptographic spec conformance |
| CONC Concurrency | Shared memory protocols, callback re-entrancy, determinism, lock ordering, temporal deadlines, weak memory ordering |
| NUM Numerical and Precision | Numerical precision contracts, precomputed table verification |
| PERF Performance | Unsafe escape with proof obligation, complexity bounds |
| FMT Binary Formats | Binary/bit-level format contracts, string encoding, codec dispatch, checksum, protocol grammar |
| STOR Storage | Crash recovery, page cache, MVCC, rollback, monotonic state, failure models |
| PLAT Platform | Platform abstract