Readout MCP server
io.github.kaitzyy-dev/readoutkaitzyy-devstreamable-httpv1.0.0Scanned
Measured readings on open-source dependencies: health, end-of-life, model prices, incidents.
31 tools: 1 do something that can't be undone, 21 change things and 9 only read.
- Reads private data · 3
- Reads text others write · 0
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
22 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Readout MCP server can do
The Readout MCP server is published by the GitHub account kaitzyy-dev. It has 31 tools. It can do things that cannot be undone, such as sending, paying or publishing (who_can_publish) and create or change data (21 tools: check_before_install, check_eol, check_provider, package_weight_history and 17 more), but cannot delete data. 9 tools only read.
3 tools read private data (check_package, search_repositories and compare_repositories); 1 tool can send data out of your system (who_can_publish).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
31 tools
Can't be undone 1Claude Code: ask
who_can_publishHow many accounts hold publish rights on a package, as the registry lists them.Can send data outNo findings
Why it is in this group
- The name "who_can_publish" says "publish": a word for a change that another call does not undo.
What it can reach
- outboundThe name "who_can_publish" says "publish": it sends or publishes something to other people.
Description, as the server wrote it 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.
Changes things 21Claude Code: ask
advisory_severityAdvisories broken down by severity rather than counted, with identifiers and dates.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Advisories broken down by severity rather than counted, with identifiers and dates. Requires a key; see https://sighttrue.com/pricing.
base_image_checkFor a container base image: its size, when it was last rebuilt, and whether the OS underneath it is still supported.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
check_before_installCall this before adding a dependency.No findings
Why it is in this group
- The name "check_before_install" says "install": a word for a change.
Description, as the server wrote it 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.
check_eolCheck whether a runtime, database or framework release is still receiving security fixes, and what to move to.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
check_providerRecorded incidents for a hosting or API provider over a window, kept after the provider’s own status page dropped them.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Recorded incidents for a hosting or API provider over a window, kept after the provider’s own status page dropped them.
domain_riskWhether the domains a package points at — homepage, funding, documentation — still resolve to a registered owner.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Whether the domains a package points at — homepage, funding, documentation — still resolve to a registered owner. Requires a key; see https://sighttrue.com/pricing.
funding_gapPackages that ask for funding, beside how heavily they are installed and how many people write them.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
help_availabilityFor a technology tag: questions asked against questions answered, over time.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it For a technology tag: questions asked against questions answered, over time. Requires a key; see https://sighttrue.com/pricing.
model_price_historyEvery recorded price for a model, with the date each was read.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Every recorded price for a model, with the date each was read. Requires a key; see https://sighttrue.com/pricing.
model_withdrawnModels that were in the catalogue and no longer are, with the date last seen.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Models that were in the catalogue and no longer are, with the date last seen. Requires a key; see https://sighttrue.com/pricing.
package_weight_historyHow the published artefact size has moved over time.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it How the published artefact size has moved over time. Returns the readings taken, not a verdict. Requires a key; see https://sighttrue.com/pricing.
provider_incidentsA provider’s recorded incidents, grouped by the component that failed, over the whole archive rather than the window its status page shows.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
provider_terms_changedWhen a provider last changed its terms or pricing page, from a stored fingerprint of the page.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
provider_transparencyHow long a provider takes to acknowledge an incident: the interval between an incident starting and its first public update.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
registry_healthRecorded outages of the package registries themselves, kept after their status pages drop them.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Recorded outages of the package registries themselves, kept after their status pages drop them. Requires a key; see https://sighttrue.com/pricing.
runtime_deadlinesSupport end dates for the runtimes a dependency set requires, including any already past.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Support end dates for the runtimes a dependency set requires, including any already past. Requires a key; see https://sighttrue.com/pricing.
time_to_fixDays between an advisory being published and a release appearing that postdates it, per package and as a distribution.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
typosquat_checkWhether a name is one edit away from a more widely installed package.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
watch_addAdd a package to the caller’s own private watchlist, so later readings are about their stack rather than the public one.No findings
Why it is in this group
- The name "watch_add" says "add": a word for a change.
Description, as the server wrote it 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.
watch_changesEverything that has changed across the caller’s private watchlist since a given date: withdrawals, licence changes, advisories, archived repositories and runtimes going out of supp…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
withdrawn_but_installedPackages whose own publisher has withdrawn them and which are still being installed heavily, with the download figure and the publisher’s notice.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 9Show 9 read-only tools
audit_manifestRead a whole manifest and return every reading on record for it, ordered by how much a reviewer would want to know.No findings
Why it is in this group
- The description's first verb is "read": a word for reading.
Description, as the server wrote it 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.
check_packageRead 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…Reads private dataNo findings
Why it is in this group
- The description's first verb is "read": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "repository": it reads repositories.
Description, as the server wrote it 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.
check_stackRead 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.No findings
Why it is in this group
- The description's first verb is "read": a word for reading.
Description, as the server wrote it 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.
compare_repositoriesHold two watched repositories against each other across downloads, OpenSSF scorecard, advisories, forks, stars and findings on record.Reads private dataNo findings
Why it is in this group
- The name "compare_repositories" says "compare": a word for reading.
What it can reach
- private-dataThe name "compare_repositories" says "compare" and "repository": it reads repositories.
- private-dataThe description's first sentence says "repository": it reads repositories.
Description, as the server wrote it 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.
diff_sinceWhat changed for a set of packages since a given date, read from the daily archive.No findings
Why it is in this group
- The name "diff_since" says "diff": a word for reading.
Description, as the server wrote it What changed for a set of packages since a given date, read from the daily archive. Requires a key; see https://sighttrue.com/pricing.
explain_findingGiven a finding id, return what was measured, when, by whom, and the address it can be checked at.No findings
Why it is in this group
- The name "explain_finding" says "explain": a word for reading.
Description, as the server wrote it 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.
find_modelFind language models by price and context window, from a catalogue read daily across sixty providers.No findings
Why it is in this group
- The name "find_model" says "find": a word for reading.
Description, as the server wrote it 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.
list_readingsList every reading this server can return, what each one measures, and which require a key.No findings
Why it is in this group
- The name "list_readings" says "list": a word for reading.
Description, as the server wrote it 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.
search_repositoriesFind watched repositories whose name contains a string, with their current readings.Reads private dataNo findings
Why it is in this group
- The name "search_repositories" says "search": a word for reading.
What it can reach
- private-dataThe name "search_repositories" says "search" and "repository": it reads repositories.
- private-dataThe description's first sentence says "find" and "repository": it reads repositories.
Description, as the server wrote it Find watched repositories whose name contains a string, with their current readings. Use it to discover what is covered before calling the other tools.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:06 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 22
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 22 tools that change things (1 irreversible, 21 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://readout-7pt.pages.dev/api/mcp: tools/list returned 31 tools to an anonymous client, including who_can_publish (irreversible), check_before_install (write), check_eol (write), check_provider (write), package_weight_history (write) and 17 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http readout https://readout-7pt.pages.dev/api/mcpclaude mcp add --transport http readout https://readout-7pt.pages.dev/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__readout__check_package",
"mcp__readout__check_stack",
"mcp__readout__search_repositories",
"mcp__readout__compare_repositories",
"mcp__readout__find_model",
"mcp__readout__list_readings",
"mcp__readout__audit_manifest",
"mcp__readout__diff_since",
"mcp__readout__explain_finding"
],
"ask": [
"mcp__readout__check_before_install",
"mcp__readout__check_eol",
"mcp__readout__check_provider",
"mcp__readout__who_can_publish",
"mcp__readout__package_weight_history",
"mcp__readout__withdrawn_but_installed",
"mcp__readout__typosquat_check",
"mcp__readout__funding_gap",
"mcp__readout__time_to_fix",
"mcp__readout__advisory_severity",
"mcp__readout__runtime_deadlines",
"mcp__readout__base_image_check",
"mcp__readout__registry_health",
"mcp__readout__provider_incidents",
"mcp__readout__provider_transparency",
"mcp__readout__provider_terms_changed",
"mcp__readout__model_price_history",
"mcp__readout__model_withdrawn",
"mcp__readout__help_availability",
"mcp__readout__watch_add",
"mcp__readout__watch_changes",
"mcp__readout__domain_risk"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as readout. Review it before you use it.
Capability tags behind 4 rules
- mcp__readout__check_package private-data
- mcp__readout__search_repositories private-data
- mcp__readout__compare_repositories private-data
- mcp__readout__who_can_publish outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.kaitzyy-dev/readout/verify?hash=8476c9b2cc603e00eafa1a1198f54e01bca21a47b9f8fb18a27e0d6b2e520740" | jq -e '.changed == false'Pinned hash 8476c9b2cc60, from Nov 19, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.kaitzyy-dev/readout/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.kaitzyy-dev/readout)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:37 UTC.
Readout MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Readout MCP server safe?
- No scan can promise that. What its definitions show: 31 tools, 22 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Readout MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Readout MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: who_can_publish.
What tools does the Readout MCP server have?
- 31 tools: 1 irreversible, 21 write, 9 read. who_can_publish, check_before_install, check_eol, check_provider, package_weight_history, withdrawn_but_installed, typosquat_check, funding_gap and 23 more.
Does the Readout MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Readout MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): who_can_publish.
Has the Readout MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.