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 Ration

PYPI · FORGINGSTACK-RATION

One quota pool, many agents, no overruns.

+6 this week 67 Trust /100

Last scanned (12 hours ago)

Scores higher than 60% of PyPI servers

Category Workflow Automation

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 Security100
  • No malware found by supply-chain analysis.Pass
  • 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 Usability63
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 330 tokens (~41/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_pool" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 8 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
What we tested

Checks we ran (16)

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

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.

  • 20 Nov 26 +21
    • Malware scan: unverified → pass ▲ security
    • Stability: unverified → 0.40 ▲ functional
  • 18 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 17 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 14 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 13 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
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-ration@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 · 8 exposed · ~330 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_pool ~77

Create a token-bucket quota pool shared by many agents. Costs 1 credit. Returns the pool with its starting availability.

NameTypeReqDescription
burst_unitsintegeryes–
capacity_unitsintegeryes–
namestringyes–
per_agent_cap_unitsintegeryes–
refill_units_per_minutenumberyes–

No output schema declared.

No examples provided.

delete_pool ~31

Delete a pool and its draws. No billing credit is charged or refunded.

NameTypeReqDescription
pool_idintegeryes–

No output schema declared.

No examples provided.

draw ~85

Draw units from a pool for one agent. Returns allowed or denied, a reason, and a hash-chained receipt. Costs 1 credit per draw call, allowed or denied; an idempotency key replay is free.

NameTypeReqDescription
agent_idstringyes–
idempotency_keystring––
pool_idintegeryes–
unitsintegeryes–

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_pool ~32

Fetch one pool by id, with its current available units (refill applied).

NameTypeReqDescription
pool_idintegeryes–

No output schema declared.

No examples provided.

get_receipt ~25

Fetch a past draw receipt by id.

NameTypeReqDescription
receipt_idintegeryes–

No output schema declared.

No examples provided.

list_pools ~19

List all pools owned by the configured API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

topup_pool ~43

Add units to a pool, clamped at capacity. Free — no billing credit is charged.

NameTypeReqDescription
pool_idintegeryes–
unitsintegeryes–

No output schema declared.

No examples provided.

Install

How do I install the ForgingStack Ration MCP server?

ForgingStack Ration runs locally as a PyPI package, launched with uvx forgingstack-ration. 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-ration

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

What is the ForgingStack Ration MCP server?

ForgingStack Ration is an MCP server listed in the public MCP registry as io.github.jdkabattles/forgingstack-ration. One quota pool, many agents, no overruns. This page covers its PyPI package (forgingstack-ration).

Is the ForgingStack Ration MCP server safe to use?

ForgingStack Ration scores 67 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 Ration MCP server expose?

ForgingStack Ration exposes 8 tools: create_pool, draw, get_pool, list_pools, topup_pool, and 3 more. Their descriptions and schemas cost roughly 330 tokens of context every time the server is loaded.

Is the ForgingStack Ration MCP server still maintained?

ForgingStack Ration 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 Ration MCP server under?

ForgingStack Ration 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 Ration MCP server?

VerifyMCP ran 16 checks on ForgingStack Ration, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.