io.github.Godzilla-lab/quorum
REMOTE · QUORUM-API-J15N.ONRENDER.COM · SCANNED SEP 22
Market evidence with receipts: every claim resolves to a real stored record you can fetch back.
Available components
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 Security74
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 777 tokens (~155/item across 5 items; 5 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.Godzilla-lab/quorum MCP server?
io.github.Godzilla-lab/quorum is a hosted endpoint at https://quorum-api-j15n.onrender.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 · quorum-api-j15n.onrender.com
claude mcp add --transport http godzilla-lab-quorum 'https://quorum-api-j15n.onrender.com/mcp'
{
"mcpServers": {
"godzilla-lab-quorum": {
"url": "https://quorum-api-j15n.onrender.com/mcp"
}
}
} {
"servers": {
"godzilla-lab-quorum": {
"type": "http",
"url": "https://quorum-api-j15n.onrender.com/mcp"
}
}
} [mcp_servers.godzilla-lab-quorum] url = "https://quorum-api-j15n.onrender.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"godzilla-lab-quorum": {
"type": "remote",
"url": "https://quorum-api-j15n.onrender.com/mcp",
"enabled": true
}
}
} openclaw mcp add godzilla-lab-quorum --url 'https://quorum-api-j15n.onrender.com/mcp' --transport streamable-http
mcp_servers:
godzilla-lab-quorum:
url: "https://quorum-api-j15n.onrender.com/mcp" {
"McpServers": {
"godzilla-lab-quorum": {
"Transport": "http",
"Url": "https://quorum-api-j15n.onrender.com/mcp"
}
}
} assistant mcp add godzilla-lab-quorum -t streamable-http -u 'https://quorum-api-j15n.onrender.com/mcp'
{
"mcpServers": {
"godzilla-lab-quorum": {
"type": "http",
"url": "https://quorum-api-j15n.onrender.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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 593 → 777 ▼ functional
- New tool “research_product” functional
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 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.
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 22 Sept 2026 · Probed https://quorum-api-j15n.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of quorum-api-j15n.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.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://quorum-api-j15n.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://quorum-api-j15n.onrender.com/mcp | HTTPS enforced | 301 | https://quorum-api-j15n.onrender.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 →
category_warmth ~82
How much is already held for a category, and therefore whether asking about it is instant and free or slow and expensive. Check this BEFORE starting a report. With no category it lists what is held, so orient here instead of guessing slugs.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | The category, for example "running shoes". Omit to list every held category. |
No output schema declared.
No examples provided.
compare_formats ~52
Video versus static advertising for a category, computed from how long real ads actually ran rather than from opinion. Returns a verdict, its confidence, and the ads behind it.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | The product category. |
No output schema declared.
No examples provided.
get_receipt ~103
Resolve receipt ids to the real records behind them. This is how you CHECK a claim: if an id does not resolve, the claim citing it was not real. Takes one id or many. Long records are truncated with notice; pass full: true for complete text.
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | – | Return complete record text with no truncation. Default false. |
| receiptIds | array | yes | Receipt ids, as returned by any other tool. Up to 50. |
No output schema declared.
No examples provided.
research_product ~152
Start collecting evidence on a product or topic from public sources. RETURNS AT ONCE: the harvest runs in the background, the first records land within a minute, and a full run takes minutes. Then call `search_evidence` or `category_warmth` for the same subject after about 30 seconds and keep calling while the counts grow; stop when they stop. Every receipt returned along the way is already a real record. Calling this twice for one subject joins the same run rather than starting another.
| Name | Type | Req | Description |
|---|---|---|---|
| subject | string | yes | A product name, a topic, or a product URL. |
| terms | array | – | What to ask about: single concepts like "sizing", "durability". Optional. |
No output schema declared.
No examples provided.
search_evidence ~298
Search the retained corpus for what people actually said about a product or topic. Returns how many independent records exist, across how many channels, whether that clears the corroboration threshold, and the loudest few quotes with their receipt ids. Costs nothing and touches no network.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Optional. ISO date (2026-01-31): only records their authors wrote on or after it. Undated records sit inside no window. |
| before | string | – | Optional. ISO date: only records written on or before it. |
| category | string | – | Optional. Narrow to one product category. |
| excludeSources | array | – | Optional. Drop these sources, e.g. ["sec-edgar", "cpsc"] to drop the institutional records from a consumer question. |
| minChannels | number | – | Optional. Demand at least this many distinct channels for a finding verdict. Can only demote. |
| phrase | boolean | – | Optional. Match the words as one ordered phrase, no any word fallback. Build phrases from content words. |
| query | string | yes | What to look for: "sizing", "battery life", "runs small". |
| sourceClasses | array | – | Optional. Filter by what kind of speaker: consumer_voice (reddit, reviews...), practitioner (github...), institutional (regulators, filings). |
| sources | array | – | Optional. Only these sources (reddit, appstore, sec-edgar...). |
No output schema declared.
No examples provided.
What is the io.github.Godzilla-lab/quorum MCP server?
io.github.Godzilla-lab/quorum is an MCP server listed in the public MCP registry as io.github.Godzilla-lab/quorum. Market evidence with receipts: every claim resolves to a real stored record you can fetch back. This page covers its hosted endpoint (https://quorum-api-j15n.onrender.com/mcp).
Is the io.github.Godzilla-lab/quorum MCP server safe to use?
io.github.Godzilla-lab/quorum scores 82 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 io.github.Godzilla-lab/quorum MCP server expose?
io.github.Godzilla-lab/quorum exposes 5 tools: research_product, search_evidence, get_receipt, category_warmth, compare_formats. Their descriptions and schemas cost roughly 687 tokens of context every time the server is loaded.
Does the io.github.Godzilla-lab/quorum MCP server require authentication?
No. We connected to io.github.Godzilla-lab/quorum without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.Godzilla-lab/quorum MCP server still maintained?
io.github.Godzilla-lab/quorum is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.