# in.co.buildwright/compliance (remote · buildwright.co.in)

Indian business compliance answers: MCA late fees, filing calendar, cheque bounce, MSME interest.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `buildwright.co.in`: 76/100 (this document), [markdown](https://verifymcp.io/servers/in-co-buildwright-compliance/api-mcp.md), [page](https://verifymcp.io/servers/in-co-buildwright-compliance/api-mcp)

## Channel facts

- Endpoint: `https://buildwright.co.in/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1309 tokens (~145/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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).
  - 96% 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the in.co.buildwright/compliance MCP server?

in.co.buildwright/compliance is a hosted endpoint at https://buildwright.co.in/api/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 in-co-buildwright-compliance 'https://buildwright.co.in/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "in-co-buildwright-compliance": {
      "url": "https://buildwright.co.in/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "in-co-buildwright-compliance": {
      "type": "http",
      "url": "https://buildwright.co.in/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.in-co-buildwright-compliance]
url = "https://buildwright.co.in/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "in-co-buildwright-compliance": {
      "type": "remote",
      "url": "https://buildwright.co.in/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add in-co-buildwright-compliance --url 'https://buildwright.co.in/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  in-co-buildwright-compliance:
    url: "https://buildwright.co.in/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "in-co-buildwright-compliance": {
      "Transport": "http",
      "Url": "https://buildwright.co.in/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add in-co-buildwright-compliance -t streamable-http -u 'https://buildwright.co.in/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "in-co-buildwright-compliance": {
      "type": "http",
      "url": "https://buildwright.co.in/api/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-21 (score 76, +1)

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

### 2026-11-19 (score 75, +1)

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

### 2026-11-16 (score 74, +1)

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

### 2026-11-14 (score 73, +1)

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

### 2026-11-12 (score 72, +1)

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

### 2026-11-10 (score 71, +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-11-09 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “company_lookup”

### 2026-11-08 (score 70)

First indexed and scored.

## MCP tools (9)

### `mca_late_fee` (~194 tokens)

MCA late filing fee

The MCA additional fee or statutory penalty for a late company or LLP filing in India: AOC-4, MGT-7/7A, INC-20A, LLP Form 8, LLP Form 11. Returns the figure or multiplier with days late, the legal source, and the consequence of not filing.

Input parameters:

- `due_date` (string, required): Date in YYYY-MM-DD form. When the filing was due
- `filing_date` (string, required): Date in YYYY-MM-DD form. When it will actually be filed (today if filing now)
- `form` (string, required): Which filing
- `llp_size` (string): LLP Form 8/11 only: 'small' = small LLP under s.2(1)(ta), LLP Act 2008 (contribution up to Rs 25 lakh and turnover up to Rs 40 lakh in the preceding financial year), else 'other'

### `compliance_calendar` (~123 tokens)

Annual compliance calendar

The dated statutory filing calendar for an Indian private limited company, one person company or LLP: what is due and when, from the incorporation date, with first-year rules (s.2(41), first AGM) applied.

Input parameters:

- `agm_date` (string): Date in YYYY-MM-DD form. Private Limited: the AGM date; One Person Company: the date the member signed the resolution adopting the accounts. Omit to assume the last day the law allows
- `entity_type` (string, required)
- `incorporation_date` (string, required): Date in YYYY-MM-DD form

### `company_lookup` (~111 tokens)

Indian company or LLP lookup by CIN or LLPIN

Looks up an Indian company or LLP in the Ministry of Corporate Affairs' company master data on data.gov.in: name, type, incorporation date, MCA status and Registrar of Companies. Feed the type and date into compliance_calendar. The dataset runs a few months behind MCA, so a company set up recently may not be found.

Input parameters:

- `cin` (string, required): 21-character CIN (e.g. U72200DL2020PTC123456) or LLPIN (e.g. AAB-1234)

### `cheque_bounce_timer` (~165 tokens)

Cheque bounce (s.138) timeline

The live deadline clock after a cheque bounce in India under s.138 Negotiable Instruments Act: when the demand notice must go, when the drawer's 15 days run out, and the last day to file the complaint.

Input parameters:

- `cheque_date` (string, required): Date in YYYY-MM-DD form. The date written on the cheque
- `memo_date` (string, required): Date in YYYY-MM-DD form. The bank return memo date
- `notice_received_date` (string): Date in YYYY-MM-DD form. When the drawer received the notice, if known
- `notice_sent` (boolean, required): Has the written demand notice gone to the drawer?
- `presentation_date` (string): Date in YYYY-MM-DD form. When the cheque was deposited (needed to detect a stale cheque)

### `msme_interest` (~180 tokens)

MSME delayed payment interest

Compound interest a buyer owes a micro or small enterprise on a delayed payment under s.16 MSMED Act (three times the RBI bank rate, compounded monthly), with the covered/not-covered verdict.

Input parameters:

- `acceptance_date` (string, required): Date in YYYY-MM-DD form. The day the buyer accepted the goods or services (delivery day if no objection was raised)
- `agreed_date` (string): Date in YYYY-MM-DD form. Payment date agreed in writing, if any
- `amount` (number, required): Unpaid principal in rupees
- `category` (string, required): Supplier's MSME category at the time of the transaction
- `registered` (string, required): When the supplier's Udyam registration was made, relative to the order
- `trader` (string, required): Is the supplier a retail/wholesale trader (NIC 45/46/47)?

### `list_free_tools` (~35 tokens)

BuildWright free tools

The free Indian compliance tools and document templates BuildWright publishes, with URLs, for anything this server's tools do not compute.

### `engage_buildwright` (~46 tokens)

Get it handled by BuildWright

How to have a filing, document or compliance task done by BuildWright's people: contact routes and what the firm handles. Use when the user wants the work done for them.

### `list_services` (~87 tokens)

BuildWright services and fees

BuildWright's SEBI adviser services with our fee in rupees, what is included, and the service page, for information. Nothing is sold in the chat: to go ahead, use request_service and BuildWright calls back. Fees to SEBI, BSE or the state are separate at actuals. Show the price exactly as returned; never compute or quote any other figure.

### `request_service` (~267 tokens)

Request a callback from BuildWright

Send the person's request to BuildWright so a person calls them back. Use for any documentation, filing or compliance task, listed or not. Before calling: ask the person for each field in conversation (name, their own 10-digit Indian mobile, optionally email, what they need, entity type, state). Never invent or guess a phone number or name. Then ask explicitly whether BuildWright may contact them about this request, show the privacy policy https://buildwright.co.in/privacy-policy, and set consent to true only if they say yes.

Input parameters:

- `consent` (boolean, required): true only after the person explicitly agreed to be contacted
- `email` (string): Email, only if the person gave one
- `entity_type` (string): Who the work is for
- `name` (string, required): The person's full name, as they gave it
- `need` (string): What they need done, in their words (required when no service_id)
- `notes` (string): Anything else they want us to know
- `phone` (string, required): The person's own 10-digit Indian mobile number, as they gave it
- `service_id` (string): An id from list_services, if the need matches one
- `state` (string): Indian state or union territory

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/in-co-buildwright-compliance/api-mcp#diagnostics

## Score history

- 2026-11-21: 76
- 2026-11-20: 75
- 2026-11-19: 75
- 2026-11-18: 74
- 2026-11-17: 74
- 2026-11-16: 74
- 2026-11-15: 73
- 2026-11-14: 73
- 2026-11-13: 72
- 2026-11-12: 72
- 2026-11-11: 71
- 2026-11-10: 71
- 2026-11-09: 70
- 2026-11-08: 70

## Common questions

### What is the in.co.buildwright/compliance MCP server?

in.co.buildwright/compliance is an MCP server listed in the public MCP registry as in.co.buildwright/compliance. Indian business compliance answers: MCA late fees, filing calendar, cheque bounce, MSME interest. This page covers its hosted endpoint (https://buildwright.co.in/api/mcp).

### Is the in.co.buildwright/compliance MCP server safe to use?

in.co.buildwright/compliance scores 76 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 in.co.buildwright/compliance MCP server expose?

in.co.buildwright/compliance exposes 9 tools: mca_late_fee, compliance_calendar, company_lookup, cheque_bounce_timer, msme_interest, and 4 more. Their descriptions and schemas cost roughly 1,208 tokens of context every time the server is loaded.

### Does the in.co.buildwright/compliance MCP server require authentication?

No. We connected to in.co.buildwright/compliance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the in.co.buildwright/compliance MCP server still maintained?

in.co.buildwright/compliance is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the in.co.buildwright/compliance MCP server?

VerifyMCP ran 13 checks on in.co.buildwright/compliance, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://buildwright.co.in/api/mcp
- Website: https://buildwright.co.in/tools/api
- Changelog RSS feed: https://verifymcp.io/servers/in-co-buildwright-compliance/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/in-co-buildwright-compliance/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/in-co-buildwright-compliance/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/in-co-buildwright-compliance/api-mcp
