Vaquill
REMOTE · REG-MCP.VAQUILL.AI · 3 COMPONENTS
Search US and Indian statutes, regulations, constitutions, and court rules.
Available components
Last scanned (22 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Education and Research
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. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (80% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +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.
- 18 Nov 26 +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.
- 16 Nov 26 +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.
- 14 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 13 Nov 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://reg-mcp.vaquill.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vaquill.ai | CN=WE1,O=Google Trust Services,C=US | 16 Nov 2026 | 14 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 5d78fdceb9d57d940e298d3299c2c91b |
| SANs: vaquill.ai, *.vaquill.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of reg-mcp.vaquill.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| vaquill.ai. | DS published | 2371 | 13 | Verified |
| reg-mcp.vaquill.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://reg-mcp.vaquill.ai/mcp | Verified | 200 | |
| http (plaintext) | http://reg-mcp.vaquill.ai/mcp | HTTPS enforced | 301 | https://reg-mcp.vaquill.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_regulatory_coverage Regulatory Coverage ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
Structured output declared, but exposes no named fields.
No examples provided.
get_regulatory_document Regulatory Document ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Document id from a search or change result. |
| include | – | – | Extra parts to return. Omit for metadata only. |
Structured output declared, but exposes no named fields.
No examples provided.
get_regulatory_document_file Regulatory Document File ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Document id from a search or change result. |
No output schema declared.
No examples provided.
list_regulatory_changes Regulatory Change Feed ~249
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
Structured output declared, but exposes no named fields.
No examples provided.
search_regulatory_documents Search Indian Regulatory Documents ~329
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
Structured output declared, but exposes no named fields.
No examples provided.
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.
remote · reg-mcp.vaquill.ai
claude mcp add --transport http vaquill-ai-vaquill-mcp 'https://reg-mcp.vaquill.ai/mcp'
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.