com.tomesphere/tomesphere
REMOTE · MCP.TOMESPHERE.COM · SCANNED AUG 3
Search 8.5M scientific papers with LLM TLDRs, citations, linked entities, figures, and full text.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1029 tokens (~114/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 Management27
- Stability observed for 8 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
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.tomesphere.com
claude mcp add --transport http com-tomesphere-tomesphere https://mcp.tomesphere.com/api/mcp
[mcp_servers.com-tomesphere-tomesphere] url = "https://mcp.tomesphere.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-tomesphere-tomesphere": {
"type": "remote",
"url": "https://mcp.tomesphere.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-tomesphere-tomesphere --url https://mcp.tomesphere.com/api/mcp --transport streamable-http
mcp_servers:
com-tomesphere-tomesphere:
url: "https://mcp.tomesphere.com/api/mcp" {
"mcpServers": {
"com-tomesphere-tomesphere": {
"type": "http",
"url": "https://mcp.tomesphere.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 62
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 3 Aug 2026 · Probed https://mcp.tomesphere.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.tomesphere.com | CN=YR2,O=Let's Encrypt,C=US | 27 Jul 2026 | 25 Oct 2026 | RSA 2048 | SHA256-RSA | 65c8fba5dd8f183b27f1fe85fde17f70c2a |
| SANs: mcp.tomesphere.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of mcp.tomesphere.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tomesphere.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.tomesphere.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.tomesphere.com/api/mcp | HTTPS enforced | 308 | https://mcp.tomesphere.com/api/mcp |
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.
citations ~92
Get papers that cite the given paper (who refers to this work). Use when the user asks 'who cites X', 'what's the impact', or wants follow-up work. Note: 2024+ citation coverage is sparse; indexing in progress.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | arXiv ID or OpenAlex Work ID. |
| k | integer | — | Max citing papers (default 25, max 100). |
No output schema declared.
No examples provided.
get_entities ~87
Get the biomedical entities linked to a paper: genes, proteins, chemicals, diseases, species, mutations, cell lines, and clinical-trial (NCT) IDs. Accepts an arXiv ID, PMC ID, or bioRxiv/medRxiv DOI.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | arXiv ID, PMC ID, or 10.1101/… DOI. |
No output schema declared.
No examples provided.
get_figures ~82
Get a paper's real figure images — URLs, labels, and captions. Most biomedical papers have figures; arXiv papers often don't. Accepts an arXiv ID, PMC ID, or bioRxiv/medRxiv DOI.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | arXiv ID, PMC ID, or 10.1101/… DOI. |
No output schema declared.
No examples provided.
get_full_text ~103
Fetch a paper's full body text as Markdown (methods, results, protocols, inline tables) — use for deep questions the abstract can't answer. Accepts an arXiv ID (2401.12345), a PMC ID (PMC5339222), or a bioRxiv/medRxiv DOI (10.1101/…).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | arXiv ID, PMC ID, or 10.1101/… DOI. |
No output schema declared.
No examples provided.
get_paper ~149
Fetch a paper's full metadata: title, authors, year, abstract, TLDR (LLM-generated), key findings, citation count, GitHub repos, HuggingFace models/datasets, videos, peer reviews, and links. Accepts an arXiv ID (e.g. '2401.12345' or '1706.03762v5') or an OpenAlex Work ID (e.g. 'W4390723197'). Use when the user names a specific paper or pastes an arXiv link.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | arXiv ID like '2401.12345' or OpenAlex Work ID like 'W4390723197'. |
No output schema declared.
No examples provided.
get_structure ~91
Resolve a gene/protein name (e.g. 'TP53', 'CD44') or UniProt accession to its 3D structure — returns the UniProt accession + AlphaFold model URL (and PDB when available). Great for a gene named in a paper's entities.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Gene/protein symbol (TP53, CD44) or UniProt accession (P04637). |
No output schema declared.
No examples provided.
references ~69
Get the papers that this paper cites (its bibliography). Use when the user asks 'what does X cite' or 'show me the references'.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | arXiv ID or OpenAlex Work ID. |
| k | integer | — | Max references (default 25, max 100). |
No output schema declared.
No examples provided.
search_papers ~170
Search 8.5 million academic papers (arXiv + biomedical: PMC / bioRxiv / medRxiv, all disciplines) by topic, keyword, author, or linked entity (gene / protein / disease). Each hit returns id, title, TLDR, type, and links. Use to find papers about a topic, e.g. 'transformer efficiency' or 'CRISPR base editing'.
| Name | Type | Req | Description |
|---|---|---|---|
| k | integer | — | Number of results (default 10, max 25). |
| query | string | yes | Natural-language search query. E.g. 'transformer attention efficiency', 'graph neural networks for molecular property prediction'. |
| year_max | integer | — | Latest publication year. |
| year_min | integer | — | Earliest publication year, e.g. 2024. |
No output schema declared.
No examples provided.
similar_papers ~93
Find papers semantically similar to a given paper using SPECTER2 embeddings (trained on scientific-citation triplets). Returns nearest neighbors with TLDR. Use when the user wants 'papers like X' or 'what's adjacent to this work'.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | arXiv ID or OpenAlex Work ID. |
| k | integer | — | Number of neighbors (default 10, max 25). |
No output schema declared.
No examples provided.