SourceToMe
REMOTE · SOURCETOME-PUBLIC.ONRENDER.COM
Search and cite passages from a vetted, rights-cleared reference library.
Available components
Last scanned (21 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Education and Research
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 → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 419 tokens (~83/item across 5 items; 5 tools + 0 resources), lean.Pass
- 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 17 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Oct 26 67
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 17 Oct 2026 · Probed https://sourcetome-public.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sourcetome-public.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sourcetome-public.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://sourcetome-public.onrender.com/mcp | HTTPS enforced | 301 | https://sourcetome-public.onrender.com/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. 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 →
explain_evidence Explain evidence coverage ~57
Recompute evidence selection for a question and explain Strong, Limited or Insufficient heuristic coverage. Edition duplicates cannot inflate independent support. This explains selection, not factual correctness.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
| source_ids | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string | yes | – |
| error_code | – | – | – |
| evidence_ids | array | yes | – |
| independent_works | integer | yes | – |
| limitations | array | yes | – |
| notice | string | – | – |
| reason | string | yes | – |
| selection_basis | string | yes | – |
| status | string | yes | – |
No examples provided.
find_evidence_gaps Identify missing evidence ~60
Identify corpus limitations and kinds of evidence needed for an unsupported question. No web search, acquisition, factual answer generation or personalized advice; suggestions are gaps, never retrieved evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
| source_ids | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| available_source_ids | array | yes | – |
| coverage | string | yes | – |
| error_code | – | – | – |
| missing_evidence | array | yes | – |
| notice | string | – | – |
| reason | string | yes | – |
| status | string | yes | – |
No examples provided.
inspect_source Inspect source and edition ~49
Inspect one public source ID returned by search: work, edition, translator, public catalog, transcription fingerprint and complete indexed locator inventory. Cannot inspect private or arbitrary sources.
| Name | Type | Req | Description |
|---|---|---|---|
| source_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| error_code | – | – | – |
| notice | string | – | – |
| reason | string | yes | – |
| source | – | – | – |
| status | string | yes | – |
No examples provided.
retrieve_evidence Retrieve source evidence ~77
Return passages, edition, locator and provenance from the bounded public library. To request an exact indexed locator, provide one source ID and that full locator. Multiple IDs permit edition comparison; missing evidence is reported.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| locator | – | – | – |
| question | string | yes | – |
| source_ids | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string | – | – |
| error_code | – | – | – |
| evidence | array | – | – |
| independent_works | integer | – | – |
| limitations | array | – | – |
| notice | string | – | – |
| reason | string | yes | – |
| status | string | yes | – |
No examples provided.
search_library Search public reference library ~83
Find passages in the public reference library: Pride and Prejudice, Frankenstein 1818/1831 and The Art of War (Giles). Includes the four available sources with stable IDs for follow-up even when no passage matches; no personal library or internet search.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| source_ids | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| available_sources | array | – | – |
| error_code | – | – | – |
| hits | array | – | – |
| notice | string | – | – |
| reason | string | yes | – |
| status | string | yes | – |
No examples provided.
How do I install the SourceToMe MCP server?
SourceToMe is a hosted endpoint at https://sourcetome-public.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · sourcetome-public.onrender.com
claude mcp add --transport http kylelloyd63-star-sourcetome 'https://sourcetome-public.onrender.com/mcp'
What is the SourceToMe MCP server?
SourceToMe is an MCP server listed in the public MCP registry as io.github.kylelloyd63-star/sourcetome. Search and cite passages from a vetted, rights-cleared reference library. This page covers its hosted endpoint (https://sourcetome-public.onrender.com/mcp).
Is the SourceToMe MCP server safe to use?
SourceToMe scores 67 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 SourceToMe MCP server expose?
SourceToMe exposes 5 tools: search_library, retrieve_evidence, inspect_source, explain_evidence, find_evidence_gaps. Their descriptions and schemas cost roughly 326 tokens of context every time the server is loaded.
Does the SourceToMe MCP server require authentication?
No. We connected to SourceToMe without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SourceToMe MCP server still maintained?
SourceToMe is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.