in.co.buildwright/compliance
REMOTE · BUILDWRIGHT.CO.IN
Indian business compliance answers: MCA late fees, filing calendar, cheque bounce, MSME interest.
Available components
Last scanned (21 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability68
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +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.
- 19 Nov 26 +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.
- 16 Nov 26 +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.
- 14 Nov 26 +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.
- 12 Nov 26 +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.
- 10 Nov 26 +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.
- 9 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- New tool “company_lookup” functional
- 8 Nov 26 70
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 21 Nov 2026 · Probed https://buildwright.co.in/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.errkhealth.com | CN=WR3,O=Google Trust Services,C=US | 30 Oct 2026 | 28 Jan 2027 | RSA 2048 | SHA256-RSA | 5906c43e051ce97c129061a675e17d7c |
| SANs: app.errkhealth.com, ignition8security.com, deal-reel.com, pw.bbrrdream.com, www.littlepixels.nz, nabergall.com, uat2-account.canstar.com.au, garcezmoveisplanejados.com, shop.esmarage.com, insquoo.com, mikrotickets.com, jondh.com and 88 more | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of buildwright.co.in. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| in. | DS published | 10094 | 13 | Verified |
| co.in. | DS published | 712 | 13 | Verified |
| buildwright.co.in. | No DS | 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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://buildwright.co.in/api/mcp | Verified | 200 | |
| http (plaintext) | http://buildwright.co.in/api/mcp | HTTPS enforced | 301 | https://buildwright.co.in/api/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 →
cheque_bounce_timer Cheque bounce (s.138) timeline ~165
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cheque_date | string | yes | Date in YYYY-MM-DD form. The date written on the cheque |
| memo_date | string | yes | 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 | yes | 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) |
No output schema declared.
No examples provided.
company_lookup Indian company or LLP lookup by CIN or LLPIN ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cin | string | yes | 21-character CIN (e.g. U72200DL2020PTC123456) or LLPIN (e.g. AAB-1234) |
No output schema declared.
No examples provided.
compliance_calendar Annual compliance calendar ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| incorporation_date | string | yes | Date in YYYY-MM-DD form |
No output schema declared.
No examples provided.
engage_buildwright Get it handled by BuildWright ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_free_tools BuildWright free tools ~35
The free Indian compliance tools and document templates BuildWright publishes, with URLs, for anything this server's tools do not compute.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_services BuildWright services and fees ~87
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mca_late_fee MCA late filing fee ~194
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.
| Name | Type | Req | Description |
|---|---|---|---|
| due_date | string | yes | Date in YYYY-MM-DD form. When the filing was due |
| filing_date | string | yes | Date in YYYY-MM-DD form. When it will actually be filed (today if filing now) |
| form | string | yes | 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' |
No output schema declared.
No examples provided.
msme_interest MSME delayed payment interest ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptance_date | string | yes | 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 | yes | Unpaid principal in rupees |
| category | string | yes | Supplier's MSME category at the time of the transaction |
| registered | string | yes | When the supplier's Udyam registration was made, relative to the order |
| trader | string | yes | Is the supplier a retail/wholesale trader (NIC 45/46/47)? |
No output schema declared.
No examples provided.
request_service Request a callback from BuildWright ~267
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.
| Name | Type | Req | Description |
|---|---|---|---|
| consent | boolean | yes | true only after the person explicitly agreed to be contacted |
| string | – | Email, only if the person gave one | |
| entity_type | string | – | Who the work is for |
| name | string | yes | 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 | yes | 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 |
No output schema declared.
No examples provided.
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.
remote · buildwright.co.in
claude mcp add --transport http in-co-buildwright-compliance 'https://buildwright.co.in/api/mcp'
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.