Skip to content

quorum MCP server

io.github.Godzilla-lab/quorumGodzilla-labstreamable-httpv0.1.0Scanned

Market evidence with receipts: every claim resolves to a real stored record you can fetch back.

5 tools: 2 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 2 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 quorum MCP server can do

The quorum MCP server is published by the GitHub account Godzilla-lab. It has 5 tools. It can create or change data (2 tools: research_product and category_warmth), but cannot delete data. 3 tools only read.

1 tool brings in text other people can write (research_product).

The fixed checks matched 1 finding (tool-shadowing). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 0.1.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.

5 tools

Changes things 2Claude Code: ask
  • category_warmthHow much is already held for a category, and therefore whether asking about it is instant and free or slow and expensive.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 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.

    Annotations the server declares

    • title: Check category warmth
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • research_productStart collecting evidence on a product or topic from public sources.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Start a harvest
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • compare_formatsVideo versus static advertising for a category, computed from how long real ads actually ran rather than from opinion.No findings

    Why it is in this group

    • The name "compare_formats" says "compare": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Compare ad formats
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_receiptResolve receipt ids to the real records behind them.1 finding

    Why it is in this group

    • The name "get_receipt" says "get": a word for reading.

    Findings

    • Warn

      The input schema at properties.receiptIds.description contains "any other tool", wording about other tools or servers.

      Matched text

      inputSchema.properties.receiptIds.description: "Receipt ids, as returned by any other tool. Up to 50."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Resolve receipt ids
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_evidenceSearch the retained corpus for what people actually said about a product or topic.No findings

    Why it is in this group

    • The name "search_evidence" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search the evidence corpus
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • 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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
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 out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:58 UTC, unchanged since Oct 22, 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
2
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
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://quorum-api-j15n.onrender.com/mcp: tools/list returned 5 tools to an anonymous client, including research_product (write), category_warmth (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The input schema at properties.receiptIds.description contains "any other tool", wording about other tools or servers.

    Matched text

    inputSchema.properties.receiptIds.description: "Receipt ids, as returned by any other tool. Up to 50."

    What this check looks for

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 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http quorum https://quorum-api-j15n.onrender.com/mcp
claude mcp add --transport http quorum https://quorum-api-j15n.onrender.com/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__quorum__search_evidence",
      "mcp__quorum__get_receipt",
      "mcp__quorum__compare_formats"
    ],
    "ask": [
      "mcp__quorum__research_product",
      "mcp__quorum__category_warmth"
    ],
    "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 quorum. Review it before you use it.

Capability tags behind 1 rule
  • mcp__quorum__research_product untrusted-input

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/io.github.Godzilla-lab/quorum/verify?hash=408ae267f67df3ff4a02c222a333c593c015939dd5a09b222dfb01c606a22df7" | jq -e '.changed == false'

Pinned hash 408ae267f67d, from Nov 15, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.Godzilla-lab/quorum/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Godzilla-lab/quorum
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Godzilla-lab/quorum.svg)](https://radar.anlyon.com/servers/io.github.Godzilla-lab/quorum)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:16 UTC.

quorum MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the quorum MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the quorum MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the quorum MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the quorum MCP server have?

5 tools: 2 write, 3 read. research_product, category_warmth, search_evidence, get_receipt and compare_formats.

Does the quorum MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the quorum MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the quorum MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.