elements-live
Registry code: f28ff84024b774b3
Elements Live is a research tool for chemistry, materials and physics literature: one question in, several ways of finding papers out -- classic title+abstract relevance search, research communities, the classics a field cites, what matters now, the newest work, element/topic lists, boolean filters, start-from-a-DOI -- plus research-intensity measurements for the 118 elements and thousands of topics. WHICH TOOL FIRST: any literature question, broad or about a specific process -> research (its `relevant` lens matches title AND abstract across the whole corpus); one element's or topic's top…
- endpoint
- https://www.elements-live.com/mcp
- door code
- 90554ed0dd10f79f
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 10 · newcomer
- Is elements-live live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
- Is elements-live free to use?
- No — it charges per call, from 0.01 USDC, quoted in its own 402 answers.
- What tools does elements-live have?
- 9 tools: get_element_ri, get_subject_history, get_subject_papers, research, get_subject_ri, lab_run, search_subjects, get_element_papers, ….
- Is elements-live safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.2%· all time 99.3%
last good check
of 9 tools
- down → live
- degraded → live
- degraded → down· timeout after 20000ms
- live → degraded· timeout after 20000ms
- live → degraded· timeout after 20000ms
- used for
- get research intensity of a chemical element
- track research topic trends over time
- list top papers on a topic
- buy a custom paper search
- takes → gives
- text → data
- tools
- 7 reads1 moves money
Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 17 doors on this origin, so the chain figures are the operator's. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-04
no flags
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_subject_history reads 0.1 USDC paid 8h ago
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"]).
{ "type": "object", "required": [ "subject_type", "subject_id" ], "properties": { "resolution": { "enum": [ "yearly", "monthly" ], "type": "string", "default": "yearly" }, "subject_id": { "type": "string" }, "subject_type": { "enum": [ "keyword", "sector" ], "type": "string" } } }arguments 27 linesget_subject_papers reads 0.02 USDC paid 8h ago
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"]).
{ "type": "object", "required": [ "subject_type", "subject_id" ], "properties": { "sort": { "enum": [ "impact", "newest", "foundational" ], "type": "string", "default": "impact", "description": "impact = citation-impact ranking (default); newest = most recently published first; foundational = most-cited first (the classics a reading list starts from)." }, "limit": { "type": "integer", "default": 20, "maximum": 100 }, "subject_id": { "type": "string" }, "subject_type": { "enum": [ "keyword", "sector" ], "type": "string" } } }arguments 34 linesresearch 0.05 USDC paid 14h ago
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"]).
{ "type": "object", "properties": { "q": { "type": "string", "description": "The research question, in plain words." }, "page": { "type": "integer", "default": 1, "maximum": 5, "minimum": 1 }, "paper": { "type": "string", "description": "Alternative to q: a DOI or title to start from." }, "lenses": { "type": "array", "items": { "enum": [ "relevant", "foundational", "now", "newest" ], "type": "string" }, "description": "Default: all four." }, "page_size": { "type": "integer", "default": 10, "maximum": 10, "minimum": 1, "description": "Papers per lens." } } }arguments 39 linesget_subject_ri reads 0.01 USDC paid 14h ago
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"]).
{ "type": "object", "required": [ "subject_type", "subject_id" ], "properties": { "subject_id": { "type": "string" }, "subject_type": { "enum": [ "keyword", "sector" ], "type": "string" } } }arguments 19 lineslab_run moves money paid never probed
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"]).
{ "type": "object", "required": [ "quote_id" ], "properties": { "depth": { "enum": [ "papers_20", "papers_100" ], "type": "string", "default": "papers_20" }, "quote_id": { "type": "string", "description": "From lab_quote." } } }arguments 20 linessearch_subjects reads 0.01 USDC paid 10h ago
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"]).
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string" } } }arguments 11 linesget_element_papers reads 0.02 USDC paid 10h ago
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"]).
{ "type": "object", "required": [ "symbol" ], "properties": { "sort": { "enum": [ "impact", "newest", "foundational" ], "type": "string", "default": "impact", "description": "impact = citation-impact ranking (default); newest = most recently published first; foundational = most-cited first (the classics a reading list starts from)." }, "limit": { "type": "integer", "default": 20, "maximum": 100 }, "symbol": { "type": "string", "description": "Element symbol, e.g. 'Fe' (a name like 'Iron' or an atomic number like '26' also works)" }, "keyword": { "type": "string", "description": "Optional: narrow to one application keyword." } } }arguments 31 lineslab_quote reads 0.01 USDC paid 14h ago
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"]).
{ "type": "object", "properties": { "query": { "type": "string", "description": "The filter, in the syntax above." }, "markdown": { "type": "string", "description": "Alternative: markdown carrying the filter in a ```query fenced block." } } }arguments 13 linesget_element_ri reads unknown 10h ago
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.
{ "type": "object", "required": [ "symbol" ], "properties": { "symbol": { "type": "string", "description": "Element symbol, e.g. 'Fe' (a name like 'Iron' or an atomic number like '26' also works)" } } }arguments 12 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idf28ff84024b774b3.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f28ff84024b774b3/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f28ff84024b774b3?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.