Readout
REMOTE · READOUT-7PT.PAGES.DEV · SCANNED SEP 20
Measured readings on open-source dependencies: health, end-of-life, model prices, incidents.
Available components
Deprecated
This server is marked deprecated in the MCP registry.
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 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. 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 2011 tokens (~64/item across 31 items; 31 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 36% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 32 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 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.
remote · readout-7pt.pages.dev
claude mcp add --transport http kaitzyy-dev-readout 'https://readout-7pt.pages.dev/api/mcp'
{
"mcpServers": {
"kaitzyy-dev-readout": {
"url": "https://readout-7pt.pages.dev/api/mcp"
}
}
} {
"servers": {
"kaitzyy-dev-readout": {
"type": "http",
"url": "https://readout-7pt.pages.dev/api/mcp"
}
}
} [mcp_servers.kaitzyy-dev-readout] url = "https://readout-7pt.pages.dev/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kaitzyy-dev-readout": {
"type": "remote",
"url": "https://readout-7pt.pages.dev/api/mcp",
"enabled": true
}
}
} openclaw mcp add kaitzyy-dev-readout --url 'https://readout-7pt.pages.dev/api/mcp' --transport streamable-http
mcp_servers:
kaitzyy-dev-readout:
url: "https://readout-7pt.pages.dev/api/mcp" {
"McpServers": {
"kaitzyy-dev-readout": {
"Transport": "http",
"Url": "https://readout-7pt.pages.dev/api/mcp"
}
}
} assistant mcp add kaitzyy-dev-readout -t streamable-http -u 'https://readout-7pt.pages.dev/api/mcp'
{
"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.
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.
- 6 Sept 26 0
- Stability: 0.97 → pass security
- 5 Sept 26 +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.
- 3 Sept 26 +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.
- 1 Sept 26 +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.
- 30 Aug 26 +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.
- 27 Aug 26 +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.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +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.
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://readout-7pt.pages.dev/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=readout-7pt.pages.dev | CN=WE1,O=Google Trust Services,C=US | 5 Aug 2026 | 3 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | d2223beb6c6ca79613e75c9d6fbc7275 |
| SANs: readout-7pt.pages.dev, *.readout-7pt.pages.dev | ||||||
| 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 readout-7pt.pages.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| pages.dev. | 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://readout-7pt.pages.dev/api/mcp | Verified | 200 | |
| http (plaintext) | http://readout-7pt.pages.dev/api/mcp | HTTPS enforced | 301 | https://readout-7pt.pages.dev/api/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 →
advisory_severity ~59
Advisories broken down by severity rather than counted, with identifiers and dates. Requires a key; see https://sighttrue.com/pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name as the registry spells it. |
| registry | string | yes | – |
No output schema declared.
No examples provided.
audit_manifest ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | – |
| manifest | string | yes | – |
No output schema declared.
No examples provided.
base_image_check ~55
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.
| Name | Type | Req | Description |
|---|---|---|---|
| image | string | yes | – |
No output schema declared.
No examples provided.
check_before_install ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name as the registry spells it. |
| registry | string | yes | – |
No output schema declared.
No examples provided.
check_eol ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cycle | string | – | Release line, e.g. 3.9 or 20. Omit for every cycle. |
| product | string | yes | Product as endoflife.date spells it, e.g. python, nodejs, postgresql. |
No output schema declared.
No examples provided.
check_package ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name as the registry spells it. |
| registry | string | yes | – |
No output schema declared.
No examples provided.
check_provider ~64
Recorded incidents for a hosting or API provider over a window, kept after the provider’s own status page dropped them.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| provider | string | – | Provider slug, e.g. cloudflare, openai, github. Omit for every provider. |
No output schema declared.
No examples provided.
check_stack ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | – |
| registry | string | yes | – |
No output schema declared.
No examples provided.
compare_repositories ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | Repository as owner/name. |
| b | string | yes | Repository as owner/name. |
No output schema declared.
No examples provided.
diff_since ~57
What changed for a set of packages since a given date, read from the daily archive. Requires a key; see https://sighttrue.com/pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | – |
| since | string | yes | YYYY-MM-DD. |
No output schema declared.
No examples provided.
domain_risk ~65
Whether the domains a package points at — homepage, funding, documentation — still resolve to a registered owner. Requires a key; see https://sighttrue.com/pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name as the registry spells it. |
| registry | string | yes | – |
No output schema declared.
No examples provided.
explain_finding ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
find_model ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| maxPrice | number | – | Maximum USD per million prompt tokens. |
| minContext | integer | – | Minimum context window in tokens. |
| provider | string | – | – |
No output schema declared.
No examples provided.
funding_gap ~48
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
help_availability ~44
For a technology tag: questions asked against questions answered, over time. Requires a key; see https://sighttrue.com/pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| tag | string | yes | – |
No output schema declared.
No examples provided.
list_readings ~39
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
model_price_history ~44
Every recorded price for a model, with the date each was read. Requires a key; see https://sighttrue.com/pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | – |
No output schema declared.
No examples provided.
model_withdrawn ~41
Models that were in the catalogue and no longer are, with the date last seen. Requires a key; see https://sighttrue.com/pricing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
package_weight_history ~64
How the published artefact size has moved over time. Returns the readings taken, not a verdict. Requires a key; see https://sighttrue.com/pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name as the registry spells it. |
| registry | string | yes | – |
No output schema declared.
No examples provided.
provider_incidents ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | – |
No output schema declared.
No examples provided.
provider_terms_changed ~49
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.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | – | – |
No output schema declared.
No examples provided.
provider_transparency ~52
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.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | – | – |
No output schema declared.
No examples provided.
registry_health ~46
Recorded outages of the package registries themselves, kept after their status pages drop them. Requires a key; see https://sighttrue.com/pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| registry | string | – | – |
No output schema declared.
No examples provided.
runtime_deadlines ~47
Support end dates for the runtimes a dependency set requires, including any already past. Requires a key; see https://sighttrue.com/pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | – |
No output schema declared.
No examples provided.
search_repositories ~50
Find watched repositories whose name contains a string, with their current readings. Use it to discover what is covered before calling the other tools.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
time_to_fix ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name as the registry spells it. |
| registry | string | yes | – |
No output schema declared.
No examples provided.
typosquat_check ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name as the registry spells it. |
| registry | string | yes | – |
No output schema declared.
No examples provided.
watch_add ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name as the registry spells it. |
| registry | string | yes | – |
No output schema declared.
No examples provided.
watch_changes ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | – |
No output schema declared.
No examples provided.
who_can_publish ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name as the registry spells it. |
| registry | string | yes | – |
No output schema declared.
No examples provided.
withdrawn_but_installed ~57
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
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.