# io.github.CloudCorpRecords/elemindex (npm · @reneturcios/elemindex)

Research-intensity trends, papers and metrics for the 118 chemical elements and topics.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/elemindex`: 69/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-elemindex/reneturcios-elemindex.md), [page](https://verifymcp.io/servers/cloudcorprecords-elemindex/reneturcios-elemindex)
- oci · `ghcr.io/cloudcorprecords/elemindex`: 39/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-elemindex/ghcr-io-cloudcorprecords-elemindex.md), [page](https://verifymcp.io/servers/cloudcorprecords-elemindex/ghcr-io-cloudcorprecords-elemindex)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/elemindex`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1756 tokens (~195/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.CloudCorpRecords/elemindex MCP server?

io.github.CloudCorpRecords/elemindex runs locally as an npm package, launched with npx -y @reneturcios/elemindex. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-elemindex -- npx -y @reneturcios/elemindex
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-elemindex": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/elemindex"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-elemindex": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/elemindex"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-elemindex -- npx -y @reneturcios/elemindex
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-elemindex": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/elemindex"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-elemindex --command npx --arg -y --arg @reneturcios/elemindex
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-elemindex:
    command: "npx"
    args: ["-y", "@reneturcios/elemindex"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-elemindex": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/elemindex"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-elemindex -t stdio -c npx -a -y @reneturcios/elemindex
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-elemindex": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/elemindex"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 68)

First indexed and scored.

## MCP tools (9)

### `research` (~378 tokens)

Research reading lists

CALL THIS FIRST for a literature question about chemistry, materials or physics research -- a broad one ('what matters in X') or a specific process or parameter one (a deposition condition, a property value, a defect mechanism). Send the question in plain words (q), or a paper you already know (paper: DOI or title). Returns reading lists in four lenses: relevant (the papers whose TITLE AND ABSTRACT best match the question, across the whole corpus, BM25 -- start here for a specific question), foundational (the classics the question's own papers cite most), now (highest impact, young papers' citations projected) and newest (last two years); plus the research communities and element sub-communities the question is about, with why each matched and whether it is rising. Put the question's key terms in q: filler words are ignored. unmatched_terms lists words that matched nothing; rephrase those. Each paper carries its DOI, a one-line reason and its abstract where one is on file. Our corpus is curated, not complete: the relevant lens also brings up to 3 of every 10 results from OpenAlex, marked source='openalex' and labelled not yet curated. One page = up to 10 papers per lens; ask for page 2+ only if needed. Requires a Personal+ account. Without a key, pay per call: $0.05 in USDC on Base or Solana via x402 (send the payment in _meta["x402/payment"]).

Input parameters:

- `lenses` (array): Default: all four.
- `page` (integer): Result page number for paged paper results.
- `page_size` (integer): Papers per lens.
- `paper` (string): Alternative to q: a DOI or title to start from.
- `q` (string): The research question, in plain words.

### `get_element_ri` (~84 tokens)

Element research intensity

Get current Research Intensity (RIS) for one of the 118 chemical elements, with a citation URL. No API key needed. Historical RI (HRI) is included with a Personal+ key.

Input parameters:

- `symbol` (string, required): Element symbol, e.g. 'Fe' (a name like 'Iron' or an atomic number like '26' also works)

### `search_subjects` (~104 tokens)

Search research subjects

Resolve a free-text query (a compound, material, or research topic) to its subject_type/subject_id for use with get_subject_ri. Free with any API key. Without a key, pay per call: $0.01 in USDC on Base or Solana via x402 (send the payment in _meta["x402/payment"]).

Input parameters:

- `query` (string, required): Free-text query naming a compound, material or research topic to resolve to a subject.

### `get_subject_ri` (~116 tokens)

Subject research intensity

Get RI, RIS, HRI and paper count for one research topic/keyword/sector. Requires a Personal+ account -- call search_subjects first to resolve subject_type/subject_id. Without a key, pay per call: $0.01 in USDC on Base or Solana via x402 (send the payment in _meta["x402/payment"]).

Input parameters:

- `subject_id` (string, required): Subject identifier, as returned by search_subjects.
- `subject_type` (string, required): Kind of subject: keyword or sector.

### `get_subject_history` (~118 tokens)

Subject research history

Full yearly (or monthly) RIS/HRI history for one topic/keyword/sector. Requires a Personal+ account. Without a key, pay per call: $0.10 in USDC on Base or Solana via x402 (send the payment in _meta["x402/payment"]).

Input parameters:

- `resolution` (string): Time resolution of the history series: yearly or monthly.
- `subject_id` (string, required): Subject identifier, as returned by search_subjects.
- `subject_type` (string, required): Kind of subject: keyword or sector.

### `get_subject_papers` (~257 tokens)

Top papers for a subject

The top papers for one research topic (resolve it with search_subjects first) -- title, DOI, venue, year, citations. Use it when asked what to READ about a specific topic, rather than how active it is. sort=impact (default) favours recent, well-cited work; sort=foundational gives the most-cited classics; sort=newest the latest. Each paper carries its abstract where one is on file (about 6 in 10). Requires a Personal+ account. Capped at 100 papers with no pagination. Without a key, pay per call: $0.02 for up to 20 papers, $0.10 for up to 100, in USDC on Base or Solana via x402 (send the payment in _meta["x402/payment"]).

Input parameters:

- `limit` (integer): Maximum number of top papers to return.
- `sort` (string): impact = citation-impact ranking (default); newest = most recently published first; foundational = most-cited first (the classics a reading list starts from).
- `subject_id` (string, required): Subject identifier, as returned by search_subjects.
- `subject_type` (string, required): Kind of subject: keyword or sector.

### `get_element_papers` (~291 tokens)

Top papers for an element

The top papers for one element, narrowed with keyword to one of its materials or applications (e.g. symbol='Al', keyword='aluminum nitride'; the keyword must name one of the element's topics exactly, case aside -- search_subjects finds topic names). Returns title, DOI, venue, year, citations. sort=impact (default) favours recent, well-cited work; sort=foundational gives the most-cited classics; sort=newest the latest. Each paper carries its abstract where one is on file (about 6 in 10). Requires a Personal+ account. Capped at 100 papers with no pagination. Without a key, pay per call: $0.02 for up to 20 papers, $0.10 for up to 100, in USDC on Base or Solana via x402 (send the payment in _meta["x402/payment"]).

Input parameters:

- `keyword` (string): Optional: narrow to one application keyword.
- `limit` (integer): Maximum number of top papers to return.
- `sort` (string): impact = citation-impact ranking (default); newest = most recently published first; foundational = most-cited first (the classics a reading list starts from).
- `symbol` (string, required): Element symbol, e.g. 'Fe' (a name like 'Iron' or an atomic number like '26' also works)

### `lab_quote` (~234 tokens)

Lab: scope a filtered query

Scope a multi-term question with a boolean filter: +must -exclude "exact topic" (a OR b) wild* year:2015..2026, over element symbols or names and EXACT topic names (e.g. +Li +Co "solid electrolyte" -sulfide). Words that are neither are DROPPED, and wildcards can expand into unrelated fields: read `warnings` first -- it lists every dropped term with the nearest topics, every abbreviation read as a topic, and every wildcard expansion. Returns how many papers match, by year and by research community, the nearest broader query when nothing matches, and a quote_id that lab_run turns into the ranked papers. Narrow filters (two elements + one topic) work best. Requires a Professional+ account. Without a key, pay per call: $0.01 in USDC on Base or Solana via x402 (send the payment in _meta["x402/payment"]).

Input parameters:

- `markdown` (string): Alternative: markdown carrying the filter in a ```query fenced block.
- `query` (string): The filter, in the syntax above.

### `lab_run` (~174 tokens)

Lab: papers for a quote

Get the papers for a lab_quote: pass its quote_id and a depth (papers_20 or papers_100) to get the top papers matching the quoted filter, ranked by impact, with the curation behind each rank. Each paper carries its abstract where one is on file (about 6 in 10). A stale or expired quote is refused. Requires a Professional+ account. Without a key, pay per call: the quoted price of the depth, less the $0.01 quote credit in USDC on Base or Solana via x402 (send the payment in _meta["x402/payment"]).

Input parameters:

- `depth` (string): How many top papers to return: papers_20 (top 20) or papers_100 (top 100).
- `quote_id` (string, required): From lab_quote.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-elemindex/reneturcios-elemindex#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 68

## Common questions

### What is the io.github.CloudCorpRecords/elemindex MCP server?

io.github.CloudCorpRecords/elemindex is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/elemindex. Research-intensity trends, papers and metrics for the 118 chemical elements and topics. This page covers its npm package (@reneturcios/elemindex).

### Is the io.github.CloudCorpRecords/elemindex MCP server safe to use?

io.github.CloudCorpRecords/elemindex 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/elemindex MCP server expose?

io.github.CloudCorpRecords/elemindex exposes 9 tools: research, get_element_ri, search_subjects, get_subject_ri, get_subject_history, and 4 more. Their descriptions and schemas cost roughly 1,756 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/elemindex MCP server still maintained?

io.github.CloudCorpRecords/elemindex 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/elemindex MCP server under?

io.github.CloudCorpRecords/elemindex declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/elemindex
- Socket report: https://socket.dev/npm/package/@reneturcios/elemindex
- Repository: https://github.com/CloudCorpRecords/elemindex
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-elemindex/reneturcios-elemindex.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-elemindex/reneturcios-elemindex.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-elemindex/reneturcios-elemindex