Global law
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
Search US and Indian statutes, regulations, constitutions, and court rules.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 12/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 32/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Vaquill。按照 https://mcp.popnx.com/i/vaquill-ai-vaquill-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.vaquill.ai) · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 5 分钟
需要 Vaquill 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Vaquillhttps://mcp.vaquill.ai/mcp在 Request headers 下添加这个名称和值
AuthorizationBearer <在这里粘贴你的密钥>只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsVaquill
用 Vaquill 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Vaquill,或回答中出现 Vaquill 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Vaquill
Vaquill 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式
A · 使用能连接 Vaquill 的应用
B · 法律与政府数据 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code · 约 5 分钟
需要 Vaquill 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user vaquill https://mcp.vaquill.ai/mcp --header 'Authorization: Bearer your-value'按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 Vaquill 在列表中并显示已连接
用 Vaquill 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Vaquill,或回答中出现 Vaquill 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 5 分钟
需要 Vaquill 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
在 Vaquill 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Vaquill 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Vaquill,或回答中出现 Vaquill 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 5 分钟
需要 Vaquill 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
在 Vaquill 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Vaquill 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Vaquill,或回答中出现 Vaquill 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --transport http --scope user vaquill https://mcp.vaquill.ai/mcp --header 'Authorization: Bearer your-value'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"vaquill": {
"url": "https://mcp.vaquill.ai/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"vaquill": {
"type": "http",
"url": "https://mcp.vaquill.ai/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 Vaquill-AI 验证,该账户拥有此仓库
代码最后更新于5天前
使用 MIT
在 631 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
云端地址最近 4 次检查中有 4 次响应 · 最近一次 631 ms · 检查于 2026年11月18日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/vaquill-ai-vaquill-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于5天前,最新版本(0.5.0)于5天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:Global law, Open Legal Data (Germany), LibreJustice, InfraNode, Fedlex Connector
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
German court decisions (Rechtsprechung) and laws (Gesetze) with citation graph and citation checks.
Search French-language and European case law and French legal texts (codes, statutes, treaties).
Keyless open data for 84 German cities: 12 lean read-only MCP tools covering 67 data types.
Search Swiss federal legislation: laws, articles, amendments via the Fedlex SPARQL endpoint.
| 本项 Vaquill | Global law | Open Legal Data (Germany) | LibreJustice | InfraNode | Fedlex Connector | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | NOASSERTION | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MCP server for Vaquill legal research API. Covers US federal and 50-state primary law: USC, CFR, state statutes and regulations, state and US constitutions, court rules, the Federal Register, executive orders, and agency guidance. Search primary law, resolve statutory citations, browse the hierarchy, and ground answers in official sources, all from your AI tools.
Sign up at app.vaquill.ai/auth/signup to get your API key (new accounts get 1,000 free API credits, no card required). Steps for AI agents: vaquill.ai/agents.
No installation needed. Add as a remote MCP server from Customize > Connectors > Add custom connector:
Option A: Bearer token (recommended)
Open the Request headers section of the same dialog and add the credential there:
URL: https://mcp.vaquill.ai/mcp
Header name: Authorization Header value: Bearer vq_key_your_key_here
Claude sends the value exactly as you type it and adds no scheme of its own, so the value field holds Bearer vq_key_... and not Authorization: Bearer vq_key_....
Option B: API key in the URL (compatibility)
https://mcp.vaquill.ai/s/vq_key_your_key_here
Still live, and still the only form that works where a client cannot send a header at all. Prefer Option A everywhere else: a credential in a URL is recorded in server logs, proxies and browsing history, which is why Anthropic's connector guidance advises against it and the MCP specification prohibits it.
Available on Claude Pro, Max, Team, and Enterprise plans. The Request headers section is in beta and is enabled per account, it accepts a short allowlist of header names, and it holds at most four. On Team and Enterprise an owner adds the connector under Organization settings first.
Open the config file from Settings > Developer > Edit Config:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.json{
"mcpServers": { "vaquill": { "command": "uvx", "args": ["vaquill-mcp"], "env": { "VAQUILL_API_KEY": "vq_key_your_key_here" } } } }
For Indian legislation, add --jurisdiction IN. One process serves one corpus, so run two entries if you want both:
{
"mcpServers": { "vaquill": { "command": "uvx", "args": ["vaquill-mcp"], "env": { "VAQUILL_API_KEY": "vq_key_your_key_here" } }, "vaquill-india": { "command": "uvx", "args": ["vaquill-mcp", "--jurisdiction", "IN"], "env": { "VAQUILL_API_KEY": "vq_key_your_key_here" } } } }
Quit Claude completely and reopen it. It does not reload the file.
Remote (no install):
claude mcp add --transport http --scope user vaquill \
https://mcp.vaquill.ai/mcp \ --header "Authorization: Bearer vq_key_your_key_here"
Local (via uvx):
claude mcp add --scope user vaquill -e VAQUILL_API_KEY=vq_key_your_key_here \
-- uvx vaquill-mcp
--scope user registers the server for every project; the default is the current directory only. -e stores the key with the registration, so it survives Claude Code being launched from an IDE, which an export in your shell profile does not. Both --header and -e are variadic, so they have to come after the server name.
Edit ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one.
Remote:
{
"mcpServers": { "vaquill": { "url": "https://mcp.vaquill.ai/mcp", "headers": { "Authorization": "Bearer vq_key_your_key_here" } } } }
Local (via uvx):
{
"mcpServers": { "vaquill": { "command": "uvx", "args": ["vaquill-mcp"], "env": { "VAQUILL_API_KEY": "vq_key_your_key_here" } } } }
Add to .vscode/mcp.json. For every project instead of one, run the MCP: Open User Configuration command and use the same shape there.
Remote:
{
"inputs": [ { "type": "promptString", "id": "vaquill-authorization", "description": "Authorization header value", "password": true } ], "servers": { "vaquill": { "type": "http", "url": "https://mcp.vaquill.ai/mcp", "headers": { "Authorization": "${input:vaquill-authorization}" } } } }
The credential goes in a prompt rather than in the file, so the file is safe to commit. VS Code asks for it on first start and remembers it. Restart the server after saving, or the tools will not appear.
Local (via uvx):
{
"servers": { "vaquill": { "type": "stdio", "command": "uvx", "args": ["vaquill-mcp"], "env": { "VAQUILL_API_KEY": "vq_key_your_key_here" } } } }
Add to ~/.codeium/windsurf/mcp_config.json.
Remote:
{
"mcpServers": { "vaquill": { "serverUrl": "https://mcp.vaquill.ai/mcp", "headers": { "Authorization": "Bearer vq_key_your_key_here" } } } }
Windsurf uses serverUrl for a remote server, not url, and interpolates ${env:VAR} if you would rather read the credential from the environment.
Local (via uvx):
{
"mcpServers": { "vaquill": { "command": "uvx", "args": ["vaquill-mcp"], "env": { "VAQUILL_API_KEY": "vq_key_your_key_here" } } } }
Tools are generated from the live Vaquill API's OpenAPI spec at startup, so the set always matches the current API. For the authoritative, up-to-date list and per-call credit costs, run the free get_pricing tool or inspect your MCP client's tool list.
The US server publishes 37 tools and the India server 22, counting search and fetch. Every one is read-only. Law change alerts (boards and watches) are deliberately not MCP tools: the API still serves them, so create and manage alerts in the Vaquill console or over the REST API directly.
The main groups (representative tools shown):
USC, CFR, all 50 state codes, constitutions, state court rules, the Federal Register, and agency guidance.
| Tool | Description |
|---|---|
search_us_statutes | Hybrid semantic + keyword search; filter by corpusType, state, titleNumber, chapter, year, and more. matchType: "boolean" takes a terms-and-connectors expression (AND, OR, NOT, /s, /p, /N, wildcards) and returns only sections that satisfy it, with totalMatches / totalMatchesExact and a nextOffset to page to the end. |
count_statute_sections | Exact section count for a scope, or for a Boolean expression (query + matchType: "boolean", with isExact and parsedQuery). |
get_us_statute_section | Section metadata by actId (citation, hierarchy, official-source links). |
get_us_statute_section_text | Full HTML + plain text of a section. |
get_sections_batch | Metadata for up to 50 sections in one call. |
resolve_statute_citation | Resolve a Bluebook citation (e.g. 42 U.S.C. § 1983) straight to its section. Optional state (a 2-letter code or federal) and corpusType are constraints, and a real citation they exclude comes back with citationOutsideFilters. |
list_statute_divisions | Browse the statutory hierarchy one level at a time. |
list_statutes_coverage | Self-describing coverage matrix: which corpora exist in which jurisdiction. |
| Tool | Description |
|---|---|
get_section_neighbors | The sections immediately before and after, in statutory order. |
get_section_definitions | The defined terms that govern a section, from its chapter's definitions section. |
get_section_cited_by | Which USC/CFR sections cross-reference this one (the inverse of crossReferences). |
get_section_cross_state | Provisions in other states addressing the same subject, ranked by similarity. |
get_section_changes | What our refreshes observed changing on this section over time. |
The Federal Register lineage of the CFR, and the dockets and Unified Agenda entries that share a Regulation Identifier Number (RIN). Metadata only: no comment text. Costs are appended to each tool's description at startup from the live pricing table.
| Tool | Description |
|---|---|
get_section_rulemaking | The Federal Register documents behind one CFR section, from its printed source note and eCFR amendment dates, with a quality tier per match. |
get_part_rulemaking | Every Federal Register document that references a CFR title and part, newest first, over the most recent years (default 5). |
get_rulemaking_docket | One Regulations.gov docket: agency, type, title, RIN, document counts and comment count (null means not measured). |
list_rulemaking_dockets | Dockets, most recently modified first, filtered by agencyId, docketType, rin, hasRin and a modified window. Cursor paged. |
list_docket_documents | The documents of one docket, oldest first, with comment periods and Federal Register document numbers. Cursor paged. |
get_rulemaking_rin | Everything held for one RIN: Unified Agenda entry, OIRA reviews, dockets, Federal Register documents by role, CFR parts and related RINs. |
list_rin_agenda | The Unified Agenda edition history of one RIN, newest first, with from and to edition ids (YYYYMM). |
list_rulemaking_committee_records | Judicial Conference Rules Committee records (minutes, agenda books, reports, rules packages, comments), most recent first, filtered by committee, docType, year, ruleSet, rule and docketId. Drafting history, not law; comments and suggestions have title, filename and text withheld. Cursor paged. |
get_rulemaking_committee_record | One committee record with its comment dockets, Federal Rule links and a window of page text (pageFrom, pageLimit). Same withheld-text rule. |
get_rulemaking_coverage | What the rulemaking store holds per source, with a freshness verdict (free). |
| Tool | Description |
|---|---|
get_pricing | Live API credit pricing (free, no auth). |
search | Generic one-string corpus search returning {id, title, url}. |
fetch | Generic one-string retrieval returning {id, title, text, url, metadata}. |
search and fetch exist because ChatGPT's deep research and company-knowledge connectors match a corpus server by those exact names and their single-string signature, and refuse to work without them. They are thin wrappers over the typed tools above, which any client that can call them should prefer: the typed ones filter by jurisdiction, corpus, date and status, and these two do not. fetch is deliberately lenient about its id, accepting an act_id, a citation URL, a bare path, or a Bluebook citation such as 42 U.S.C. 1983.
This server is not only tools. An MCP server generated from an OpenAPI document publishes one tool per endpoint and nothing else; these two primitives are where the knowledge that is not in the API lives, and neither costs anything in the per-turn tool budget.
Resources (read, don't call):
| Resource | Contents |
|---|---|
vaquill://guide | How to use the corpus correctly: identifier rules, what "still good law" actually means here, what an empty change list does and does not tell you, and where the cost is. Not backed by any endpoint. |
| `vaquill://us/coverag