io.github.ParthibanRajasekaran/rendercheck
NPM · @RENDERCHECK/SDK
Check from a screenshot that text is really visible to users. Local, offline OCR.
Available components
Last scanned (17 hours ago)
Scores higher than 93% of npm servers
Category Testing and QA
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 Security96
- 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
- 10 of 17 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 ParthibanRajasekaran/text-from-image). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 23 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 327 tokens (~163/item across 2 items; 2 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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +3
- Stability: unverified → 0.23 ▲ functional
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 4 Nov 2026 · Analysed npm/@rendercheck/sdk@0.6.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 | ParthibanRajasekaran/text-from-image |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ParthibanRajasekaran/text-from-image/.github/workflows/release-rendercheck.yml@refs/tags/rendercheck-v0.6.0 |
| Rekor log index | 3209680665 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f7df5a032272f64193d0aa641eee40976b5601af4234a10f05892f8a9fe5949dc9e0ca98b730c346bd7853fd60957f8813c54a64579b092106d248d46 |
Background: How many MCP packages publish verified provenance →
Dependencies 17 packages
| Packages resolved | 17 |
|---|---|
| Stale | 10 |
| 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 →
read_text Read the text visible in a screenshot ~105
OCR a screenshot locally and return the text a user would see, line by line with confidence and position. Use it to see what actually rendered when you do not know what to expect.
| Name | Type | Req | Description |
|---|---|---|---|
| image_base64 | string | – | Base64 PNG or JPEG, if there is no file path |
| image_path | string | – | Path to a PNG or JPEG screenshot on this machine |
| region | object | – | Only read this part of the screenshot (pixels from the top-left corner) |
No output schema declared.
No examples provided.
verify_text Verify text is visible on screen ~222
Check from a screenshot that expected text is really visible to a user (not just in the DOM). Runs local OCR, offline. Returns pass/fail, what was read, confidence and, on failure, the reason (NOT_FOUND, LOW_CONFIDENCE, INSUFFICIENT_CONTRAST) and where on the screenshot. Use it after changing UI to confirm the change rendered.
| Name | Type | Req | Description |
|---|---|---|---|
| exact | boolean | – | Require the region text to equal the expected text |
| expected | string | yes | The text a user should be able to read |
| ignore_case | boolean | – | – |
| image_base64 | string | – | Base64 PNG or JPEG, if there is no file path |
| image_path | string | – | Path to a PNG or JPEG screenshot on this machine |
| min_confidence | number | – | OCR confidence, default 80 |
| min_contrast_ratio | number | – | WCAG contrast ratio, e.g. 4.5 |
| region | object | – | Only read this part of the screenshot (pixels from the top-left corner) |
No output schema declared.
No examples provided.
How do I install the io.github.ParthibanRajasekaran/rendercheck MCP server?
io.github.ParthibanRajasekaran/rendercheck runs locally as an npm package, launched with npx -y @rendercheck/sdk. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rendercheck/sdk
claude mcp add parthibanrajasekaran-rendercheck -- npx -y @rendercheck/sdk
What is the io.github.ParthibanRajasekaran/rendercheck MCP server?
io.github.ParthibanRajasekaran/rendercheck is an MCP server listed in the public MCP registry as io.github.ParthibanRajasekaran/rendercheck. Check from a screenshot that text is really visible to users. Local, offline OCR. This page covers its npm package (@rendercheck/sdk).
Is the io.github.ParthibanRajasekaran/rendercheck MCP server safe to use?
io.github.ParthibanRajasekaran/rendercheck scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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.ParthibanRajasekaran/rendercheck MCP server expose?
io.github.ParthibanRajasekaran/rendercheck exposes 2 tools: verify_text, read_text. Their descriptions and schemas cost roughly 327 tokens of context every time the server is loaded.
Is the io.github.ParthibanRajasekaran/rendercheck MCP server still maintained?
io.github.ParthibanRajasekaran/rendercheck is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.ParthibanRajasekaran/rendercheck MCP server under?
io.github.ParthibanRajasekaran/rendercheck declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.