# lastseen score (remote · score.lastseen.dev)

Trust scores and dated liveness/drift facts for MCP servers, from the lastseen.dev register.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- remote · `score.lastseen.dev`: 65/100 (this document), [markdown](https://verifymcp.io/servers/dev-lastseen-score/score.md), [page](https://verifymcp.io/servers/dev-lastseen-score/score)

## Channel facts

- Endpoint: `https://score.lastseen.dev/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-08-20.

- **Endpoint Security**: 63/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 3 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.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 235 tokens (~78/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http dev-lastseen-score https://score.lastseen.dev/mcp
```

### Codex

```toml
[mcp_servers.dev-lastseen-score]
url = "https://score.lastseen.dev/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dev-lastseen-score --url https://score.lastseen.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-lastseen-score:
    url: "https://score.lastseen.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "dev-lastseen-score": {
      "type": "http",
      "url": "https://score.lastseen.dev/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-08-19 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-18 (score 64)

First indexed and scored.

## MCP tools (3)

### `trust_score` (~129 tokens)

Derived trust score (0-100) for an MCP server, computed from the lastseen.dev register's dated observations by a published method. The score carries DEPTH (how many of 5 dimensions were computable) BOUND INTO the number as `display`, e.g. '80 · depth 2/5 · provisional' — a depth-2 score answers a narrower question (mortality, not merit). Not a prediction, not advice. Methodology: score.lastseen.dev/methodology.

Input parameters:

- `id` (string, required): MCP schema-server identifier, e.g. io.github.owner/name

### `schema_history` (~57 tokens)

Dated schema/tool-count observations for an MCP server (a series when known): first_seen, last_observed, drift events. Facts from the register, not a score.

Input parameters:

- `id` (string, required): e.g. io.github.owner/name

### `dependency_risk` (~49 tokens)

An MCP server's dependencies and their mortality state (dead/dormant counts) from the register. Facts, not a score.

Input parameters:

- `id` (string, required): e.g. io.github.owner/name

## Diagnostics

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

## Score history

- 2026-08-20: 65
- 2026-08-19: 65
- 2026-08-18: 64

## Links

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