compliance MCP server
in.co.buildwright/compliancebuildwright.co.instreamable-httpv1.0.0Scanned
Indian business compliance answers: MCA late fees, filing calendar, cheque bounce, MSME interest.
8 tools: 1 do something that can't be undone, 5 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the compliance MCP server can do
The compliance MCP server is published by buildwright.co.in, a domain the MCP Registry verified. It has 8 tools. It can do things that cannot be undone, such as sending, paying or publishing (request_service) and create or change data (5 tools: mca_late_fee, compliance_calendar, cheque_bounce_timer, msme_interest and 1 more), but cannot delete data. 2 tools only read.
1 tool reads private data (list_free_tools); 1 tool brings in text other people can write (request_service); 1 tool can send data out of your system (request_service). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 8, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Can't be undone 1Claude Code: ask
request_serviceSend the person's request to BuildWright so a person calls them back.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "request_service" says "request": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Changes things 5Claude Code: ask
cheque_bounce_timerThe 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 t…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
compliance_calendarThe 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(…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
engage_buildwrightHow to have a filing, document or compliance task done by BuildWright's people: contact routes and what the firm handles.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
mca_late_feeThe 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
msme_interestCompound 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-cover…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
Only reads 2Show 2 read-only tools
list_free_toolsThe free Indian compliance tools and document templates BuildWright publishes, with URLs, for anything this server's tools do not compute.Reads private dataNo findings
Why it is in this group
- The name "list_free_tools" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "document": it reads documents.
Description, as the server wrote it The free Indian compliance tools and document templates BuildWright publishes, with URLs, for anything this server's tools do not compute.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_servicesBuildWright's SEBI adviser services with our fee in rupees, what is included, and the service page, for information.No findings
Why it is in this group
- The name "list_services" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
1 path in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__compliance__request_service"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 16, 2026, 14:21 UTC, unchanged since Nov 9, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://buildwright.co.in/api/mcp: tools/list returned 9 tools to an anonymous client, including request_service (irreversible), mca_late_fee (write), compliance_calendar (write), cheque_bounce_timer (write), msme_interest (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http compliance https://buildwright.co.in/api/mcpclaude mcp add --transport http compliance https://buildwright.co.in/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__compliance__list_free_tools",
"mcp__compliance__list_services"
],
"ask": [
"mcp__compliance__mca_late_fee",
"mcp__compliance__compliance_calendar",
"mcp__compliance__cheque_bounce_timer",
"mcp__compliance__msme_interest",
"mcp__compliance__engage_buildwright",
"mcp__compliance__request_service"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as compliance. Review it before you use it.
Capability tags behind 2 rules
- mcp__compliance__list_free_tools private-data
- mcp__compliance__request_service untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/in.co.buildwright/compliance/verify?hash=67ca3e104ee80ba12648439f55c80764b264d9094c1a024c4241d128c4c42211" | jq -e '.changed == false'Pinned hash 67ca3e104ee8, from Nov 8, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/in.co.buildwright/compliance/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/in.co.buildwright/compliance)Source: MCP Registry. Synced Nov 8, 2026, 07:17 UTC.
compliance MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the compliance MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the compliance MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the compliance MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: request_service.
What tools does the compliance MCP server have?
- 8 tools: 1 irreversible, 5 write, 2 read. request_service, mca_late_fee, compliance_calendar, cheque_bounce_timer, msme_interest, engage_buildwright, list_free_tools and list_services.
Does the compliance MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the compliance MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): request_service.
Has the compliance MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.