Red by Big Red Cloud
REMOTE · RED.BIGREDCLOUD.COM · SCANNED SEP 29
Secure MCP access to Big Red Cloud accounting data, workflows, help and training.
Available components
Recent critical change
Authorization (21 Aug 2026). See the changelog before you install this server.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (brc_clear_company_api_key). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability71
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 48750 tokens (~300/item across 162 items; 159 tools + 3 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Tool Safety50
- Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "Do not tell the user", at byte 6066 of that field. See how to fix → Fail
- All 20 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 161 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Red by Big Red Cloud MCP server?
Red by Big Red Cloud is a hosted endpoint at https://red.bigredcloud.com/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 · red.bigredcloud.com
claude mcp add --transport http bigredcloud-red-mcp-server 'https://red.bigredcloud.com/mcp'
{
"mcpServers": {
"bigredcloud-red-mcp-server": {
"url": "https://red.bigredcloud.com/mcp"
}
}
} {
"servers": {
"bigredcloud-red-mcp-server": {
"type": "http",
"url": "https://red.bigredcloud.com/mcp"
}
}
} [mcp_servers.bigredcloud-red-mcp-server] url = "https://red.bigredcloud.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bigredcloud-red-mcp-server": {
"type": "remote",
"url": "https://red.bigredcloud.com/mcp",
"enabled": true
}
}
} openclaw mcp add bigredcloud-red-mcp-server --url 'https://red.bigredcloud.com/mcp' --transport streamable-http
mcp_servers:
bigredcloud-red-mcp-server:
url: "https://red.bigredcloud.com/mcp" {
"McpServers": {
"bigredcloud-red-mcp-server": {
"Transport": "http",
"Url": "https://red.bigredcloud.com/mcp"
}
}
} assistant mcp add bigredcloud-red-mcp-server -t streamable-http -u 'https://red.bigredcloud.com/mcp'
{
"mcpServers": {
"bigredcloud-red-mcp-server": {
"type": "http",
"url": "https://red.bigredcloud.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 29 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 26 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 25 Sept 26 −14
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 23 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 22 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 29 Sept 2026 · Probed https://red.bigredcloud.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=red.bigredcloud.com | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 22 Jun 2026 | 22 Dec 2026 | RSA 2048 | SHA256-RSA | 6c07bac9103762755b9c617f2187113 |
| SANs: red.bigredcloud.com | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of red.bigredcloud.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| bigredcloud.com. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://red.bigredcloud.com/mcp | Verified | 200 | |
| http (plaintext) | http://red.bigredcloud.com/mcp | HTTPS enforced | 301 | https://red.bigredcloud.com/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 →
brc_update_cash_payment ~412
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| companyName | string | yes | – |
| confirmWrite | boolean | – | – |
| connectionRef | string | – | – |
| id | – | yes | – |
| payload | object | – | – |
| routeToken | string | yes | – |
| updates | object | – | – |
No output schema declared.
No examples provided.
brc_update_cash_receipt ~350
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| companyName | string | yes | – |
| confirmWrite | boolean | – | – |
| connectionRef | string | – | – |
| id | – | yes | – |
| payload | object | – | – |
| routeToken | string | yes | – |
| updates | object | – | – |
No output schema declared.
No examples provided.
brc_update_customer ~346
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| companyName | string | yes | – |
| confirmWrite | boolean | – | – |
| connectionRef | string | – | – |
| id | – | yes | – |
| payload | object | – | – |
| routeToken | string | yes | – |
| updates | object | – | – |
No output schema declared.
No examples provided.
brc_update_nominal_journal_batch ~396
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| accountTransactions | array | yes | – |
| bookTranTypeId | integer | – | – |
| companyName | string | yes | – |
| confirmWrite | boolean | – | – |
| connectionRef | string | – | – |
| entryDate | string | yes | – |
| id | integer | yes | – |
| procDate | string | yes | – |
| routeToken | string | yes | – |
| timestamp | string | yes | – |
| total | number | yes | – |
No output schema declared.
No examples provided.
brc_update_payment ~346
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| companyName | string | yes | – |
| confirmWrite | boolean | – | – |
| connectionRef | string | – | – |
| id | – | yes | – |
| payload | object | – | – |
| routeToken | string | yes | – |
| updates | object | – | – |
No output schema declared.
No examples provided.
brc_update_prepayment ~422
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| acCode | string | yes | – |
| companyName | string | yes | – |
| confirmWrite | boolean | – | – |
| connectionRef | string | – | – |
| entryDate | string | yes | – |
| firstDetail | string | – | – |
| id | integer | yes | – |
| procDate | string | yes | – |
| reference | string | yes | – |
| routeToken | string | yes | – |
| secondDetail | string | – | – |
| timestamp | string | yes | – |
| total | number | yes | – |
No output schema declared.
No examples provided.
brc_update_product ~346
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| companyName | string | yes | – |
| confirmWrite | boolean | – | – |
| connectionRef | string | – | – |
| id | – | yes | – |
| payload | object | – | – |
| routeToken | string | yes | – |
| updates | object | – | – |
No output schema declared.
No examples provided.
brc_update_purchase ~477
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| acCode | string | – | – |
| accountCode | string | – | – |
| analysisCategoryId | integer | – | – |
| bookTranTypeId | integer | – | – |
| companyName | string | yes | – |
| confirmWrite | boolean | – | – |
| connectionRef | string | – | – |
| description | string | – | – |
| entryDate | string | – | – |
| id | – | yes | – |
| netAmount | number | – | – |
| note | string | – | – |
| procDate | string | – | – |
| routeToken | string | yes | – |
| supplierId | string | – | – |
| vatPercentage | number | – | – |
| vatRateId | integer | – | – |
No output schema declared.
No examples provided.
brc_update_quote ~452
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| companyName | string | yes | – |
| confirmWrite | boolean | – | – |
| connectionRef | string | – | – |
| id | – | yes | – |
| reference | string | – | – |
| routeToken | string | yes | – |
No output schema declared.
No examples provided.
brc_update_sales_credit_note ~497
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| companyName | string | yes | – |
| confirmWrite | boolean | – | – |
| connectionRef | string | – | – |
| customerId | integer | – | – |
| details | string | – | – |
| entryDate | string | – | – |
| id | – | yes | – |
| note | string | – | – |
| ourReference | string | – | – |
| procDate | string | – | – |
| productTrans | array | – | – |
| reference | string | – | – |
| routeToken | string | yes | – |
| saleRepId | integer | – | – |
| total | number | – | – |
| totalNet | number | – | – |
| totalVAT | number | – | – |
| vatTypeId | integer | – | – |
| yourReference | string | – | – |
No output schema declared.
No examples provided.
brc_update_sales_entry ~736
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| acCode | string | – | – |
| acEntries | array | – | – |
| bookTranTypeId | integer | – | – |
| companyName | string | yes | – |
| confirmWrite | boolean | – | – |
| connectionRef | string | – | – |
| customerId | integer | – | – |
| details | string | – | – |
| entryDate | string | – | – |
| id | – | yes | – |
| note | string | – | – |
| procDate | string | – | – |
| reference | string | – | – |
| routeToken | string | yes | – |
| total | number | – | – |
| totalNet | number | – | – |
| totalVAT | number | – | – |
| vatEntries | array | – | – |
| vatTypeId | integer | – | – |
No output schema declared.
No examples provided.
brc_update_sales_invoice ~618
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bookTranTypeId | integer | – | – |
| companyName | string | yes | – |
| confirmWrite | boolean | – | – |
| connectionRef | string | – | – |
| customerId | integer | – | – |
| details | string | – | – |
| entryDate | string | – | – |
| id | – | yes | – |
| note | string | – | – |
| ourReference | string | – | – |
| procDate | string | – | – |
| productTrans | array | – | – |
| reference | string | – | – |
| routeToken | string | yes | – |
| saleRepId | integer | – | – |
| total | number | – | – |
| totalNet | number | – | – |
| totalVAT | number | – | – |
| vatTypeId | integer | – | – |
| yourReference | string | – | – |
No output schema declared.
No examples provided.
brc_update_sales_rep ~340
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | – |
| companyName | string | yes | – |
| confirmWrite | boolean | – | – |
| connectionRef | string | – | – |
| id | – | yes | – |
| name | string | – | – |
| routeToken | string | yes | – |
No output schema declared.
No examples provided.
brc_update_supplier ~346
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| companyName | string | yes | – |
| confirmWrite | boolean | – | – |
| connectionRef | string | – | – |
| id | – | yes | – |
| payload | object | – | – |
| routeToken | string | yes | – |
| updates | object | – | – |
No output schema declared.
No examples provided.
brc_validate_transaction_date ~148
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| companyName | string | yes | – |
| connectionRef | string | – | – |
| transactionDate | string | yes | – |
No output schema declared.
No examples provided.
What is the Red by Big Red Cloud MCP server?
Red by Big Red Cloud is an MCP server listed in the public MCP registry as io.github.BigRedCloud/red-mcp-server. Secure MCP access to Big Red Cloud accounting data, workflows, help and training. This page covers its hosted endpoint (https://red.bigredcloud.com/mcp).
Is the Red by Big Red Cloud MCP server safe to use?
Red by Big Red Cloud scores 62 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.
Does the Red by Big Red Cloud MCP server require authentication?
No. We connected to Red by Big Red Cloud without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Red by Big Red Cloud MCP server still maintained?
Red by Big Red Cloud is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.