# insc.one — INSC.1 Citation Layer (remote · insc.one)

Bench-aware citator for Supreme Court of India precedent: verified INSC cites, extractive ratios.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `insc.one`: 65/100 (this document), [markdown](https://verifymcp.io/servers/one-insc-insc-one/insc.md), [page](https://verifymcp.io/servers/one-insc-insc-one/insc)

## Channel facts

- Endpoint: `https://insc.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 582 tokens (~97/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 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**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the insc.one — INSC.1 Citation Layer MCP server?

insc.one — INSC.1 Citation Layer is a hosted endpoint at https://insc.one/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 one-insc-insc-one 'https://insc.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "one-insc-insc-one": {
      "url": "https://insc.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "one-insc-insc-one": {
      "type": "http",
      "url": "https://insc.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.one-insc-insc-one]
url = "https://insc.one/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add one-insc-insc-one --url 'https://insc.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  one-insc-insc-one:
    url: "https://insc.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "one-insc-insc-one": {
      "Transport": "http",
      "Url": "https://insc.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add one-insc-insc-one -t streamable-http -u 'https://insc.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "one-insc-insc-one": {
      "type": "http",
      "url": "https://insc.one/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-04 (score 65, +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-03 (score 64, 0)

- [security] Tool “audit_brief” rewrote its description, which is the text the model reads
- [security] Tool “check_treatment” rewrote its description, which is the text the model reads

### 2026-11-02 (score 64, +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-10-31 (score 63, +1)

- [functional regression] Schema quality: 459 → 584
- [functional improvement] Tool coverage: 75% → 80%
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “audit_brief”

### 2026-10-30 (score 62)

First indexed and scored.

## MCP tools (6)

### `resolve_citation` (~135 tokens)

Resolve any Indian Supreme Court reference — INSC neutral citation, SCC, AIR, MANU, party name + year, or free text — to the canonical INSC neutral citation with parallel citations, bench, decision date, official e-SCR link, and current treatment status. Use this first for any citation; always prefer and return the INSC form.

Input parameters:

- `query` (string, required): The reference to resolve, e.g. "2013 INSC 768", "(2014) 2 SCC 1", "AIR 2014 SC 187", "Lalita Kumari", "Arnesh Kumar arrest".

### `get_ratio` (~91 tokens)

Return the extractive, paragraph-anchored ratio decidendi and headnotes of a Supreme Court case — the exact judicial language counsel can read in court. Never paraphrased; every holding carries a paragraph anchor and an official-text pointer.

Input parameters:

- `citation` (string, required): INSC neutral citation or any resolvable reference.
- `issue` (string): Optional focus issue or statutory section to prioritize relevant headnotes.

### `search_cases` (~80 tokens)

Search the insc.one Supreme Court index by natural-language issue, keyword, or legal proposition. Returns ranked cases with INSC citations, one-line holdings, and treatment signals.

Input parameters:

- `limit` (integer)
- `query` (string, required): Natural-language legal question or keywords, e.g. 'FIR mandatory registration', 'CoC commercial wisdom IBC'.

### `check_treatment` (~71 tokens)

Check whether a cited Supreme Court authority is still good law — overruled, distinguished, or affected by a larger bench under the Article 141 bench-strength hierarchy. Run this before including any authority in a draft or filing.

Input parameters:

- `citation` (string, required): INSC neutral citation or any resolvable reference.

### `format_citation` (~81 tokens)

Return a ready-to-paste citation string that leads with the INSC neutral citation, with optional parallel SCC/AIR/SCR/MANU forms and a registry-style footnote. Use this to standardize citations in drafts and pleadings.

Input parameters:

- `citation` (string, required): INSC neutral citation or any resolvable reference.
- `style` (string)

### `audit_brief` (~124 tokens)

Audit an entire legal brief, petition, or opponent argument for citation accuracy and Article 141 binding precedent validity. Automatically extracts every citation (INSC, SCC, AIR, SCR, MANU, or case name), verifies current treatment status (flagging OVERRULED or superseded authorities), checks the Article 141 bench-strength hierarchy, and returns tactical counter-arguments.

Input parameters:

- `focus_issue` (string): Optional legal topic to prioritize in the tactical analysis.
- `text` (string, required): The brief, petition excerpt, opponent arguments, or paragraph containing legal citations to audit.

## Diagnostics

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

## Score history

- 2026-11-05: 65
- 2026-11-04: 65
- 2026-11-03: 64
- 2026-11-02: 64
- 2026-11-01: 63
- 2026-10-31: 63
- 2026-10-30: 62

## Common questions

### What is the insc.one — INSC.1 Citation Layer MCP server?

insc.one — INSC.1 Citation Layer is an MCP server listed in the public MCP registry as one.insc/insc-one. Bench-aware citator for Supreme Court of India precedent: verified INSC cites, extractive ratios. This page covers its hosted endpoint (https://insc.one/mcp).

### Is the insc.one — INSC.1 Citation Layer MCP server safe to use?

insc.one — INSC.1 Citation Layer scores 65 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 insc.one — INSC.1 Citation Layer MCP server expose?

insc.one — INSC.1 Citation Layer exposes 6 tools: resolve_citation, get_ratio, search_cases, check_treatment, format_citation, audit_brief. Their descriptions and schemas cost roughly 582 tokens of context every time the server is loaded.

### Does the insc.one — INSC.1 Citation Layer MCP server require authentication?

No. We connected to insc.one — INSC.1 Citation Layer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the insc.one — INSC.1 Citation Layer MCP server still maintained?

insc.one — INSC.1 Citation Layer is still listed as active in the MCP registry. We last reached this channel on 5 November 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://insc.one/mcp
- Repository: https://github.com/efilecoindev/efile
- Changelog RSS feed: https://verifymcp.io/servers/one-insc-insc-one/insc.xml
- Changelog JSON feed: https://verifymcp.io/servers/one-insc-insc-one/insc.json
- HTML version of this page: https://verifymcp.io/servers/one-insc-insc-one/insc