slashyear — sourced history
REMOTE · SLASHYEAR.COM · SCANNED SEP 20
Sourced history: 85,753 dated events, each quoted from a citable Wikipedia revision id.
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 → Why this is hard to score →
Endpoint Security57
- 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 7 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
- 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 Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 639 tokens (~91/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the slashyear — sourced history MCP server?
slashyear — sourced history is a hosted endpoint at https://slashyear.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 · slashyear.com
claude mcp add --transport http com-slashyear-mcp 'https://slashyear.com/mcp'
{
"mcpServers": {
"com-slashyear-mcp": {
"url": "https://slashyear.com/mcp"
}
}
} {
"servers": {
"com-slashyear-mcp": {
"type": "http",
"url": "https://slashyear.com/mcp"
}
}
} [mcp_servers.com-slashyear-mcp] url = "https://slashyear.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-slashyear-mcp": {
"type": "remote",
"url": "https://slashyear.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-slashyear-mcp --url 'https://slashyear.com/mcp' --transport streamable-http
mcp_servers:
com-slashyear-mcp:
url: "https://slashyear.com/mcp" {
"McpServers": {
"com-slashyear-mcp": {
"Transport": "http",
"Url": "https://slashyear.com/mcp"
}
}
} assistant mcp add com-slashyear-mcp -t streamable-http -u 'https://slashyear.com/mcp'
{
"mcpServers": {
"com-slashyear-mcp": {
"type": "http",
"url": "https://slashyear.com/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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 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.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 0
- Schema quality: 486 → 639 ▼ functional
- Tool coverage: 75% → 82% ▲ functional
- Schema quality: excellent → good functional
- New tool “get_country” functional
- New tool “list_countries” functional
- 9 Sept 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.
- 8 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 7 Sept 26 63
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 20 Sept 2026 · Probed https://slashyear.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=slashyear.com | CN=WE1,O=Google Trust Services,C=US | 6 Sept 2026 | 5 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1e850b8e5bd5ec5113aa45b73c5b7d5e |
| SANs: slashyear.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 slashyear.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| slashyear.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://slashyear.com/mcp | Verified | 200 | |
| http (plaintext) | http://slashyear.com/mcp | HTTPS enforced | 301 | https://slashyear.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 →
get_country ~116
One country's dated record, century by century, harvested from the per-country year articles English Wikipedia writes separately ('1969 in Japan') and never indexes together. Use this when the question is about a nation rather than a year or a subject.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | country name or slug, e.g. 'Japan', 'south-africa' |
| from_year | integer | – | earliest year; astronomical numbering |
| limit | integer | – | default 200, max 2000 |
| to_year | integer | – | latest year |
No output schema declared.
No examples provided.
get_day ~65
One calendar day across every recorded year — what happened on 4 July in all of them. This aggregate exists in no single encyclopedia article.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | 'july-4', 'July 4', '07-04' or any 'YYYY-MM-DD' |
No output schema declared.
No examples provided.
get_timeline ~104
One subject's whole record in date order: every dated entry across all years in which Wikipedia's editors linked to it, with its Wikidata id for joining to other datasets.
| Name | Type | Req | Description |
|---|---|---|---|
| from_year | integer | – | – |
| limit | integer | – | default 100, max 1000 |
| subject | string | yes | subject name or slug, e.g. 'Byzantine Empire' or 'byzantine-empire' |
| to_year | integer | – | – |
No output schema declared.
No examples provided.
get_year ~55
Everything the record holds for one year: the headline summary and every dated entry, grouped by subject, each with its source revision.
| Name | Type | Req | Description |
|---|---|---|---|
| year | integer | yes | astronomical numbering: 1969, or -43 for 44 BCE |
No output schema declared.
No examples provided.
list_countries ~37
Browse the countries that have a record of their own, largest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | default 100, max 500 |
No output schema declared.
No examples provided.
list_subjects ~43
Browse the subjects that have a timeline, largest record first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | default 50, max 500 |
| starts_with | string | – | – |
No output schema declared.
No examples provided.
search_history ~150
Full-text search across every dated entry in the historical record, plus the subjects that match. Each entry is a sentence quoted verbatim from a numbered English Wikipedia revision and carries that revision id, so an answer built on it can cite a source that will still say the same thing next year. Use this whenever you need a dated fact.
| Name | Type | Req | Description |
|---|---|---|---|
| from_year | integer | – | earliest year; astronomical numbering, so -43 means 44 BCE |
| limit | integer | – | maximum entries to return (default 25, max 200) |
| query | string | yes | words to find, e.g. 'volcanic eruption' or 'Constantinople' |
| to_year | integer | – | latest year |
No output schema declared.
No examples provided.
What is the slashyear — sourced history MCP server?
slashyear — sourced history is an MCP server listed in the public MCP registry as com.slashyear/mcp. Sourced history: 85,753 dated events, each quoted from a citable Wikipedia revision id. This page covers its hosted endpoint (https://slashyear.com/mcp).
Is the slashyear — sourced history MCP server safe to use?
slashyear — sourced history scores 68 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 slashyear — sourced history MCP server expose?
slashyear — sourced history exposes 7 tools: search_history, get_year, get_day, get_timeline, get_country, and 2 more. Their descriptions and schemas cost roughly 570 tokens of context every time the server is loaded.
Does the slashyear — sourced history MCP server require authentication?
No. We connected to slashyear — sourced history without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the slashyear — sourced history MCP server still maintained?
slashyear — sourced history is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.