# Vaquill (remote · mcp.vaquill.ai) Search US and Indian statutes, regulations, constitutions, and court rules. - Trust score: 74/100 (medium) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-10-05 ## Components - remote · `mcp.vaquill.ai`: 74/100 (this document), [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`: 38/100, [markdown](https://verifymcp.io/servers/vaquill-ai-vaquill-mcp/mcp.md), [page](https://verifymcp.io/servers/vaquill-ai-vaquill-mcp/mcp) ## Channel facts - Endpoint: `https://mcp.vaquill.ai/in/mcp` - Transports: `streamable-http` - Auth: `required` - Version: `0.4.1` ## 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-10-05. - **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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. - 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**: 79/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 5014 tokens (~200/item across 25 items; 22 tools + 3 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 10/100 - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 99/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 97% of tool parameters carry a description. - Structured output schemas are declared (100% 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 22 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 23 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://mcp.vaquill.ai/in/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://mcp.vaquill.ai/in/mcp' ``` ### Cursor ```json { "mcpServers": { "vaquill-ai-vaquill-mcp": { "url": "https://mcp.vaquill.ai/in/mcp" } } } ``` ### VS Code ```json { "servers": { "vaquill-ai-vaquill-mcp": { "type": "http", "url": "https://mcp.vaquill.ai/in/mcp" } } } ``` ### Codex ```toml [mcp_servers.vaquill-ai-vaquill-mcp] url = "https://mcp.vaquill.ai/in/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "vaquill-ai-vaquill-mcp": { "type": "remote", "url": "https://mcp.vaquill.ai/in/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add vaquill-ai-vaquill-mcp --url 'https://mcp.vaquill.ai/in/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: vaquill-ai-vaquill-mcp: url: "https://mcp.vaquill.ai/in/mcp" ``` ### Netclaw ```json { "McpServers": { "vaquill-ai-vaquill-mcp": { "Transport": "http", "Url": "https://mcp.vaquill.ai/in/mcp" } } } ``` ### Vellum ```bash assistant mcp add vaquill-ai-vaquill-mcp -t streamable-http -u 'https://mcp.vaquill.ai/in/mcp' ``` ### Other ```json { "mcpServers": { "vaquill-ai-vaquill-mcp": { "type": "http", "url": "https://mcp.vaquill.ai/in/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-10-04 (score 74, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-03 (score 73, 0) - [functional improvement] Stability: unverified → 0.03 ### 2026-10-02 (score 73) First indexed and scored. ## MCP tools (22) ### `fetch` (~106 tokens) Fetch Indian Enactment Fetch one Indian enactment by the `id` from a `search` result, returning `{id, title, text, url, metadata}`. Also accepts a source URL or a bare path. NOTE: the India corpus serves an enactment as publisher links rather than inline text, so `text` carries the title and `metadata` carries the PDF, HTML and plain-text URLs to read. Prefer `get_act_text` if you can call it. Input parameters: - `id` (string, required) ### `get_act_amendments` (~312 tokens) Act Amendment History The amendment history recorded against one enactment: substitutions, insertions and omissions, each with the amending Act and its effective date (e.g. 'Subs. by Act 22 of 2023, s. 44 (w.e.f. 13-11-2025)'). Use to check whether a provision still reads as enacted before relying on its text. An empty list means no amendment was recorded, NOT that the Act was never amended. Cost: 5 credits. Input parameters: - `act_id` (string, required): Section identifier, e.g. `USC_T42_C21_S1983` (Title 42, Chapter 21, Section 1983, written 42 U.S.C. 1983). Take it from a search result rather than assembling it: the title and section are derivable… - `page` (integer): 1-based page number. - `pageSize` (integer): Results per page (1-200). - `section`: Keep only footnotes attached to this section, written exactly as the publisher does. Alphanumeric suffixes are part of the number, not a sub-provision: `498A` is one section, not section 498 clause A. - `type`: Action classes are returned in nominal form, but filters accept both nominal and stored verbal spellings. For example, `substitution` and `substituted` are both accepted. ### `get_act_section` (~259 tokens) Act Section Metadata Metadata for one provision, including its citation, position in the act, structural features and references. Use when identifying or inspecting a provision without fetching its wording. Text is not included. Use get_act_section_body to read it. wordCount covers all passages, and actsReferenced normalizes whitespace before deduplication so publisher line breaks do not create duplicate acts. Cost: 2 credits. Input parameters: - `act_id` (string, required): Section identifier, e.g. `USC_T42_C21_S1983` (Title 42, Chapter 21, Section 1983, written 42 U.S.C. 1983). Take it from a search result rather than assembling it: the title and section are derivable… - `section_number` (string, required): Section number as the publisher writes it, e.g. `302` or `498A`; an alphanumeric suffix is part of the number, not a sub-provision. Near spellings (`498-A`, `Sec. 302`, `302(1)`) are tried when the e… ### `get_act_section_body` (~249 tokens) Act Section Text The publisher's full text for one provision, taken directly from the act document without synthesized search headers. Use when reading, quoting or citing the provision's wording rather than its metadata. Amendments are not applied to this text. Check get_section_history for recorded changes before treating the wording as current law. Cost: 3 credits. Input parameters: - `act_id` (string, required): Section identifier, e.g. `USC_T42_C21_S1983` (Title 42, Chapter 21, Section 1983, written 42 U.S.C. 1983). Take it from a search result rather than assembling it: the title and section are derivable… - `section_number` (string, required): Section number as the publisher writes it, e.g. `302` or `498A`; an alphanumeric suffix is part of the number, not a sub-provision. Near spellings (`498-A`, `Sec. 302`, `302(1)`) are tried when the e… ### `get_act_status` (~170 tokens) Act Status and Repeal Record An act's standing in three separate fields, publisherStatus for India Code's label, servedStatus for API availability and repealClaim for the publisher's sourced repeal record. Use when assessing whether an act remains law or why it is unavailable. These are not one verdict. A repealClaim does not verify that the repealing instrument was brought into force. Cost: 1 credit. Input parameters: - `act_id` (string, required): Section identifier, e.g. `USC_T42_C21_S1983` (Title 42, Chapter 21, Section 1983, written 42 U.S.C. 1983). Take it from a search result rather than assembling it: the title and section are derivable… ### `get_act_structure` (~167 tokens) Act Table of Contents An act's table of contents, with chapters and parts where the publisher supplies them and provisions listed beneath. Use when locating a section or planning a traversal of the act. hasHierarchy is false for most acts, where nodes is a flat section list rather than an error. Section numbers sort numerically with alphabetic suffixes attached. Cost: 2 credits. Input parameters: - `act_id` (string, required): Section identifier, e.g. `USC_T42_C21_S1983` (Title 42, Chapter 21, Section 1983, written 42 U.S.C. 1983). Take it from a search result rather than assembling it: the title and section are derivable… ### `get_act_text` (~142 tokens) Act Text Source links for one enactment: the plain-text, PDF and HTML renderings, plus how many sections it holds. Use when the user wants to read or cite the Act itself rather than a matched section. Cost: 3 credits. Input parameters: - `act_id` (string, required): Section identifier, e.g. `USC_T42_C21_S1983` (Title 42, Chapter 21, Section 1983, written 42 U.S.C. 1983). Take it from a search result rather than assembling it: the title and section are derivable… ### `get_corresponding_provisions` (~178 tokens) IPC/CrPC to BNS/BNSS Mapping Map a repealed Indian criminal code to the 2023 code that replaced it, section by section: IPC to BNS and CrPC to BNSS, in force from 1 July 2024. Pass either side ('ipc' or 'bns' both work). Use whenever a source, a pleading or the user cites an old section number, so you answer under the provision actually in force rather than the repealed one. 'iea'/'bsa' return 404 until that mapping lands. Cost: 1 credit. Input parameters: - `act_code` (string, required): `ipc` and `bns` return the same mapping, as do `crpc` and `bnss`. Case-insensitive. `iea` and `bsa` are accepted but return 404 until their mapping is available. ### `get_coverage` (~81 tokens) India Corpus Coverage India corpus counts for acts and provisions, broken down by jurisdiction, regulator and status, plus coverage depth. Use when checking whether the corpus supports a question before searching or interpreting an empty result. The depth block distinguishes text coverage from much thinner parsed amendment coverage. actsClaimingAmendmentsWithoutEvents marks missing records, not an absence of amendments. Free. ### `get_india_credit_balance` (~78 tokens) Credit Balance The account-wide spendable credit balance shared by the India and United States APIs. Use for pre-flight checks or low-balance alerts from an India workflow. This returns the same balance as get_credit_balance, not a separate India allowance. Check bySource before assuming credits will last. Subscription credits expire at the period end. Free. ### `get_pricing_in` (~103 tokens) India Credit Pricing Credit-to-price conversion and per-endpoint costs for the India legislation API, billed in US dollars. Use when estimating a workflow or comparing endpoint charges. Set region to US for United States primary-law pricing instead. Both surfaces use the same API key and account-wide credit balance. No authentication is required. Input parameters: - `region`: Defaults to the jurisdiction of the documentation you are reading. If omitted, returns pricing only for that jurisdiction's endpoints, not prices across jurisdictions. ### `get_section_history` (~299 tokens) Section Amendment History Recorded amendments to one provision, including the changing Act and section, effective dates and replaced wording where published. Use when tracing changes or checking whether published text reflects later amendments. An empty history can mean no changes or no parsed records, as coverage explains. Read appliedStatus on every event. Amendments are not applied to served text. Cost: 2 credits. Input parameters: - `act_id` (string, required): Section identifier, e.g. `USC_T42_C21_S1983` (Title 42, Chapter 21, Section 1983, written 42 U.S.C. 1983). Take it from a search result rather than assembling it: the title and section are derivable… - `asOf`: Split the recorded amendments around a date (YYYY-MM-DD). Returns a timeline, never reconstructed text. - `limit` (integer): Events per page. - `offset` (integer): Zero-based offset. - `section_number` (string, required): Section number as the publisher writes it, e.g. `302` or `498A`; an alphanumeric suffix is part of the number, not a sub-provision. Near spellings (`498-A`, `Sec. 302`, `302(1)`) are tried when the e… ### `india_act_cited_by` (~235 tokens) Acts Citing This One Paged inbound citations from provisions elsewhere in the corpus that name an act. Use when finding provisions that mention the act, rather than following its outbound references. Matching uses the act's title, not its identifier, so title variants and line breaks can be missed. Read matchBasis and treat results as a floor. total counts distinct citing provisions across all pages. Cost: 2 credits. Input parameters: - `act_id` (string, required): Section identifier, e.g. `USC_T42_C21_S1983` (Title 42, Chapter 21, Section 1983, written 42 U.S.C. 1983). Take it from a search result rather than assembling it: the title and section are derivable… - `limit`: DEPRECATED alias for `pageSize`, kept working for clients written against the original shape. Send one or the other, not both. - `page` (integer): 1-based page number. - `pageSize`: Rows per page (1-100). Defaults to 25. ### `india_act_definitions` (~236 tokens) Defined Terms in an Act Extracted defined terms and their defining provisions, plus a separate definitionSections list. Use when a question turns on an act's own meaning of a term. Extraction covers only a minority of acts, so an empty result does not mean the act defines nothing. definitionSections identifies provisions to read even without extracted terms. terms is paged, but definitionSections is not. Cost: 2 credits. Input parameters: - `act_id` (string, required): Section identifier, e.g. `USC_T42_C21_S1983` (Title 42, Chapter 21, Section 1983, written 42 U.S.C. 1983). Take it from a search result rather than assembling it: the title and section are derivable… - `limit`: DEPRECATED alias for `pageSize`, kept working for clients written against the original shape. Send one or the other, not both. - `page` (integer): 1-based page number. - `pageSize`: Rows per page (1-100). Defaults to 25. ### `india_act_subordinate` (~237 tokens) Rules Made Under an Act Paged rules, regulations, notifications and orders the publisher records as made under an act. Use when looking beyond the parent statute to its subordinate instruments. Matching uses the parent's title, not parent_act_id, which is an India Code identifier that does not address this corpus. Check matchBasis. total counts distinct instruments across all pages, while returned counts rows on this page. Cost: 2 credits. Input parameters: - `act_id` (string, required): Section identifier, e.g. `USC_T42_C21_S1983` (Title 42, Chapter 21, Section 1983, written 42 U.S.C. 1983). Take it from a search result rather than assembling it: the title and section are derivable… - `limit`: DEPRECATED alias for `pageSize`, kept working for clients written against the original shape. Send one or the other, not both. - `page` (integer): 1-based page number. - `pageSize`: Rows per page (1-100). Defaults to 25. ### `india_section_references` (~262 tokens) Citations From a Section Outbound citations from a provision to other enactments and sections of its own act. Use when following references outwards, not finding citations to the act. actId identifies served targets, while resolved false marks coverage gaps rather than parse failures. Results are not paged. totalActs and totalSections give full counts, so check truncated before treating returned references as complete. Cost: 2 credits. Input parameters: - `act_id` (string, required): Section identifier, e.g. `USC_T42_C21_S1983` (Title 42, Chapter 21, Section 1983, written 42 U.S.C. 1983). Take it from a search result rather than assembling it: the title and section are derivable… - `section_number` (string, required): Section number as the publisher writes it, e.g. `302` or `498A`; an alphanumeric suffix is part of the number, not a sub-provision. Near spellings (`498-A`, `Sec. 302`, `302(1)`) are tried when the e… ### `list_act_filters` (~55 tokens) Act Filter Values Self-describing filter vocabulary: every category, state, department and status the acts corpus actually holds, with counts. Call this before filtering, so a query uses a value that exists instead of returning empty because the spelling was wrong. ### `list_acts` (~446 tokens) Browse Indian Acts Browse and filter enactments rather than searching their text: by jurisdiction (central or a state), issuing regulator, year and status. Use when the user wants to know WHAT exists in an area before asking what it says, or to confirm an Act's exact title before citing it. Cost: 1 credit. Input parameters: - `category`: Jurisdictional class of the instrument. `repealed` and `spent` are accepted for backward compatibility and resolve against the act's status instead. Values: `central`, `state`, `regulatory`, `repeale… - `department`: Accepts both regulator slugs such as `sebi` and `rbi` and free-text state department names such as `Law Department`. Values are not limited to a fixed enum or a uniform slug format. - `page` (integer): 1-based page number. - `pageSize` (integer): Results per page (1-100). - `search`: Keep only acts whose title contains this substring, matched case-insensitively. A title filter, not a search over the text: use POST /acts/search for that. - `sort` (string): Sort order. `popular` is DEPRECATED and behaves as `year_desc`: it ordered by a read counter held only in the retired store. Values: `year_desc`, `year_asc`, `title_asc`, `title_desc`, `popular`. - `state`: Jurisdiction slug. `central` is a value here, for Union legislation. Live counts per jurisdiction are on GET /acts/coverage. - `status`: The publisher's lifecycle status for the act. Their claim, not our verdict: see GET /acts/{actId}/status. Values: `in_force`, `repealed`, `superseded`, `spent`. - `yearFrom`: Earliest year of enactment to include, inclusive. Matched against the publisher's own year field, which is occasionally corrupt, so there is no lower bound and a value below 1800 is a legitimate way… - `yearTo`: Latest year of enactment to include, inclusive. ### `resolve_india_citation` (~196 tokens) Resolve Indian Citation The provision named by an Indian legal citation, accepting common abbreviations and flexible element order. Use when a user provides a citation rather than a research topic, such as s.302 IPC, O. 39 R. 1 CPC or Art. 21 of the Constitution. Subsection and clause references are supported. Malformed citations are rejected rather than reported as not found. Cost: 2 credits. Input parameters: - `asAtDate`: The date the conduct or document belongs to, as YYYY-MM-DD. This is how a caller says which side of the 2023 recodification they mean: without it, a criminal section number resolves to BOTH the old c… - `cite` (string, required): One citation string. - `state`: Narrow to one jurisdiction. Required for a State-universal title, where the same short title names a different act in each State. ### `resolve_india_citations_batch` (~180 tokens) Resolve Indian Citations (Batch) Provision resolutions for a list of Indian legal citations, using the same resolver as resolve_india_citation. Use when several citations need resolving without individual calls. Accepts up to 50 distinct citations and 500 entries before deduplication. One citation failing does not invalidate the others. Unknown request fields are rejected rather than ignored. Cost: 2 credits. Input parameters: - `asAtDate`: The date the conduct or document belongs to, as YYYY-MM-DD. This is how a caller says which side of the 2023 recodification they mean: without it, a criminal section number resolves to BOTH the old c… - `citations` (array, required): Citation strings, as a lawyer would type them. - `state`: Narrow to one jurisdiction. Required for a State-universal title. ### `search` (~85 tokens) Search Indian Legislation Generic corpus search over Indian Central and State legislation, returning `{id, title, url}` records for citation. Present so this server works in clients that require the standard search/fetch pair. Prefer `search_acts` if you can call it: it filters by category, state, year and status. Pair with `fetch` to read a result. Input parameters: - `query` (string, required) ### `search_acts` (~806 tokens) Search Indian Acts Search Indian legislation down to the individual section: Central and State Acts plus the instruments of the principal regulators (SEBI, RBI, MCA, IRDAI, TRAI, DGFT). Use for any 'what does Indian law say' question. Supports boolean and phrase queries; filters by category, state, year and status. Returns sections with title, chapter and a sourceUrl pointing at the publisher's own document. The returned actId (e.g. 'IND_central_2065') feeds every acts tool. Cost: 2 credits. Input parameters: - `actStatus`: Filter by the publisher's lifecycle status. Accepts one value or a list. This is the publisher's claim, not our verdict: see GET /acts/{actId}/status. Values: `in_force`, `repealed`, `superseded`, `s… - `actTitle`: Filter by words in the act's title. Each word must appear, so `Bharatiya Nyaya` narrows to the Sanhita. - `category`: Jurisdictional class. `repealed` and `spent` are accepted for backward compatibility and resolve against `actStatus` instead. Values: `central`, `state`, `regulatory`, `repealed`, `spent`. - `department`: Accepts both regulator slugs such as `sebi` and `rbi` and free-text state department names such as `Law Department`. Values are not limited to a fixed enum or a uniform slug format. - `excludeRepealed` (boolean): Drop provisions whose act the publisher records as repealed or spent. Off by default, because repealed law is still law that was in force and is routinely the thing being researched. - `isSubordinate`: True for subordinate instruments only (rules, notifications, circulars, orders); false for principal acts only. Omit for both. - `legalSubject`: Accepts one value or a list, matched against subject classifications assigned at ingest. - `matchType` (string): One of `any`, `all`, `phrase`. Filters ranked candidates rather than re-querying the index, so `phrase` matches only within the top candidates and not every corpus match. Narrow with structured filte… - `page` (integer): 1-based page number. `page * pageSize` may not exceed 100; narrow the query with filters to reach deeper matches. - `pageSize` (integer): Results per page (1-50). - `provisionType`: Filter by what the provision DOES. Accepts one value or a list. Values: `mandatory`, `general`, `prohibitory`, `overriding`, `discretionary`, `declaratory`. - `query` (string, required): Search query. - `sectionNumber`: Filter by exact section number. The publisher's own numbering, which is not an integer: `498A`, `376DA` and `2-A` all occur, and the alphabetic suffix is part of the number rather than a sub-provisio… - `sectionType`: Filter by structural kind of the passage. Accepts one value or a list. Values: `amendment_provision`, `article`, `body`, `chapter_heading`, `definition_clause`, `definitions`, `part_heading`, `preamb… - `state`: Jurisdiction slug. `central` is a value here, for Union legislation. Live counts per jurisdiction are on GET /acts/coverage. - `yearFrom`: Earliest year of enactment to include, inclusive. Matched against the publisher's own year field, which is occasionally corrupt, so there is no lower bound and a value below 1800 is a legitimate way… - `yearTo`: Latest year of enactment to include, inclusive. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/vaquill-ai-vaquill-mcp/in-mcp#diagnostics ## Score history - 2026-10-05: 74 - 2026-10-04: 74 - 2026-10-03: 73 - 2026-10-02: 73 ## 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://mcp.vaquill.ai/in/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 22 tools: fetch, get_act_amendments, get_act_section, get_act_section_body, get_act_status, and 17 more. Their descriptions and schemas cost roughly 4,882 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 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://mcp.vaquill.ai/in/mcp - Authorisation metadata: https://mcp.vaquill.ai/.well-known/oauth-protected-resource/in/mcp - Repository: https://github.com/Vaquill-AI/vaquill-mcp - Changelog RSS feed: https://verifymcp.io/servers/vaquill-ai-vaquill-mcp/in-mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/vaquill-ai-vaquill-mcp/in-mcp.json - HTML version of this page: https://verifymcp.io/servers/vaquill-ai-vaquill-mcp/in-mcp