io.github.CloudCorpRecords/chainlens
NPM · @RENETURCIOS/CHAINLENS · 2 COMPONENTS
Blockscout explorer data: addresses, blocks, transactions, tokens, NFTs, and contract reads.
Available components
Last scanned (3 hours ago)
Scores higher than 36% of npm servers
Category Crypto and Web3
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 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1223 tokens (~76/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
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.
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 +15
- Malware scan: unverified → pass ▲ security
- 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/chainlens@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 →
__unlock_blockchain_analysis__ ~28
Unlock blockchain analysis: local guidance and the list of supported chains. No network call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
direct_api_call ~128
Call an arbitrary Blockscout API v2 endpoint path directly.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | yes | Chain ID as a string, such as "1" for Ethereum. |
| cursor | string | – | Pagination cursor for the next page of results. |
| endpoint_path | string | yes | Blockscout API v2 endpoint path to call. |
| json_body | object | – | JSON request body to send, as an object. |
| method | string | – | HTTP method to use, defaulting to GET. |
| query_params | object | – | Query parameters to send with the request, as an object. |
No output schema declared.
No examples provided.
get_address_by_ens_name ~43
Resolve an ENS name to an address via Blockscout search on Ethereum mainnet.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | ENS name to resolve to an address. |
No output schema declared.
No examples provided.
get_address_info ~55
Get information about an address: balance, type, and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Blockchain address to look up. |
| chain_id | string | yes | Chain ID as a string, such as "1" for Ethereum. |
No output schema declared.
No examples provided.
get_block_info ~72
Get information about a block by number or hash.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | yes | Chain ID as a string, such as "1" for Ethereum. |
| include_transactions | boolean | – | Whether to include the block's transactions. |
| number_or_hash | string | yes | Block number or block hash to look up. |
No output schema declared.
No examples provided.
get_block_number ~58
Get the latest block number, optionally as of a datetime.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | yes | Chain ID as a string, such as "1" for Ethereum. |
| datetime | string | – | Datetime to return the block number as of. |
No output schema declared.
No examples provided.
get_chains_list ~49
List the supported chains, optionally filtered by a substring of name, chain id, or currency.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Substring filter matched against chain name, chain ID, or currency. |
No output schema declared.
No examples provided.
get_contract_abi ~52
Get the ABI of a verified smart contract.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Contract address to look up. |
| chain_id | string | yes | Chain ID as a string, such as "1" for Ethereum. |
No output schema declared.
No examples provided.
get_token_transfers_by_address ~143
Get token transfers for an address within an age range, optionally for one token.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Blockchain address whose token transfers to return. |
| age_from | string | yes | Start of the timestamp range to include, as a date or datetime string. |
| age_to | string | yes | End of the timestamp range to include, as a date or datetime string. |
| chain_id | string | yes | Chain ID as a string, such as "1" for Ethereum. |
| cursor | string | – | Pagination cursor for the next page of results. |
| token | string | – | Token to filter by, matched against its address, symbol, or name. |
No output schema declared.
No examples provided.
get_tokens_by_address ~68
Get token balances held by an address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Blockchain address whose token balances to return. |
| chain_id | string | yes | Chain ID as a string, such as "1" for Ethereum. |
| cursor | string | – | Pagination cursor for the next page of results. |
No output schema declared.
No examples provided.
get_transaction_info ~68
Get information about a transaction by hash.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | yes | Chain ID as a string, such as "1" for Ethereum. |
| hash | string | yes | Transaction hash to look up. |
| include_raw_input | boolean | – | Whether to include the transaction's raw input data. |
No output schema declared.
No examples provided.
get_transactions_by_address ~136
Get transactions for an address within an age range, optionally filtered by method.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Blockchain address whose transactions to return. |
| age_from | string | yes | Start of the timestamp range to include, as a date or datetime string. |
| age_to | string | yes | End of the timestamp range to include, as a date or datetime string. |
| chain_id | string | yes | Chain ID as a string, such as "1" for Ethereum. |
| cursor | string | – | Pagination cursor for the next page of results. |
| methods | string | – | Comma-separated list of transaction method names to filter by. |
No output schema declared.
No examples provided.
inspect_contract_code ~72
Inspect the source code of a verified smart contract, optionally for one file.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Contract address to inspect. |
| chain_id | string | yes | Chain ID as a string, such as "1" for Ethereum. |
| file_name | string | – | Name of a single source file to inspect. |
No output schema declared.
No examples provided.
lookup_token_by_symbol ~57
Look up tokens by symbol on a chain via Blockscout search.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | yes | Chain ID as a string, such as "1" for Ethereum. |
| symbol | string | yes | Token symbol to search for. |
No output schema declared.
No examples provided.
nft_tokens_by_address ~78
Get NFT tokens (ERC-721 and ERC-1155) held by an address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Blockchain address whose NFT tokens to return. |
| chain_id | string | yes | Chain ID as a string, such as "1" for Ethereum. |
| cursor | string | – | Pagination cursor for the next page of results. |
No output schema declared.
No examples provided.
read_contract ~116
Read a smart contract function using its ABI, function name, and JSON-encoded args.
| Name | Type | Req | Description |
|---|---|---|---|
| abi | object | yes | Contract ABI to use for the call. |
| address | string | yes | Contract address to read from. |
| args | string | – | Function arguments as a JSON-encoded string. |
| block | string | – | Block to perform the read at. |
| chain_id | string | yes | Chain ID as a string, such as "1" for Ethereum. |
| function_name | string | yes | Name of the contract function to call. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/chainlens MCP server?
io.github.CloudCorpRecords/chainlens runs locally as an npm package, launched with npx -y @reneturcios/chainlens. 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/chainlens
claude mcp add cloudcorprecords-chainlens -- npx -y @reneturcios/chainlens
What is the io.github.CloudCorpRecords/chainlens MCP server?
io.github.CloudCorpRecords/chainlens is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/chainlens. Blockscout explorer data: addresses, blocks, transactions, tokens, NFTs, and contract reads. This page covers its npm package (@reneturcios/chainlens).
Is the io.github.CloudCorpRecords/chainlens MCP server safe to use?
io.github.CloudCorpRecords/chainlens scores 69 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/chainlens MCP server expose?
io.github.CloudCorpRecords/chainlens exposes 16 tools: __unlock_blockchain_analysis__, get_chains_list, get_address_by_ens_name, lookup_token_by_symbol, get_contract_abi, and 11 more. Their descriptions and schemas cost roughly 1,223 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/chainlens MCP server still maintained?
io.github.CloudCorpRecords/chainlens 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/chainlens MCP server under?
io.github.CloudCorpRecords/chainlens declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.