_ registry / mcp streamable-http · checked 2h ago

insc-one

https://insc.one

Registry code: f8779515771e2d1c

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://insc.one/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is insc-one live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is insc-one free to use?
Yes — the hub reached it with no key and no payment.
What tools does insc-one have?
5 tools: resolve_citation, format_citation, get_ratio, search_cases, check_treatment.
Is insc-one safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,187ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
3 open 2 never probed 3 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_ratio open 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "citation"
  ],
  "properties": {
    "issue": {
      "type": "string",
      "description": "Optional focus issue or statutory section to prioritize relevant headnotes."
    },
    "citation": {
      "type": "string",
      "description": "INSC neutral citation or any resolvable reference."
    }
  }
}
    arguments 16 lines
  • search_cases open 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 5,
      "maximum": 15,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "Natural-language legal question or keywords, e.g. 'FIR mandatory registration', 'CoC commercial wisdom IBC'."
    }
  }
}
    arguments 18 lines
  • check_treatment open 2h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "citation"
  ],
  "properties": {
    "citation": {
      "type": "string",
      "description": "INSC neutral citation or any resolvable reference."
    }
  }
}
    arguments 12 lines
  • resolve_citation unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "The reference to resolve, e.g. \"2013 INSC 768\", \"(2014) 2 SCC 1\", \"AIR 2014 SC 187\", \"Lalita Kumari\", \"Arnesh Kumar arrest\"."
    }
  }
}
    arguments 12 lines
  • format_citation unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "citation"
  ],
  "properties": {
    "style": {
      "enum": [
        "insc_primary",
        "insc_only",
        "full_parallel"
      ],
      "type": "string",
      "default": "insc_primary"
    },
    "citation": {
      "type": "string",
      "description": "INSC neutral citation or any resolvable reference."
    }
  }
}
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f8779515771e2d1c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f8779515771e2d1c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f8779515771e2d1c/badge.svg)](https://brick.blue/agent/f8779515771e2d1c?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.