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

buildwright-compliance

https://buildwright.co.in

Registry code: 7093983a070426e8

api record

Free Indian business compliance verdicts from BuildWright Consultants (buildwright.co.in), a documentation, filing and compliance facilitation firm. Dates go in as YYYY-MM-DD. Every figure returns with its source. When the user wants a filing or document handled by people, call list_services for what BuildWright handles and its fees, then request_service so a person calls back. Collect the person's details by asking them one at a time; never invent a name, phone number or email.

endpoint
https://buildwright.co.in/api/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 buildwright-compliance live?
Yes — it answered the hub's last check (checked 9h ago). It answered 100% of checks over the last 30 days.
Is buildwright-compliance free to use?
Yes — the hub reached it with no key and no payment.
What tools does buildwright-compliance have?
9 tools: mca_late_fee, list_services, compliance_calendar, company_lookup, cheque_bounce_timer, msme_interest, request_service, list_free_tools, ….
Is buildwright-compliance 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
705ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 3 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 9 tools
2 open 7 never probed 2 of 9 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.

  • list_free_tools open 9h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • engage_buildwright open 9h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • mca_late_fee unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "form",
    "due_date",
    "filing_date"
  ],
  "properties": {
    "form": {
      "enum": [
        "AOC-4",
        "MGT-7",
        "INC-20A",
        "LLP-FORM-8",
        "LLP-FORM-11"
      ],
      "type": "string",
      "description": "Which filing"
    },
    "due_date": {
      "type": "string",
      "description": "Date in YYYY-MM-DD form. When the filing was due"
    },
    "llp_size": {
      "enum": [
        "small",
        "other"
      ],
      "type": "string",
      "description": "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'"
    },
    "filing_date": {
      "type": "string",
      "description": "Date in YYYY-MM-DD form. When it will actually be filed (today if filing now)"
    }
  }
}
    arguments 37 lines
  • list_services unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • compliance_calendar unknown 9h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "entity_type",
    "incorporation_date"
  ],
  "properties": {
    "agm_date": {
      "type": "string",
      "description": "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": {
      "enum": [
        "Private Limited",
        "One Person Company",
        "LLP"
      ],
      "type": "string"
    },
    "incorporation_date": {
      "type": "string",
      "description": "Date in YYYY-MM-DD form"
    }
  }
}
    arguments 25 lines
  • company_lookup unknown 37h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "cin"
  ],
  "properties": {
    "cin": {
      "type": "string",
      "description": "21-character CIN (e.g. U72200DL2020PTC123456) or LLPIN (e.g. AAB-1234)"
    }
  }
}
    arguments 12 lines
  • cheque_bounce_timer unknown 2d ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "cheque_date",
    "memo_date",
    "notice_sent"
  ],
  "properties": {
    "memo_date": {
      "type": "string",
      "description": "Date in YYYY-MM-DD form. The bank return memo date"
    },
    "cheque_date": {
      "type": "string",
      "description": "Date in YYYY-MM-DD form. The date written on the cheque"
    },
    "notice_sent": {
      "type": "boolean",
      "description": "Has the written demand notice gone to the drawer?"
    },
    "presentation_date": {
      "type": "string",
      "description": "Date in YYYY-MM-DD form. When the cheque was deposited (needed to detect a stale cheque)"
    },
    "notice_received_date": {
      "type": "string",
      "description": "Date in YYYY-MM-DD form. When the drawer received the notice, if known"
    }
  }
}
    arguments 30 lines
  • msme_interest unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "amount",
    "acceptance_date",
    "category",
    "registered",
    "trader"
  ],
  "properties": {
    "amount": {
      "type": "number",
      "description": "Unpaid principal in rupees"
    },
    "trader": {
      "enum": [
        "no",
        "yes",
        "mixed",
        "unsure"
      ],
      "type": "string",
      "description": "Is the supplier a retail/wholesale trader (NIC 45/46/47)?"
    },
    "category": {
      "enum": [
        "micro",
        "small",
        "medium",
        "none",
        "unsure"
      ],
      "type": "string",
      "description": "Supplier's MSME category at the time of the transaction"
    },
    "registered": {
      "enum": [
        "before-order",
        "after-order",
        "after-delivery",
        "unsure"
      ],
      "type": "string",
      "description": "When the supplier's Udyam registration was made, relative to the order"
    },
    "agreed_date": {
      "type": "string",
      "description": "Date in YYYY-MM-DD form. Payment date agreed in writing, if any"
    },
    "acceptance_date": {
      "type": "string",
      "description": "Date in YYYY-MM-DD form. The day the buyer accepted the goods or services (delivery day if no objection was raised)"
    }
  }
}
    arguments 55 lines
  • request_service unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "phone",
    "consent"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "The person's full name, as they gave it"
    },
    "need": {
      "type": "string",
      "description": "What they need done, in their words (required when no service_id)"
    },
    "email": {
      "type": "string",
      "description": "Email, only if the person gave one"
    },
    "notes": {
      "type": "string",
      "description": "Anything else they want us to know"
    },
    "phone": {
      "type": "string",
      "description": "The person's own 10-digit Indian mobile number, as they gave it"
    },
    "state": {
      "type": "string",
      "description": "Indian state or union territory"
    },
    "consent": {
      "type": "boolean",
      "description": "true only after the person explicitly agreed to be contacted"
    },
    "service_id": {
      "type": "string",
      "description": "An id from list_services, if the need matches one"
    },
    "entity_type": {
      "enum": [
        "individual",
        "proprietorship",
        "partnership",
        "llp",
        "company",
        "other"
      ],
      "type": "string",
      "description": "Who the work is for"
    }
  }
}
    arguments 54 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 7093983a070426e8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7093983a070426e8/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/7093983a070426e8/badge.svg)](https://brick.blue/agent/7093983a070426e8?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
100%

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.