io.github.smeet666/mcp-supertoinette
NPM · MCP-SUPERTOINETTE · 2 COMPONENTS · SCANNED SEP 20
Read Supertoinette recipes and rescale their quantities honestly. No API key.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to smeet666/mcp-supertoinette). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1693 tokens (~282/item across 6 items; 6 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 Management80
- Stability observed for 24 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.smeet666/mcp-supertoinette server?
io.github.smeet666/mcp-supertoinette runs locally as an npm package, launched with npx -y mcp-supertoinette. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-supertoinette
claude mcp add smeet666-mcp-supertoinette -- npx -y mcp-supertoinette
{
"mcpServers": {
"smeet666-mcp-supertoinette": {
"command": "npx",
"args": [
"-y",
"mcp-supertoinette"
]
}
}
} {
"servers": {
"smeet666-mcp-supertoinette": {
"command": "npx",
"args": [
"-y",
"mcp-supertoinette"
]
}
}
} codex mcp add smeet666-mcp-supertoinette -- npx -y mcp-supertoinette
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"smeet666-mcp-supertoinette": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-supertoinette"
],
"enabled": true
}
}
} openclaw mcp add smeet666-mcp-supertoinette --command npx --arg -y --arg mcp-supertoinette
mcp_servers:
smeet666-mcp-supertoinette:
command: "npx"
args: ["-y", "mcp-supertoinette"] {
"McpServers": {
"smeet666-mcp-supertoinette": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-supertoinette"
]
}
}
} assistant mcp add smeet666-mcp-supertoinette -t stdio -c npx -a -y mcp-supertoinette
{
"mcpServers": {
"smeet666-mcp-supertoinette": {
"command": "npx",
"args": [
"-y",
"mcp-supertoinette"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 1.0.2 → 1.1.0 functional
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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 20 Sept 2026 · Analysed npm/mcp-supertoinette@1.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | smeet666/mcp-supertoinette |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/smeet666/mcp-supertoinette/.github/workflows/publish.yml@refs/tags/v1.1.0 |
| Rekor log index | 2786822812 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:137cb6766f02ff9a8afc0c0f5b48fe6707610b2e2505dad643ec0ab38cee1a1d85b6e9a4cff55711a11c5bfe1bbb21923dc3566de8cca19f112390f56 |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
browse_recipes Read one category's recipes ~204
Read the recipes of one Supertoinette category, page by page. The category is a number and a name together, taken from list_categories or from the 'tags' of a recipe, and never assembled by hand. Each row carries the identifier get_recipe reads a recipe with, plus the difficulty and the total time the site prints beside it. The site publishes no total, so 'last_page' says how far the listing runs.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | The category to read, as a number and a name together, such as '107/recettes-desserts'. Take one from list_categories or from a recipe's tags. |
| limit | integer | – | Rows to render, 20 by default. The site serves at most 30 to a page, and 'rows_published' always states what the page held. |
| page | integer | – | Which page to read, 1 by default. 'last_page' says how far the listing runs. |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | The category that was read. |
| last_page | integer | yes | The highest page the site links to from this one. |
| notes | array | yes | – |
| page | integer | yes | The page these rows were read from. |
| result_count | integer | yes | Rows rendered here. |
| results | array | yes | – |
| rows_published | integer | yes | Rows the page held, before any were rendered. |
| source | string | yes | – |
| title | string|null | yes | The site's own heading for the category. |
| total_available | null | yes | Supertoinette prints no total on a category page, so there is none to report. |
| url | string | yes | The page these rows were read from. |
No examples provided.
get_recipe Read one recipe ~189
Read one recipe on Supertoinette by its identifier, which is the number in its address: 4210 in /recette/4210/veloute-de-gaverole.html. Returns the ingredients, the steps, the times, the difficulty and the cost the site publishes. A time the site does not publish comes back as null rather than as zero. Pass 'servings' to rescale the quantities: each line then says whether the arithmetic landed exactly, or had to move to stay an amount a kitchen can measure out.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The number in the recipe's address, such as '4210'. Search for a dish when you do not have one. |
| servings | integer | – | Rescale the quantities to this many. Left out, they come back as the site published them. It is refused when the site's own wording carries no number to scale from. |
| Name | Type | Req | Description |
|---|---|---|---|
| author | string|null | yes | – |
| category | string|null | yes | – |
| cook_minutes | – | yes | Null when the site publishes no cooking time. |
| cost_level | – | yes | The site's own wording, with the scale it draws the symbols on. |
| description | string|null | yes | – |
| difficulty | – | yes | The site's own wording. It publishes no scale for this, so none is stated. |
| faq | array | yes | – |
| id | string | yes | – |
| images | array | yes | – |
| ingredient_count | integer | yes | Lines rendered, headings included. |
| ingredient_sheets | array | yes | – |
| ingredients | array | yes | – |
| intro | string|null | yes | The prose the page prints above the steps. |
| notes | array | yes | – |
| nutrition | null | yes | Supertoinette publishes none. |
| prep_minutes | – | yes | Null when the site publishes no preparation time. |
| published_at | string|null | yes | – |
| rating | – | yes | – |
| rest_minutes | – | yes | Resting time, which the page prints as 'Pause'. |
| source | string | yes | – |
| steps | array | yes | – |
| tags | array | yes | – |
| title | string | yes | The title with the pictogram the site opens it with taken off. |
| title_as_published | string | yes | The title exactly as the site wrote it. |
| total_minutes | – | yes | – |
| url | string | yes | The public page. Show this when citing the recipe. |
| yield | object | yes | How many the recipe was written for, and how many were asked for. |
No examples provided.
get_wine_pairings Read the wines ranked for a dish ~155
Read the wines Supertoinette ranks for one dish, given the number in its address as 'id'. Each wine comes with the site's own wording for how well it goes, from 'Bon accord' to 'Accord parfait'. Called with 'page' instead, it reads one page of the alphabetical index of dishes, which is where the identifiers come from: the index runs alphabetically, so a dish beginning with a late letter sits on a late page.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | The number in a dish's address, such as '10'. Give this or 'page'. |
| page | integer | – | Read one page of the alphabetical index of dishes instead of one dish. Give this or 'id'. |
| Name | Type | Req | Description |
|---|---|---|---|
| dish | – | yes | The wines ranked for one dish, when 'id' was given. |
| index | – | yes | One page of the index of dishes, when 'page' was given. |
| kind | string | yes | Which of the two answers arrived. The other field is null. |
| notes | array | yes | – |
| source | string | yes | – |
No examples provided.
list_categories List the categories recipes are browsed by ~119
List the categories Supertoinette browses its recipes by. Each entry carries the token that opens its listing with browse_recipes, and 'listed_in' says where the site printed it: its footer holds the kinds of dish, its menu holds the ways of cooking and the seasons. Never build a token by hand, because the site answers a number paired with the wrong name with a page it does not hold. These two lists are not every category the site files recipes under: a recipe's own tags open onto hundreds more that neither list publishes.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | – |
| category_count | integer | yes | Entries the two lists hold. |
| notes | array | yes | – |
| source | string | yes | – |
| url | string | yes | The page these categories were read from. |
No examples provided.
scale_ingredients Rescale a list of ingredients ~182
Rescale a list of French ingredient lines, offline. Give either 'factor', or 'from_servings' and 'to_servings' together. Each line comes back with what was done to it: 'scaled' when the arithmetic landed exactly, 'rounded' when the value had to move to stay something a kitchen can measure out, and 'unscaled' when the line carries no quantity at all. Nothing is converted between unit systems, and an approximate measure such as a pincée keeps its own size.
| Name | Type | Req | Description |
|---|---|---|---|
| factor | number | – | What to multiply the quantities by. Give this, or the two servings counts. |
| from_servings | integer | – | How many the list was written for. |
| ingredients | array | yes | The lines to rescale, as the recipe wrote them. |
| to_servings | integer | – | How many it should serve. |
| Name | Type | Req | Description |
|---|---|---|---|
| factor | number | yes | What the quantities were multiplied by. |
| ingredients | array | yes | – |
| notes | array | yes | – |
| rounded_count | integer | yes | Lines whose value had to move. |
| scaled_count | integer | yes | Lines whose arithmetic landed exactly. |
| unscaled_count | integer | yes | Lines carrying no quantity. |
No examples provided.
search_recipes Search the recipes ~265
Search Supertoinette by a dish or an ingredient. Each row carries the identifier to read the recipe with get_recipe. The site publishes no total, so 'total_available' is null and 'last_page' says how far the results run. The categories it counts beside a search are returned as 'facets': pass one back as 'category' to narrow the search, spelled exactly as the site spells it. A category the site does not know is answered like a search that matched nothing, so a filter that finds nothing is dropped and the answer says so.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Narrow the search to one category, taken from the 'facets' of a previous answer and spelled exactly as the site spells it. Never build one by hand: the site answers a wording it does not know with a… |
| limit | integer | – | Rows to render, 20 by default. The site serves at most 39 to a page, and 'rows_published' always states what the page held. |
| page | integer | – | Which page of results to read, 1 by default. 'last_page' says how far they run. |
| query | string | yes | A dish or an ingredient to look for, in French. |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string|null | yes | The category the answer was narrowed to, or null for a search across all of them. |
| facets | array | yes | The categories the site counts inside this search. A recipe filed under two is counted by both, so these do not add up to the rows served. |
| last_page | integer | yes | The highest page the site links to from this one. |
| notes | array | yes | – |
| page | integer | yes | The page these rows were read from. |
| query | string | yes | – |
| result_count | integer | yes | Rows rendered here. |
| results | array | yes | – |
| rows_published | integer | yes | Rows the page held, before any were rendered. |
| source | string | yes | – |
| total_available | null | yes | Supertoinette prints no total on a search page, so there is none to report. |
| url | string | yes | The page these rows were read from. |
No examples provided.
What is the io.github.smeet666/mcp-supertoinette server?
io.github.smeet666/mcp-supertoinette is listed in the public MCP registry as io.github.smeet666/mcp-supertoinette. Read Supertoinette recipes and rescale their quantities honestly. No API key. This page covers its npm package (mcp-supertoinette).
Is the io.github.smeet666/mcp-supertoinette server safe to use?
io.github.smeet666/mcp-supertoinette scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.smeet666/mcp-supertoinette server expose?
io.github.smeet666/mcp-supertoinette exposes 6 tools: get_recipe, search_recipes, list_categories, browse_recipes, get_wine_pairings, scale_ingredients. Their descriptions and schemas cost roughly 1,114 tokens of context every time the server is loaded.
Is the io.github.smeet666/mcp-supertoinette server still maintained?
io.github.smeet666/mcp-supertoinette is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.smeet666/mcp-supertoinette server under?
io.github.smeet666/mcp-supertoinette declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.