Paprika MCP Server

@bojanrajkovic/mcp-paprika npm v1.6.1 Source verified

Published by bojanrajkovic — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for Paprika recipe manager

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 48

Each tool and what it can reach — statically extracted from the published source.

  • list_meal_historyingests untrusted input
  • add_grocery_itemsno sensitive capability
  • add_mealsno sensitive capability
  • add_menu_itemsno sensitive capability
  • add_menu_to_plannerno sensitive capability
  • add_pantry_itemsno sensitive capability
  • clear_allno sensitive capability
  • clear_purchasedno sensitive capability
  • create_categoryno sensitive capability
  • create_grocery_listno sensitive capability
Show 38 more tools ↓
  • create_menuno sensitive capability
  • create_recipeno sensitive capability
  • delete_categoryno sensitive capability
  • delete_grocery_itemno sensitive capability
  • delete_grocery_listno sensitive capability
  • delete_mealno sensitive capability
  • delete_menuno sensitive capability
  • delete_menu_itemno sensitive capability
  • delete_pantry_itemno sensitive capability
  • delete_photono sensitive capability
  • delete_recipeno sensitive capability
  • discover_recipesno sensitive capability
  • empty_trashno sensitive capability
  • filter_by_ingredientno sensitive capability
  • filter_by_timeno sensitive capability
  • generate_photono sensitive capability
  • get_pantry_itemno sensitive capability
  • list_aislesno sensitive capability
  • list_categoriesno sensitive capability
  • list_grocery_listsno sensitive capability
  • list_meal_typesno sensitive capability
  • list_menusno sensitive capability
  • list_pantryno sensitive capability
  • list_recipesno sensitive capability
  • move_to_pantryno sensitive capability
  • read_grocery_listno sensitive capability
  • read_menuno sensitive capability
  • read_recipeno sensitive capability
  • rename_grocery_listno sensitive capability
  • search_recipesno sensitive capability
  • update_categoryno sensitive capability
  • update_grocery_itemno sensitive capability
  • update_mealno sensitive capability
  • update_menuno sensitive capability
  • update_menu_itemno sensitive capability
  • update_pantry_itemno sensitive capability
  • update_recipeno sensitive capability
  • upload_photono sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.6.1 latest A 97/100 0 1.13.0 2026-09-08

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/bojanrajkovic-mcp-paprika/badge.svg)](https://mcptrustchecker.com/registry/bojanrajkovic-mcp-paprika)
HTML
<a href="https://mcptrustchecker.com/registry/bojanrajkovic-mcp-paprika"><img src="https://mcptrustchecker.com/registry/bojanrajkovic-mcp-paprika/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/bojanrajkovic-mcp-paprika/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @bojanrajkovic/mcp-paprika --online

Use the free API → How scoring works

More in Web, Search & Scraping