io.github.CloudCorpRecords/elemindex
OCI · GHCR.IO/CLOUDCORPRECORDS/ELEMINDEX · 2 COMPONENTS
Research-intensity trends, papers and metrics for the 118 chemical elements and topics.
Available components
Last scanned (4 hours ago)
Scores higher than 39% of OCI servers
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
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 Usability66
- AI-judged instruction clarity (excellent).Pass
- 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. 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 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
- 4 Nov 26 39
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 oci/ghcr.io/cloudcorprecords/elemindex@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 | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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_element_papers Top papers for an element ~291
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"]).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Element symbol, e.g. 'Fe' (a name like 'Iron' or an atomic number like '26' also works) |
No output schema declared.
No examples provided.
get_element_ri Element research intensity ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Element symbol, e.g. 'Fe' (a name like 'Iron' or an atomic number like '26' also works) |
No output schema declared.
No examples provided.
get_subject_history Subject research history ~118
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"]).
| Name | Type | Req | Description |
|---|---|---|---|
| resolution | string | – | Time resolution of the history series: yearly or monthly. |
| subject_id | string | yes | Subject identifier, as returned by search_subjects. |
| subject_type | string | yes | Kind of subject: keyword or sector. |
No output schema declared.
No examples provided.
get_subject_papers Top papers for a subject ~257
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"]).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Subject identifier, as returned by search_subjects. |
| subject_type | string | yes | Kind of subject: keyword or sector. |
No output schema declared.
No examples provided.
get_subject_ri Subject research intensity ~116
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"]).
| Name | Type | Req | Description |
|---|---|---|---|
| subject_id | string | yes | Subject identifier, as returned by search_subjects. |
| subject_type | string | yes | Kind of subject: keyword or sector. |
No output schema declared.
No examples provided.
lab_quote Lab: scope a filtered query ~234
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"]).
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | – | Alternative: markdown carrying the filter in a ```query fenced block. |
| query | string | – | The filter, in the syntax above. |
No output schema declared.
No examples provided.
lab_run Lab: papers for a quote ~174
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"]).
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | How many top papers to return: papers_20 (top 20) or papers_100 (top 100). |
| quote_id | string | yes | From lab_quote. |
No output schema declared.
No examples provided.
research Research reading lists ~378
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"]).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
search_subjects Search research subjects ~104
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"]).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Free-text query naming a compound, material or research topic to resolve to a subject. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/elemindex MCP server?
io.github.CloudCorpRecords/elemindex runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/elemindex:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/cloudcorprecords/elemindex
claude mcp add cloudcorprecords-elemindex -- docker run --rm -i ghcr.io/cloudcorprecords/elemindex:0.1.0
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 container image (ghcr.io/cloudcorprecords/elemindex).
Is the io.github.CloudCorpRecords/elemindex MCP server safe to use?
io.github.CloudCorpRecords/elemindex scores 39 out of 100 on VerifyMCP. 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.