Secure MCP access to Big Red Cloud accounting data, workflows, help and training.
Finance & Cryptov1.4.0streamable-httpred.bigredcloud.com repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 176ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo Red@1.4.0 |
| tooling | 35 / 35 | tools/list OK: 157 tools e.g. "brc_start_company_connection"; 157/157 described, 157/157 fully-typed schemas, median description 362 chars |
| latency | 10 / 10 | initialize round-trip 176ms |
| provenance | 15 / 15 | description present; repository linked; version 1.4.0; namespace io.github.BigRedCloud matches endpoint/repo |
Score 100/100 · latency 176ms · 157 tools · protocol access: open ⓘ
Security, data integrity, citation quality, and advertised claims are measured separately from protocol uptime. Missing evidence is marked unverified, never converted into a pass.
| Dimension | Metric | Status | Evidence | Source |
|---|---|---|---|---|
| citation_quality | citation_capability_advertised | unverified | Metadata/tool descriptions advertise citation or evidence capability: Cross-reference brc_list_vat_categories to group rates by Sales vs Purchase category before choosing | _setup_config Gets full BRC company setup configuration, including general details, financial year, reference settings, and processing options | Requires a reference when the company is configured for manual purchase references; otherwise prefer brc_create_purchase_gen_ref. No response-level citation benchmark has verified this claim yet. | live_probe |
| security | sensitive_capabilities_declared | concern | 4 discovered tool(s) advertise potentially state-changing or privileged capabilities. Tool names: brc_get_company_api_key_status, brc_get_deployment_policy, brc_open_edu_admin, brc_list_audit_log. Classification is description-based and does not prove exploitability. Observed value: brc_get_company_api_key_status, brc_get_deployment_policy, brc_open_edu_admin, brc_list_audit_log Sample: n=4 | live_probe |
| security | authentication_boundary | observed | Live protocol probe observed auth_state=open. This describes discovery/access behavior; it is not by itself a vulnerability finding. Observed value: open | live_probe |
Machine-readable receipt: /api/trust/io.github.BigRedCloud/red-mcp-server.json
Claude Code:
claude mcp add --transport http red-mcp-server https://red.bigredcloud.com/mcp
Generic MCP client config:
{ "mcpServers": { "red-mcp-server": { "type": "http", "url": "https://red.bigredcloud.com/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/io.github.BigRedCloud/red-mcp-server · referral link https://mcpqueen.com/go/io.github.BigRedCloud/red-mcp-server (counts as “routed via the queen”).
Live operational-grade badge, re-probed continuously — not a security or data-quality certification. Put it in your README and link to the complete receipt:
[](https://mcpqueen.com/s/io.github.BigRedCloud/red-mcp-server)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-30 13:31 | A | 100 | 176ms |