Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

India Company Diligence

PYPI · INDIA-COMPANY-DILIGENCE

India company data for agents: 3.74M-company MCA mirror, CIN/GSTIN tools, provenance on every field

+5 this week 55 Trust /100

Last scanned (1 hour ago)

Scores higher than 56% of PyPI servers

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability59
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 167 tokens (~41/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
Changelog

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.

  • 5 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 −12
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.20 ▲ functional
    • Package version: 0.1.1 → 0.2.0 functional
  • 30 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 25 Oct 26 50

    First indexed and scored.

Diagnostics

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 · Analysed pypi/india-company-diligence@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 23 packages
Packages resolved 23
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~167 tokens

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 →

Tool Tokens
cin_decode ~27

Decode a Corporate Identity Number without using the mirror or network.

NameTypeReqDescription
cinstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

company_lookup ~28

Look up one company by its 21-character Corporate Identity Number.

NameTypeReqDescription
cinstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

company_search ~38

Search company names case-insensitively, returning at most 50 rows.

NameTypeReqDescription
limitinteger––
namestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

gstin_validate ~74

Validate a GSTIN offline: structure, state code, and mod-36 check digit. Pure offline — no network, no keys. Live fields (legal name, trade name, registration status, filing history) require an authenticated GST API and are stated as missing, never fabricated.

NameTypeReqDescription
gstinstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the India Company Diligence MCP server?

India Company Diligence runs locally as a PyPI package, launched with uvx india-company-diligence. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · india-company-diligence

# add to Claude Code
claude mcp add amit043-india-company-diligence -- uvx india-company-diligence
Common questions

What is the India Company Diligence MCP server?

India Company Diligence is an MCP server listed in the public MCP registry as io.github.amit043/india-company-diligence. India company data for agents: 3.74M-company MCA mirror, CIN/GSTIN tools, provenance on every field. This page covers its PyPI package (india-company-diligence).

Is the India Company Diligence MCP server safe to use?

India Company Diligence scores 55 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 India Company Diligence MCP server expose?

India Company Diligence exposes 4 tools: company_lookup, company_search, cin_decode, gstin_validate. Their descriptions and schemas cost roughly 167 tokens of context every time the server is loaded.

Is the India Company Diligence MCP server still maintained?

India Company Diligence 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.

What licence is the India Company Diligence MCP server under?

India Company Diligence declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.