io.github.CloudCorpRecords/visprobe
NPM · @RENETURCIOS/VISPROBE · 2 COMPONENTS
AI-visibility audit: AI crawler access, identity files, page signals, hosted analysis.
Available components
Last scanned (45 minutes ago)
Scores higher than 38% 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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 537 tokens (~53/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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 +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.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 54
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/visprobe@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 →
analyze_site ~66
Starts the audit that also asks the answer engines whether they name the site, and returns a `run_id`. A survey without an account, the teaser on a free plan, the whole audit on a paid one.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The site to check (URL or domain) |
No output schema declared.
No examples provided.
check_ai_access ~73
Which AI crawlers `robots.txt` lets in, separating the ones that fetch a page to answer a live question from the ones that only collect training data. Blocking the first kind is what makes a site invisible; blocking the second costs nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The site to check (URL or domain) |
No output schema declared.
No examples provided.
check_identity ~61
Free and instant: which answer-engine crawlers get in, the identity files, structured data, an identity score out of 100 and what that reading says to fix. No model asked.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The site to check (URL or domain) |
No output schema declared.
No examples provided.
check_identity_files ~49
Which of the ten identity files exist — `llms.txt`, `ai.json`, `identity.json` and the rest.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The site to check (URL or domain) |
No output schema declared.
No examples provided.
check_page_signals ~48
Title, description, canonical, hreflang, and the Schema.org types in the page's JSON-LD.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The site to check (URL or domain) |
No output schema declared.
No examples provided.
compare_sites ~61
Your site and a competitor's, read the same way, side by side, and who is ahead on each count.
| Name | Type | Req | Description |
|---|---|---|---|
| other | string | yes | The competitor site (URL or domain) |
| url | string | yes | The site to check (URL or domain) |
No output schema declared.
No examples provided.
get_analysis ~43
Progress while it runs; the score out of 100 and what to fix first once it finishes.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The run id returned by analyze_site |
No output schema declared.
No examples provided.
my_reports ~17
Signed in: your audits, newest first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
visibility_fixes ~73
The fix plan, most important first: what to change, why, how many points it should recover, the pages it applies to, and a paste-ready file when there is one. Signed in, built from your latest audit of the site.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The site to check (URL or domain) |
No output schema declared.
No examples provided.
visibility_history ~46
How the reading moved: the INITE Atlas's weekly readings for a site it carries, and your own audits.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The site to check (URL or domain) |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/visprobe MCP server?
io.github.CloudCorpRecords/visprobe runs locally as an npm package, launched with npx -y @reneturcios/visprobe. 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/visprobe
claude mcp add cloudcorprecords-visprobe -- npx -y @reneturcios/visprobe
What is the io.github.CloudCorpRecords/visprobe MCP server?
io.github.CloudCorpRecords/visprobe is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/visprobe. AI-visibility audit: AI crawler access, identity files, page signals, hosted analysis. This page covers its npm package (@reneturcios/visprobe).
Is the io.github.CloudCorpRecords/visprobe MCP server safe to use?
io.github.CloudCorpRecords/visprobe scores 70 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/visprobe MCP server expose?
io.github.CloudCorpRecords/visprobe exposes 10 tools: check_ai_access, check_identity_files, check_page_signals, check_identity, visibility_fixes, and 5 more. Their descriptions and schemas cost roughly 537 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/visprobe MCP server still maintained?
io.github.CloudCorpRecords/visprobe 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/visprobe MCP server under?
io.github.CloudCorpRecords/visprobe declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.