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.

Recap Studio

MCPB · RECAP-STUDIO.MCPB

Render and score one HTML page that explains your work or a topic. Opens offline, no JavaScript.

Available components

34 Trust /100

Last scanned (17 hours ago)

Scores higher than 70% of MCPB servers

Category Documents and Files

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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability55
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 624 tokens (~56/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage69
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 7% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy_vercel_preview" implies "deploy" 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 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; 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 (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

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 Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  • Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).

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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 32

    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 mcpb/https://github.com/Aboudjem/recap-studio/releases/download/v0.6.4/recap-studio.mcpb

Provenance No attestation

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

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 11 exposed · ~624 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
cache_source ~68

Append a research source to .recap-studio/cache/sources.jsonl. Idempotent on URL hash.

NameTypeReqDescription
excerptstring––
publishedAtstring|null––
publisherstring––
summarystringyes–
urlstringyes–

No output schema declared.

No examples provided.

create_run_artifact ~54

Persist a Recap Studio artifact under artifacts/<slug>/<filename>. Use for generated content JSON, diagrams, reports.

NameTypeReqDescription
contentstringyes–
filenamestringyes–
slugstringyes–

No output schema declared.

No examples provided.

deploy_vercel_preview ~57

(stub) Never deploys. Checks that confirmed: true and VERCEL_TOKEN are set, then returns the shell command that deploys a Vercel preview, for you to run yourself.

NameTypeReqDescription
confirmedbooleanyes–

No output schema declared.

No examples provided.

generate_mermaid_diagram ~40

Validate a Mermaid diagram source and return a normalized snippet plus required alt text.

NameTypeReqDescription
altstringyes–
codestringyes–

No output schema declared.

No examples provided.

read_run_artifact ~30

Read a previously persisted artifact.

NameTypeReqDescription
filenamestringyes–
slugstringyes–

No output schema declared.

No examples provided.

render_page_screenshot ~48

(scaffold) Render a screenshot of the given URL using Playwright. Disabled until Playwright is installed locally.

NameTypeReqDescription
outPathstringyes–
urlstringyes–

No output schema declared.

No examples provided.

render_recap_html ~111

Render a RecapPageContent JSON into ONE self-contained, dark-mode HTML file: inlined CSS, zero JavaScript, opens with a double-click offline. Reads artifacts/<slug>/content.json (or the optional path) and writes artifacts/<slug>/recap-<slug>.html. Works in any project and any MCP client.

NameTypeReqDescription
pathstring–Optional path to the content JSON, relative to the working directory.
slugstringyes–
themestring––

No output schema declared.

No examples provided.

run_accessibility_scan ~48

(scaffold) Run an axe-core scan against a URL or local HTML snapshot. Disabled until axe is installed.

NameTypeReqDescription
htmlPathstring––
urlstring––

No output schema declared.

No examples provided.

run_lighthouse_summary ~33

(scaffold) Run a Lighthouse summary. Disabled until lighthouse is installed locally.

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

send_email_draft ~70

(stub) Never sends email. Returns the draft (to, subject, first 200 characters of the body) for you to paste into your mail client.

NameTypeReqDescription
bodystringyes–
confirmedbooleanyes–
subjectstringyes–
tostringyes–

No output schema declared.

No examples provided.

validate_content ~65

Run the deterministic validation suite against a content JSON and return a Markdown report, verdict first. Reads artifacts/<slug>/content.json, or the optional path.

NameTypeReqDescription
pathstring–Optional path to the content JSON, relative to the working directory.
slugstringyes–

No output schema declared.

No examples provided.

Install

How do I install the Recap Studio MCP server?

Recap Studio ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, aed2473c6a548dfd64d6e534a2cbd8b3636d2aa841f399f3391720a788946848; the commands to do that are on this page. If it does not match, do not open it.

mcpb · recap-studio.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

aed2473c6a548dfd64d6e534a2cbd8b3636d2aa841f399f3391720a788946848

macOS / Linux

echo "aed2473c6a548dfd64d6e534a2cbd8b3636d2aa841f399f3391720a788946848  recap-studio.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\recap-studio.mcpb).Hash -eq "aed2473c6a548dfd64d6e534a2cbd8b3636d2aa841f399f3391720a788946848"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the Recap Studio MCP server?

Recap Studio is an MCP server listed in the public MCP registry as io.github.Aboudjem/recap-studio. Render and score one HTML page that explains your work or a topic. Opens offline, no JavaScript. This page covers its MCPB bundle (https://github.com/Aboudjem/recap-studio/releases/download/v0.6.4/recap-studio.mcpb).

Is the Recap Studio MCP server safe to use?

Recap Studio scores 34 out of 100 on VerifyMCP. 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 Recap Studio MCP server expose?

Recap Studio exposes 11 tools: create_run_artifact, read_run_artifact, cache_source, generate_mermaid_diagram, render_page_screenshot, and 6 more. Their descriptions and schemas cost roughly 624 tokens of context every time the server is loaded.

What licence is the Recap Studio MCP server under?

Recap Studio 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 Recap Studio MCP server?

VerifyMCP ran 12 checks on Recap Studio, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Recap Studio: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.