io.github.CloudCorpRecords/vischeck
NPM · @RENETURCIOS/VISCHECK · 2 COMPONENTS
See whether ChatGPT, Claude and Gemini recommend a startup product, and who wins instead.
Available components
Last scanned (15 minutes ago)
Scores higher than 40% of npm servers
Category Marketing and SEO
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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 452 tokens (~75/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 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
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 6 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.
- 4 Nov 26 71
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@reneturcios/vischeck@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
check_public_launch Check a launch FrontStat tracks ~116
Look up a product launch that FrontStat already tracks: its name, its rank on this week's or this month's launch board, its visibility score (0 to 100), and whether ChatGPT, Claude and Gemini recommend it for its buyer question, with the products they name instead. Returns a link to its public FrontStat page. If FrontStat does not track the domain yet, says so and links to the free report. No token needed.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The product's domain or URL, for example example.com. |
No output schema declared.
No examples provided.
cited_sites Sites AI search engines cite ~68
The sites the AI search engines cite most when they answer your buyer questions, with how many answers cite each one, your own domain left out. These are the pages to get mentioned on. Needs FrontStat Pro: send your dashboard token as a Bearer token. Covers the domain on your subscription.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_visibility Your AI visibility today ~79
Your latest FrontStat Pro report: date, visibility score, whether each AI search engine recommends your product for your main buyer question and who it names instead, and for your buyer questions how many answers recommend you (X of Y) per assistant. Needs FrontStat Pro: send your dashboard token as a Bearer token. Covers the domain on your subscription.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_buyer_questions Your buyer questions ~60
Each buyer question FrontStat asks the AI search engines about your market, with yes or no per engine: does the answer recommend your product. Needs FrontStat Pro: send your dashboard token as a Bearer token. Covers the domain on your subscription.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
visibility_history Your visibility over 30 days ~64
One point per day for the last 30 days: your visibility score and how many answers recommend your product. Use it to see whether your changes moved AI search engines. Needs FrontStat Pro: send your dashboard token as a Bearer token. Covers the domain on your subscription.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
who_wins_instead Who wins instead of you ~65
The products the AI search engines name instead of yours, and the sites they cite, each with how many answers it appears in, from your latest Pro report. Needs FrontStat Pro: send your dashboard token as a Bearer token. Covers the domain on your subscription.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/vischeck MCP server?
io.github.CloudCorpRecords/vischeck runs locally as an npm package, launched with npx -y @reneturcios/vischeck. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/vischeck
claude mcp add cloudcorprecords-vischeck -- npx -y @reneturcios/vischeck
What is the io.github.CloudCorpRecords/vischeck MCP server?
io.github.CloudCorpRecords/vischeck is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/vischeck. See whether ChatGPT, Claude and Gemini recommend a startup product, and who wins instead. This page covers its npm package (@reneturcios/vischeck).
Is the io.github.CloudCorpRecords/vischeck MCP server safe to use?
io.github.CloudCorpRecords/vischeck scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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.CloudCorpRecords/vischeck MCP server expose?
io.github.CloudCorpRecords/vischeck exposes 6 tools: check_public_launch, get_visibility, list_buyer_questions, who_wins_instead, cited_sites, visibility_history. Their descriptions and schemas cost roughly 452 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/vischeck MCP server still maintained?
io.github.CloudCorpRecords/vischeck is still listed as active in the MCP registry. We last reached this channel on 5 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.CloudCorpRecords/vischeck MCP server under?
io.github.CloudCorpRecords/vischeck declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.