Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ForgingStack Quorum

PYPI · FORGINGSTACK-QUORUM

Before an agent acts alone, get the quorum. One proposal, N approvals, one receipt.

−15 this week 50 Trust /100

Last scanned (13 hours ago)

Scores higher than 48% of PyPI servers

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 241 tokens (~60/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 71% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (14)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 20 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 11 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 10 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 8 Nov 26 50

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed pypi/forgingstack-quorum@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~241 tokens

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 →

Tool Tokens
create_proposal ~162

Propose an action for quorum approval. Each approver gets a one-time emailed link; when the required number approve, the proposal is approved and a hash-chained receipt is issued. Costs 1 credit per proposal; approvals are free.

NameTypeReqDescription
actionstringyesThe action to approve, non-empty, at most 500 characters.
approversarrayyesEmail addresses of the approvers (at least as many as required_approvals).
expires_atstringyesProposal expiry, ISO 8601, must be in the future.
mandate_refstring–Optional reference to a mandate (at most 500 characters).
required_approvalsintegeryesHow many approvals are needed for quorum (1 or more).

No output schema declared.

No examples provided.

get_credits ~18

Remaining credit balance for the configured API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_proposal ~36

Fetch a proposal by id, with its approval state and, once approved, its receipt id.

NameTypeReqDescription
proposal_idstringyes–

No output schema declared.

No examples provided.

get_receipt ~25

Fetch a past quorum receipt by id.

NameTypeReqDescription
receipt_idintegeryes–

No output schema declared.

No examples provided.

Install

How do I install the ForgingStack Quorum MCP server?

ForgingStack Quorum runs locally as a PyPI package, launched with uvx forgingstack-quorum. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · forgingstack-quorum

# add to Claude Code
claude mcp add jdkabattles-forgingstack-quorum -- uvx forgingstack-quorum
Common questions

What is the ForgingStack Quorum MCP server?

ForgingStack Quorum is an MCP server listed in the public MCP registry as io.github.jdkabattles/forgingstack-quorum. Before an agent acts alone, get the quorum. One proposal, N approvals, one receipt. This page covers its PyPI package (forgingstack-quorum).

Is the ForgingStack Quorum MCP server safe to use?

ForgingStack Quorum scores 50 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 ForgingStack Quorum MCP server expose?

ForgingStack Quorum exposes 4 tools: create_proposal, get_proposal, get_credits, get_receipt. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.

Is the ForgingStack Quorum MCP server still maintained?

ForgingStack Quorum is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the ForgingStack Quorum MCP server under?

ForgingStack Quorum declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the ForgingStack Quorum MCP server?

VerifyMCP ran 14 checks on ForgingStack Quorum, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about ForgingStack Quorum: Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.