io.github.CloudCorpRecords/officelens
NPM · @RENETURCIOS/OFFICELENS · 2 COMPONENTS
Sourced, dated registry records of family offices in Switzerland, Liechtenstein and beyond.
Available components
Last scanned (4 hours ago)
Scores higher than 35% of npm servers
Category CRM and Sales
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 Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 434 tokens (~217/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 Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% 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.
- 4 Nov 26 68
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/officelens@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 →
get_record Read one registry record ~138
One firm by its registry id. Without a subscription key this returns the open fields and says how many named roles the full record holds; with one it returns the named roles, the contact channels, the full source list and the verification note.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Registry id, as returned by search_registry. |
| purpose | string | – | Optional. One line on what the user is trying to do: the task, not who they are or who they work for (e.g. "shortlisting Zurich multi-family offices for a fund raise"). Logged without the caller, to… |
No output schema declared.
No examples provided.
search_registry Search the family office registry ~296
Search verified family offices and related firms in Switzerland, Liechtenstein, Austria, Germany, Dubai (free, no names) and the US (registered advisers). Returns one page of open records — the same fields the public site publishes. Named people, contact channels, source lists and verification notes need a subscription. Read the skill resource before answering from these results.
| Name | Type | Req | Description |
|---|---|---|---|
| alloc | string | – | Subscription only: list firms by how they invest. Without a key the search refuses this filter; get_record gives any one firm's call free. |
| canton | string | – | Swiss canton code, e.g. ZH, ZG, GE. |
| country | string | – | – |
| page | integer | – | – |
| purpose | string | – | Optional. One line on what the user is trying to do: the task, not who they are or who they work for (e.g. "shortlisting Zurich multi-family offices for a fund raise"). Logged without the caller, to… |
| q | string | – | Free text. Without a key it looks in the open fields (name, city, register id, legal form, focus tags); with one, in the people and the purpose clauses too. For a place, filter by canton or country. |
| size | integer | – | Results per page, capped at 25 without a subscription key. |
| type | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/officelens MCP server?
io.github.CloudCorpRecords/officelens runs locally as an npm package, launched with npx -y @reneturcios/officelens. 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/officelens
claude mcp add cloudcorprecords-officelens -- npx -y @reneturcios/officelens
What is the io.github.CloudCorpRecords/officelens MCP server?
io.github.CloudCorpRecords/officelens is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/officelens. Sourced, dated registry records of family offices in Switzerland, Liechtenstein and beyond. This page covers its npm package (@reneturcios/officelens).
Is the io.github.CloudCorpRecords/officelens MCP server safe to use?
io.github.CloudCorpRecords/officelens scores 68 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/officelens MCP server expose?
io.github.CloudCorpRecords/officelens exposes 2 tools: search_registry, get_record. Their descriptions and schemas cost roughly 434 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/officelens MCP server still maintained?
io.github.CloudCorpRecords/officelens 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/officelens MCP server under?
io.github.CloudCorpRecords/officelens declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.