Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Nothing to run from here
Supprecord is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
18
tools declared
local
runs on your machine
—
downloads a day
What it does
Dated formula history, confirmed changes, and evidence for U.S. pre-workout supplements.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user supprecord-mcp '--' npx -y @reneturcios/supprecord mcp
# 2 — ask your agent for something these tools do
# record.search, products.resolve, products.get and 15 more
Supprecord costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CLAll 380 servers
CloudCorpRecords380 servers
28 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Supprecord as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user supprecord-mcp '--' npx -y @reneturcios/supprecord mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Answer one specific, bounded question from FormulaSignal's covered pre-workout Record. When to use: Use for a single natural-language question about a covered product: what it declares now, whether it changed, what it costs per serving, or which covered products meet one stated numeric condition.…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | One plain-language question about covered pre-workout products, for example "How much caffeine is in C4 Original?". Ask once; rewording the same question returns the same answer and costs quota. |
Resolve a brand, product name, or alias to one canonical covered product. When to use: Call this first whenever you hold a user-supplied product name and need the canonical product_id every other capability takes. What it cannot provide: It never guesses. An ambiguous or generic name returns the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| identifier | string | yes | A brand, product name or alias as the user wrote it, for example "C4 Original". |
Return the controlled current Record for one covered product: identity, serving configuration, declared ingredients, captured price context, and freshness. When to use: Use when you need what a product declares right now, with the dates and limitations attached. What it cannot provide: It…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | string | yes | A canonical FormulaSignal product id, such as the product_id returned by products.resolve. Not a display name. |
Return the controlled historical timeline for one covered product, with each state classified by what it can actually support. When to use: Use to find out whether a product has changed, how deep the recoverable history is, and which states are comparable to each other. What it cannot provide:…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | string | yes | A canonical FormulaSignal product id, such as the product_id returned by products.resolve. Not a display name. |
Explain one approved FormulaSignal Signal: a confirmed, reviewed change between two comparable product states. When to use: Use when a product record or history response named a signal_id and you need the before state, the after state, the observation window, and the evidence. What it cannot…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| signal_id | string | yes | A Signal id, as named by a product record, a formula history, or signals.list. |
Return approved FormulaSignal Signals in release order, newest first, for incremental polling. When to use: Use to keep a system in step with the Record. Pass since with the release date you last saw, or follow next_cursor, and filter by product, brand, dimension or category. What it cannot…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | no | Only Signals released on or after this date, YYYY-MM-DD. Pass the newest release date you have already seen to poll for what is new. |
| until | string | no | Only Signals released on or before this date, YYYY-MM-DD. |
| product_id | string | no | Only Signals for this canonical product id. |
| brand | string | no | Only Signals for this brand, matched on the full brand name, case-insensitive. |
| dimension | string | no | Only Signals of this kind of change: FORMULA, FORMULA_DOSE, SERVING, PRICE, CLAIMS, CERTIFICATION, LIFECYCLE or OTHER. |
| category | string | no | Only Signals whose change category matches this value, case-insensitive, as shown in a Signal's change.category field. |
| limit | integer | no | Signals per page, 1 to 25. Defaults to the plan's page size. |
| cursor | string | no | The next_cursor value from the previous page. Omit it for the first page. |
Compare two or three covered products on consistent FormulaSignal criteria. When to use: Use when a user asks how covered products differ on formula, serving economics, stimulant load, or record depth. What it cannot provide: It returns no overall winner and no suitability judgement. A product…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_ids | array | yes | Two or three canonical product ids to compare. Resolve names with products.resolve first. |
Return the captured commercial facts and the deterministic price arithmetic for one covered product. When to use: Use for package price, price basis, serving count, price per serving, and the date each was observed. What it cannot provide: It never calls an observed price a list price unless the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | string | yes | A canonical FormulaSignal product id, such as the product_id returned by products.resolve. Not a display name. |
Return the dose range used in the selected evidence set for named ingredients, with the citation and its limitations. When to use: Use to place a declared amount against published work. Pass ingredient ids, or a product_id to read the ingredients that product declares. What it cannot provide: A…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ingredient_ids | array | no | Up to five canonical ingredient ids. Pass these or product_id, not both. |
| product_id | string | no | A canonical product id, to read the ingredients that product declares. Pass this or ingredient_ids, not both. |
Return regulatory records and documented cautions for named ingredients, each carrying the class of record it actually is. When to use: Use when you need to know what filings, advisories, label warnings, interactions, or enforcement actions FormulaSignal holds for an ingredient. What it cannot…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ingredient_ids | array | no | Up to five canonical ingredient ids. Pass these or product_id, not both. |
| product_id | string | no | A canonical product id, to read the ingredients that product declares. Pass this or ingredient_ids, not both. |
Return a bounded summary of approved Signals and coverage state across the covered pre-workout set for a date window. When to use: Use for 'what changed in the category recently'. Pass from and to dates; the window is capped and the page size is capped. What it cannot provide: It is not an…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | no | Start of the window, YYYY-MM-DD. Defaults to the widest window the plan allows before to. |
| to | string | no | End of the window, YYYY-MM-DD. Defaults to today (UTC). |
| limit | integer | no | Signals per page, 1 to 25. Defaults to the plan's page size. |
| cursor | string | no | The next_cursor value from the previous page. Omit it for the first page. |
List the published Category Ledger editions: period, status, data-as-of date and the count released in each. When to use: Call this first to find which edition covers a period, then fetch that edition by id. What it cannot provide: It returns no figures from inside an edition and no product…
No parameter schema on file.
Return one Category Ledger edition: the executive summary, confirmed changes released in the period, category benchmarks with their cohorts, serving economics, the product comparison, and the limitations. When to use: Use when an agent needs the month's category intelligence with every…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| edition_id | string | yes | A Category Ledger edition id, as returned by ledger.list. |
Return the watchlist of the one Founding Pro account this key is bound to, with each product's monitoring state. When to use: Use to answer what a person is watching, when each product was last read, when the next check is due, and whether anything is currently unreadable. What it cannot…
No parameter schema on file.
Add one covered product to the bound account's watchlist. When to use: Use when a person asks to start watching a product. Resolve the product first if you were given a name rather than an id. What it cannot provide: It cannot add a product outside the covered set, exceed the account's watch…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | string | yes | The canonical product id to start watching. Resolve a name with products.resolve first. |
Remove one product from the bound account's watchlist. When to use: Use when a person asks to stop watching a product. Future alerts stop; everything already delivered stays. What it cannot provide: It cannot delete an account, cancel a subscription, or remove history. Removing a watch never…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | string | yes | The canonical product id to stop watching. |
Return the monitoring receipt for one period: valid checks, attempts that returned nothing, recoveries, and confirmed Signals. When to use: Use to answer whether anything a person watches changed in a period, and what monitoring did in the period whether or not anything did. What it cannot…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| period | string | no | A calendar month, YYYY-MM. Defaults to the current month (UTC). |
Return the public Record version, the methodology version, the supported category, coverage counts, and source freshness. When to use: Call this to state which version of FormulaSignal intelligence an answer came from, or to detect that coverage has moved. What it cannot provide: It exposes no…
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Supprecord or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.1.0 · scanned 5 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest052881460777c95e44b19c3296e82cf1c165e2bfa3e425d23794bc9cf59b94c8
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest052881460777c95e
Scanned2026-11-05
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Supprecord can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.