# Readout (remote · readout-7pt.pages.dev)

Measured readings on open-source dependencies: health, end-of-life, model prices, incidents.

- Trust score: 74/100 (medium)
- Change this week: 0
- Registry status: deprecated
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

> **Deprecated**: this server is marked deprecated in the MCP registry.

## Components

- remote · `readout-7pt.pages.dev`: 74/100 (this document), [markdown](https://verifymcp.io/servers/kaitzyy-dev-readout/api-mcp.md), [page](https://verifymcp.io/servers/kaitzyy-dev-readout/api-mcp)

## Channel facts

- Endpoint: `https://readout-7pt.pages.dev/api/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 31 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**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 2011 tokens (~64/item across 31 items; 31 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 79/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 36% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "who_can_publish" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 32 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 Readout MCP server?

Readout is a hosted endpoint at https://readout-7pt.pages.dev/api/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 kaitzyy-dev-readout 'https://readout-7pt.pages.dev/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "kaitzyy-dev-readout": {
      "url": "https://readout-7pt.pages.dev/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kaitzyy-dev-readout": {
      "type": "http",
      "url": "https://readout-7pt.pages.dev/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.kaitzyy-dev-readout]
url = "https://readout-7pt.pages.dev/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kaitzyy-dev-readout": {
      "type": "remote",
      "url": "https://readout-7pt.pages.dev/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kaitzyy-dev-readout --url 'https://readout-7pt.pages.dev/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  kaitzyy-dev-readout:
    url: "https://readout-7pt.pages.dev/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "kaitzyy-dev-readout": {
      "Transport": "http",
      "Url": "https://readout-7pt.pages.dev/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add kaitzyy-dev-readout -t streamable-http -u 'https://readout-7pt.pages.dev/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "kaitzyy-dev-readout": {
      "type": "http",
      "url": "https://readout-7pt.pages.dev/api/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-06 (score 74, 0)

- [security] Stability: 0.97 → pass

### 2026-09-05 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-03 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-01 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-30 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-27 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-26 (score 69, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-25 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (31)

### `check_before_install` (~125 tokens)

Call this before adding a dependency. Returns only the facts a reviewer would be annoyed to discover afterwards: whether the publisher has withdrawn the package, whether it runs scripts on the installing machine, whether its repository is archived, how many advisories are on record, whether the licence is source-available, and how long since it was actually published. Each fact carries the address of the body that published it. It does not say whether to install; it says what is on record.

Input parameters:

- `name` (string, required): Package name as the registry spells it.
- `registry` (string, required)

### `check_package` (~70 tokens)

Read the current standing of one open-source package: downloads with the window they cover, OpenSSF scorecard, advisory count, licence, whether the repository is archived, and when it was last pushed to.

Input parameters:

- `name` (string, required): Package name as the registry spells it.
- `registry` (string, required)

### `check_stack` (~79 tokens)

Read a whole dependency list at once and report what is archived, what carries advisories, what has a source-available licence, and what has not been pushed to in a year. Use when reviewing a package.json, requirements.txt, Cargo.toml, composer.json or Gemfile.

Input parameters:

- `names` (array, required)
- `registry` (string, required)

### `search_repositories` (~50 tokens)

Find watched repositories whose name contains a string, with their current readings. Use it to discover what is covered before calling the other tools.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `compare_repositories` (~68 tokens)

Hold two watched repositories against each other across downloads, OpenSSF scorecard, advisories, forks, stars and findings on record. Compares only; it does not pick a winner.

Input parameters:

- `a` (string, required): Repository as owner/name.
- `b` (string, required): Repository as owner/name.

### `find_model` (~84 tokens)

Find language models by price and context window, from a catalogue read daily across sixty providers. Use this before choosing a model: prices move without announcement and training data is out of date on the day it ships.

Input parameters:

- `maxPrice` (number): Maximum USD per million prompt tokens.
- `minContext` (integer): Minimum context window in tokens.
- `provider` (string)

### `check_eol` (~95 tokens)

Check whether a runtime, database or framework release is still receiving security fixes, and what to move to. Covers about two dozen products read daily from endoflife.date.

Input parameters:

- `cycle` (string): Release line, e.g. 3.9 or 20. Omit for every cycle.
- `product` (string, required): Product as endoflife.date spells it, e.g. python, nodejs, postgresql.

### `check_provider` (~64 tokens)

Recorded incidents for a hosting or API provider over a window, kept after the provider’s own status page dropped them.

Input parameters:

- `days` (integer)
- `provider` (string): Provider slug, e.g. cloudflare, openai, github. Omit for every provider.

### `list_readings` (~39 tokens)

List every reading this server can return, what each one measures, and which require a key. Call this first if unsure which tool answers a question.

### `who_can_publish` (~79 tokens)

How many accounts hold publish rights on a package, as the registry lists them. Answers who can put code on your machine, which is a different question from who writes it. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `name` (string, required): Package name as the registry spells it.
- `registry` (string, required)

### `package_weight_history` (~64 tokens)

How the published artefact size has moved over time. Returns the readings taken, not a verdict. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `name` (string, required): Package name as the registry spells it.
- `registry` (string, required)

### `withdrawn_but_installed` (~57 tokens)

Packages whose own publisher has withdrawn them and which are still being installed heavily, with the download figure and the publisher’s notice. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `limit` (integer)

### `typosquat_check` (~75 tokens)

Whether a name is one edit away from a more widely installed package. States that both names exist; which one was meant is the caller’s call. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `name` (string, required): Package name as the registry spells it.
- `registry` (string, required)

### `funding_gap` (~48 tokens)

Packages that ask for funding, beside how heavily they are installed and how many people write them. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `limit` (integer)

### `time_to_fix` (~66 tokens)

Days between an advisory being published and a release appearing that postdates it, per package and as a distribution. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `name` (string, required): Package name as the registry spells it.
- `registry` (string, required)

### `advisory_severity` (~59 tokens)

Advisories broken down by severity rather than counted, with identifiers and dates. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `name` (string, required): Package name as the registry spells it.
- `registry` (string, required)

### `runtime_deadlines` (~47 tokens)

Support end dates for the runtimes a dependency set requires, including any already past. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `names` (array, required)

### `base_image_check` (~55 tokens)

For a container base image: its size, when it was last rebuilt, and whether the OS underneath it is still supported. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `image` (string, required)

### `registry_health` (~46 tokens)

Recorded outages of the package registries themselves, kept after their status pages drop them. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `registry` (string)

### `provider_incidents` (~56 tokens)

A provider’s recorded incidents, grouped by the component that failed, over the whole archive rather than the window its status page shows. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `provider` (string, required)

### `provider_transparency` (~52 tokens)

How long a provider takes to acknowledge an incident: the interval between an incident starting and its first public update. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `provider` (string)

### `provider_terms_changed` (~49 tokens)

When a provider last changed its terms or pricing page, from a stored fingerprint of the page. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `provider` (string)

### `model_price_history` (~44 tokens)

Every recorded price for a model, with the date each was read. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `model` (string, required)

### `model_withdrawn` (~41 tokens)

Models that were in the catalogue and no longer are, with the date last seen. Requires a key; see https://sighttrue.com/pricing.

### `help_availability` (~44 tokens)

For a technology tag: questions asked against questions answered, over time. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `tag` (string, required)

### `audit_manifest` (~68 tokens)

Read a whole manifest and return every reading on record for it, ordered by how much a reviewer would want to know. One call instead of one per dependency. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `filename` (string)
- `manifest` (string, required)

### `diff_since` (~57 tokens)

What changed for a set of packages since a given date, read from the daily archive. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `names` (array, required)
- `since` (string, required): YYYY-MM-DD.

### `watch_add` (~79 tokens)

Add a package to the caller’s own private watchlist, so later readings are about their stack rather than the public one. The list is private to the key that created it. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `name` (string, required): Package name as the registry spells it.
- `registry` (string, required)

### `watch_changes` (~63 tokens)

Everything that has changed across the caller’s private watchlist since a given date: withdrawals, licence changes, advisories, archived repositories and runtimes going out of support. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `since` (string)

### `explain_finding` (~64 tokens)

Given a finding id, return what was measured, when, by whom, and the address it can be checked at. For an agent quoting a figure into a review. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `id` (string, required)

### `domain_risk` (~65 tokens)

Whether the domains a package points at — homepage, funding, documentation — still resolve to a registered owner. Requires a key; see https://sighttrue.com/pricing.

Input parameters:

- `name` (string, required): Package name as the registry spells it.
- `registry` (string, required)

## Diagnostics

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

## Score history

- 2026-09-20: 74
- 2026-09-19: 74
- 2026-09-18: 74
- 2026-09-17: 74
- 2026-09-16: 74
- 2026-09-15: 74
- 2026-09-14: 74
- 2026-09-13: 74
- 2026-09-12: 74
- 2026-09-11: 74
- 2026-09-10: 74
- 2026-09-09: 74
- 2026-09-08: 74
- 2026-09-07: 74
- 2026-09-06: 74
- 2026-09-05: 74
- 2026-09-04: 73
- 2026-09-03: 73
- 2026-09-02: 72
- 2026-09-01: 72
- 2026-08-31: 71
- 2026-08-30: 71
- 2026-08-29: 70
- 2026-08-28: 70
- 2026-08-27: 70
- 2026-08-26: 69
- 2026-08-25: 69
- 2026-08-24: 68
- 2026-08-23: 67
- 2026-08-22: 67

## Common questions

### What is the Readout MCP server?

Readout is an MCP server listed in the public MCP registry as io.github.kaitzyy-dev/readout. Measured readings on open-source dependencies: health, end-of-life, model prices, incidents. This page covers its hosted endpoint (https://readout-7pt.pages.dev/api/mcp).

### Is the Readout MCP server safe to use?

Readout scores 74 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 Readout MCP server expose?

Readout exposes 31 tools: check_before_install, check_package, check_stack, search_repositories, compare_repositories, and 26 more. Their descriptions and schemas cost roughly 1,952 tokens of context every time the server is loaded.

### Does the Readout MCP server require authentication?

No. We connected to Readout without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Readout MCP server still maintained?

Readout is marked deprecated 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://readout-7pt.pages.dev/api/mcp
- Repository: https://github.com/kaitzyy-dev/readout
- Website: https://readout-7pt.pages.dev/
- Changelog RSS feed: https://verifymcp.io/servers/kaitzyy-dev-readout/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/kaitzyy-dev-readout/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/kaitzyy-dev-readout/api-mcp