insc.one — INSC.1 Citation Layer
REMOTE · INSC.ONE
Bench-aware citator for Supreme Court of India precedent: verified INSC cites, extractive ratios.
Available components
Last scanned (10 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 582 tokens (~97/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 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.
- 3 Nov 26 0
- 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 security
- 2 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.
- 31 Oct 26 +1
- Schema quality: 459 → 584 ▼ functional
- Tool coverage: 75% → 80% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “audit_brief” functional
- 30 Oct 26 62
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 5 Nov 2026 · Probed https://insc.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=insc.one | CN=YE1,O=Let's Encrypt,C=US | 28 Oct 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 59969c4019b6ad19edc5d32a20ad113a3d9 |
| SANs: insc.one, www.insc.one | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of insc.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| insc.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
| Header | Value |
|---|---|
| content-security-policy | upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://insc.one/mcp | Verified | 200 | |
| http (plaintext) | http://insc.one/mcp | HTTPS enforced | 301 | https://insc.one/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 →
audit_brief ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| focus_issue | string | – | Optional legal topic to prioritize in the tactical analysis. |
| text | string | yes | The brief, petition excerpt, opponent arguments, or paragraph containing legal citations to audit. |
No output schema declared.
No examples provided.
check_treatment ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | INSC neutral citation or any resolvable reference. |
No output schema declared.
No examples provided.
format_citation ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | INSC neutral citation or any resolvable reference. |
| style | string | – | – |
No output schema declared.
No examples provided.
get_ratio ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | INSC neutral citation or any resolvable reference. |
| issue | string | – | Optional focus issue or statutory section to prioritize relevant headnotes. |
No output schema declared.
No examples provided.
resolve_citation ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The reference to resolve, e.g. "2013 INSC 768", "(2014) 2 SCC 1", "AIR 2014 SC 187", "Lalita Kumari", "Arnesh Kumar arrest". |
No output schema declared.
No examples provided.
search_cases ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Natural-language legal question or keywords, e.g. 'FIR mandatory registration', 'CoC commercial wisdom IBC'. |
No output schema declared.
No examples provided.
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.
remote · insc.one
claude mcp add --transport http one-insc-insc-one 'https://insc.one/mcp'
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.