# Vaquill (remote · reg-mcp.vaquill.ai)

Search US and Indian statutes, regulations, constitutions, and court rules.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.vaquill.ai`: 88/100, [markdown](https://verifymcp.io/servers/vaquill-ai-vaquill-mcp/in-mcp.md), [page](https://verifymcp.io/servers/vaquill-ai-vaquill-mcp/in-mcp)
- remote · `mcp.vaquill.ai`: 40/100, [markdown](https://verifymcp.io/servers/vaquill-ai-vaquill-mcp/mcp.md), [page](https://verifymcp.io/servers/vaquill-ai-vaquill-mcp/mcp)
- remote · `reg-mcp.vaquill.ai`: 74/100 (this document), [markdown](https://verifymcp.io/servers/vaquill-ai-vaquill-mcp/reg-mcp.md), [page](https://verifymcp.io/servers/vaquill-ai-vaquill-mcp/reg-mcp)

## Channel facts

- Endpoint: `https://reg-mcp.vaquill.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 979 tokens (~195/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (80% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Vaquill MCP server?

Vaquill is a hosted endpoint at https://reg-mcp.vaquill.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http vaquill-ai-vaquill-mcp 'https://reg-mcp.vaquill.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "vaquill-ai-vaquill-mcp": {
      "url": "https://reg-mcp.vaquill.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "vaquill-ai-vaquill-mcp": {
      "type": "http",
      "url": "https://reg-mcp.vaquill.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.vaquill-ai-vaquill-mcp]
url = "https://reg-mcp.vaquill.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vaquill-ai-vaquill-mcp": {
      "type": "remote",
      "url": "https://reg-mcp.vaquill.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vaquill-ai-vaquill-mcp --url 'https://reg-mcp.vaquill.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  vaquill-ai-vaquill-mcp:
    url: "https://reg-mcp.vaquill.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "vaquill-ai-vaquill-mcp": {
      "Transport": "http",
      "Url": "https://reg-mcp.vaquill.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add vaquill-ai-vaquill-mcp -t streamable-http -u 'https://reg-mcp.vaquill.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "vaquill-ai-vaquill-mcp": {
      "type": "http",
      "url": "https://reg-mcp.vaquill.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 70)

First indexed and scored.

## MCP tools (5)

### `get_regulatory_coverage` (~108 tokens)

Regulatory Coverage

What the corpus covers and how fresh each source is. Use it before saying nothing was published. A stale or failing source means our crawl is behind, not that the publisher stopped: say so. A null time means not yet checked, never fine. Free.

Input parameters:

- `includePaused`: True to include sources we have paused.
- `publisherId`: Publisher ids, e.g. ['sebi', 'rbi']. A list of separate values, never one comma-joined string.

### `get_regulatory_document` (~104 tokens)

Regulatory Document

One regulatory document by id. Take the id from a search or change result, never guess one. include body for the extracted text (cheaper than the file), diff for what changed between the two most recent captures, versions for every capture. Check fileAvailability before asking for the file. Cost: 1 credit.

Input parameters:

- `id` (integer, required): Document id from a search or change result.
- `include`: Extra parts to return. Omit for metadata only.

### `get_regulatory_document_file` (~98 tokens)

Regulatory Document File

The archived original of one document, returned as a file, not text; for text use get_regulatory_document with include body. Check fileAvailability first. content_not_archived means we never held the bytes: do not retry. archive_unavailable means our archive failed: retry later. Neither means the regulator did not publish it. Cost: 1 credit.

Input parameters:

- `id` (integer, required): Document id from a search or change result.

### `list_regulatory_changes` (~249 tokens)

Regulatory Change Feed

What is new, changed or retracted since a time or cursor. Use it to answer what moved since I last looked. The feed follows our capture order, not publishedAt, so an older document can appear after a newer one: that is correct, do not re-sort. Pass nextCursor back unchanged while hasMore is true. Cost: 1 credit.

Input parameters:

- `changeKind`: Kinds of change to include. Omit for all.
- `cursor`: Opaque. Pass back exactly the nextCursor of the previous page. Do not parse, edit or construct one.
- `docType`: Document types as returned in results. A list of separate values.
- `limit`: Page size, 1 to 100. Omit to use the default.
- `publisherId`: Publisher ids, e.g. ['sebi', 'rbi']. A list of separate values, never one comma-joined string.
- `since`: ISO date or timestamp. Omit to continue from a cursor.
- `sourceId`: Source ids (a publisher's sub-sources, as get_regulatory_coverage lists them). A list of separate values, never comma-joined.

### `search_regulatory_documents` (~329 tokens)

Search Indian Regulatory Documents

Search Indian regulatory publications: circulars, orders, notices and press releases from named government regulators. Not case law, statute text or commentary. Capture began 2026-08-23, so an empty result for an earlier date does not mean nothing was published. Not an in-force view. Filters are lists. Pass nextCursor back unchanged while hasMore is true. total null means not measured; 0 means none. Cost: 1 credit.

Input parameters:

- `cursor`: Opaque. Pass back exactly the nextCursor of the previous page. Do not parse, edit or construct one.
- `docType`: Document types as returned in results. A list of separate values.
- `facets`: True to also return the filter values available.
- `id`: Fetch these document ids in one call, instead of searching.
- `limit`: Page size, 1 to 100. Omit to use the default.
- `publishedFrom`: ISO date, YYYY-MM-DD, as the publisher dated it.
- `publishedTo`: ISO date, YYYY-MM-DD, as the publisher dated it.
- `publisherId`: Publisher ids, e.g. ['sebi', 'rbi']. A list of separate values, never one comma-joined string.
- `q`: Words to search for. Omit to list by filters alone.
- `sort`: Order of results. Omit for the default.
- `sourceId`: Source ids (a publisher's sub-sources, as get_regulatory_coverage lists them). A list of separate values, never comma-joined.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/vaquill-ai-vaquill-mcp/reg-mcp#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 74
- 2026-11-19: 73
- 2026-11-18: 73
- 2026-11-17: 72
- 2026-11-16: 72
- 2026-11-15: 71
- 2026-11-14: 71
- 2026-11-13: 70

## Common questions

### What is the Vaquill MCP server?

Vaquill is an MCP server listed in the public MCP registry as io.github.Vaquill-AI/vaquill-mcp. Search US and Indian statutes, regulations, constitutions, and court rules. This page covers its hosted endpoint (https://reg-mcp.vaquill.ai/mcp).

### Is the Vaquill MCP server safe to use?

Vaquill scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Vaquill MCP server expose?

Vaquill exposes 5 tools: get_regulatory_coverage, get_regulatory_document, get_regulatory_document_file, list_regulatory_changes, search_regulatory_documents. Their descriptions and schemas cost roughly 888 tokens of context every time the server is loaded.

### Does the Vaquill MCP server require authentication?

No. We connected to Vaquill without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Vaquill MCP server still maintained?

Vaquill is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Vaquill MCP server?

VerifyMCP ran 13 checks on Vaquill, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://reg-mcp.vaquill.ai/mcp
- Repository: https://github.com/Vaquill-AI/vaquill-mcp
- Changelog RSS feed: https://verifymcp.io/servers/vaquill-ai-vaquill-mcp/reg-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/vaquill-ai-vaquill-mcp/reg-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/vaquill-ai-vaquill-mcp/reg-mcp.json
- HTML version of this page: https://verifymcp.io/servers/vaquill-ai-vaquill-mcp/reg-mcp
