# slashyear — sourced history (remote · slashyear.com)

Sourced history: 85,753 dated events, each quoted from a citable Wikipedia revision id.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `slashyear.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-slashyear-mcp/slashyear.md), [page](https://verifymcp.io/servers/com-slashyear-mcp/slashyear)

## Channel facts

- Endpoint: `https://slashyear.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 639 tokens (~91/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-slashyear-mcp 'https://slashyear.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-slashyear-mcp": {
      "url": "https://slashyear.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-slashyear-mcp": {
      "type": "http",
      "url": "https://slashyear.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-slashyear-mcp]
url = "https://slashyear.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-slashyear-mcp": {
      "type": "remote",
      "url": "https://slashyear.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-slashyear-mcp --url 'https://slashyear.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-slashyear-mcp:
    url: "https://slashyear.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-slashyear-mcp": {
      "Transport": "http",
      "Url": "https://slashyear.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-slashyear-mcp -t streamable-http -u 'https://slashyear.com/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-18 (score 68, +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.

### 2026-09-16 (score 67, +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.

### 2026-09-14 (score 66, +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.

### 2026-09-12 (score 65, +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.

### 2026-09-10 (score 64, 0)

- [functional regression] Schema quality: 486 → 639
- [functional improvement] Tool coverage: 75% → 82%
- [functional] Schema quality: excellent → good
- [functional] New tool “get_country”
- [functional] New tool “list_countries”

### 2026-09-09 (score 64, +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.

### 2026-09-08 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-07 (score 63)

First indexed and scored.

## MCP tools (7)

### `search_history` (~150 tokens)

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.

Input parameters:

- `from_year` (integer): earliest year; astronomical numbering, so -43 means 44 BCE
- `limit` (integer): maximum entries to return (default 25, max 200)
- `query` (string, required): words to find, e.g. 'volcanic eruption' or 'Constantinople'
- `to_year` (integer): latest year

### `get_year` (~55 tokens)

Everything the record holds for one year: the headline summary and every dated entry, grouped by subject, each with its source revision.

Input parameters:

- `year` (integer, required): astronomical numbering: 1969, or -43 for 44 BCE

### `get_day` (~65 tokens)

One calendar day across every recorded year — what happened on 4 July in all of them. This aggregate exists in no single encyclopedia article.

Input parameters:

- `date` (string, required): 'july-4', 'July 4', '07-04' or any 'YYYY-MM-DD'

### `get_timeline` (~104 tokens)

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.

Input parameters:

- `from_year` (integer)
- `limit` (integer): default 100, max 1000
- `subject` (string, required): subject name or slug, e.g. 'Byzantine Empire' or 'byzantine-empire'
- `to_year` (integer)

### `get_country` (~116 tokens)

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.

Input parameters:

- `country` (string, required): 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

### `list_countries` (~37 tokens)

Browse the countries that have a record of their own, largest first.

Input parameters:

- `limit` (integer): default 100, max 500

### `list_subjects` (~43 tokens)

Browse the subjects that have a timeline, largest record first.

Input parameters:

- `limit` (integer): default 50, max 500
- `starts_with` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-slashyear-mcp/slashyear#diagnostics

## Score history

- 2026-09-20: 68
- 2026-09-19: 68
- 2026-09-18: 68
- 2026-09-17: 67
- 2026-09-16: 67
- 2026-09-15: 66
- 2026-09-14: 66
- 2026-09-13: 65
- 2026-09-12: 65
- 2026-09-11: 64
- 2026-09-10: 64
- 2026-09-09: 64
- 2026-09-08: 63
- 2026-09-07: 63

## Common questions

### 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.

## Links

- Remote endpoint: https://slashyear.com/mcp
- Website: https://slashyear.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-slashyear-mcp/slashyear.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-slashyear-mcp/slashyear.json
- HTML version of this page: https://verifymcp.io/servers/com-slashyear-mcp/slashyear