MCP servers › io.github.WatermelonBros › reado

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.WatermelonBros/reado

Your code review comments from Reado, the read-first IDE, as context and tools for your agent. — the publisher's description

5 of 5 record checks metRead-only · tools listed 2026-10-23Topic: developer-tools · AI-classifiedPricing: open-source · AI-classifiedversion 1.34.0TypeScriptstandard input/output27 tools

Summary

io.github.WatermelonBros/reado is a local MCP server listed in the official MCP registry at version 1.34.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 27 tools, 6 resources and 0 prompts.

Record checks

5 of 5 record checks met · 4 do not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
met: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: not an npm or PyPI package
#1,504 of 22,952 repositories by GitHub stars, tied with 23 others

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: MCP bundle
Repository: public
Tools: 27
Described as changing data: 19 of 27 toolsAI-classified
Mainly works on: a web browser or desktop applicationsAI-classified
Topic: developer-toolsAI-classified
Pricing: open-sourceAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

19 tools are described as changing something (browser_eval, browser_navigate, browser_click, …): our AI model's reading of the descriptions, not something we tested. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

1.34.0, published 2026-10-19 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-09 (earliest version still in the registry; older removed versions would be earlier)

Version history

3 versions listed, 2026-10-09 to 2026-10-19; 3 in the 90 days before the 2026-10-23 snapshot.

Most recent 3 versions

1.34.0 · 2026-10-19
1.33.2 · 2026-10-09
1.33.1 · 2026-10-09

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.34.0 (published 2026-10-19).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

27tools

6resources

0prompts

What it mainly works on, as our AI model read its tool descriptions: a web browser or desktop applications.

19 of 27 tools are described as changing something (creating, editing, deleting, sending or running).

browser_consoleon 6 other serversreads or searches
“Read everything the preview page logged, as JSON: each entry's level (log/info/warn/error), message, source and stack.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
browser_networkon 7 other serversreads or searches
“Read the preview page's network activity, as JSON: method, URL, status and timing per request, with failures flagged.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
browser_errorson 1 other serverreads or searches
“Read only the preview's error-level console entries — errors and unhandled rejections — as JSON: the part of browser_console that answers "what broke?".”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
browser_evalon 8 other serversruns code or commandsdescribed as changing data
“Run a JavaScript expression in the preview page and answer its value, JSON-serialized.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
1 input, 1 required
- jsstringrequired“A JavaScript expression; wrap statements in an IIFE, e.g.”
browser_navigateon 29 other serverscontrols a browser or desktopdescribed as changing data
“Load a URL in the preview, replacing the current page.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
1 input, 1 required
- urlstringrequired“Absolute (`http://localhost:5173/settings`) or relative to the current page (`/settings`).”
browser_domreads or searches
“Inspect one element of the preview: its tag, outerHTML (first 2000 characters), box (x, y, width, height in CSS px, relative to the viewport) and key computed styles (display, color, background, font…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- selectorstringrequired“CSS selector; the first matching element is used (document.querySelector).”
browser_animationreads or searches
“Read the animations running on one element of the preview, as JSON: for each, its name, keyframes and computed timing (duration, delay, easing, progress).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- selectorstringrequired“CSS selector; the first matching element is used (document.querySelector).”
browser_clickon 30 other serverscontrols a browser or desktopdescribed as changing data
“Click an element in the preview: scrolls it to the middle of the viewport, then fires a DOM click().”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
1 input, 1 required
- selectorstringrequired“CSS selector; the first matching element is used (document.querySelector).”
browser_hoveron 16 other serverscontrols a browser or desktopdescribed as changing data
“Hover an element in the preview by dispatching mouseover and mouseenter — to open a menu or tooltip before inspecting it.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
1 input, 1 required
- selectorstringrequired“CSS selector; the first matching element is used (document.querySelector).”
browser_typeon 23 other serverscontrols a browser or desktopdescribed as changing data
“Fill a form field in the preview: focuses it, replaces its whole value with `text`, then fires input and change.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs, 2 required
- selectorstringrequired“CSS selector of an input, textarea or select; the first match is used.”
- textstringrequired“The field's new value.”
browser_scrollon 24 other serverscontrols a browser or desktopdescribed as changing data
“Scroll the preview's window to an absolute position (window.scrollTo) — to bring content into view before browser_frame.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs
- xnumber“CSS pixels from the document's left edge.”
- ynumber“CSS pixels from the document's top.”
browser_framereads or searches
“Screenshot the preview as it renders right now, answered as a PNG image.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.

Show 15 more tools

task_doneon 1 other servercreates or changes datadescribed as changing data
“Mark a task resolved once your change addresses it, recording how.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
4 inputs, 1 required
- diffRefstring“The commit or ref holding the change, e.g.”
- idstringrequired“The task's id, from `reado://tasks`.”
- modelstring“The model that made the change, for provenance.”
- verifystring“A shell command that proves the fix, e.g.”
task_failcreates or changes datadescribed as changing data
“Record a failed attempt at a task.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs, 1 required
- idstringrequired“The task's id, from `reado://tasks`.”
- notestring“What you tried and why it didn't work; posted as a reply in the task's thread, in Markdown.”
task_blockcreates or changes datadescribed as changing data
“Block a task you cannot finish without the human — a decision, a credential or context you don't have.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs, 2 required
- idstringrequired“The task's id, from `reado://tasks`.”
- reasonstringrequired“The question or missing piece, written for the human who has to answer it.”
comment_addon 2 other serverscreates or changes datadescribed as changing data
“Anchor a new comment to a line range, signed by the agent.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
6 inputs, 3 required
- bodystringrequired“The comment, in Markdown.”
- endinteger“Last line of the range, inclusive.”
- filestringrequired“Project-relative path, e.g.”
- kindstring“`task` asks for work (default); `note` only informs.”
- lineintegerrequired“First line of the range, 1-based.”
- typestring“What the comment is about.”
comment_replyon 1 other servercreates or changes datadescribed as changing data
“Reply in an existing comment's thread, signed by the agent — to answer a question the user asked, or to explain what you changed.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs, 2 required
- bodystringrequired“The reply, in Markdown.”
- idstringrequired“The comment's id, from `reado://comments` or `reado://tasks`.”
mascot_saysends messagesdescribed as changing data
“Say one line through Reado's mascot — the small companion in the corner of the user's screen.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs, 1 required
- moodstring“The mascot's expression.”
- textstringrequired“One line, at most 280 characters.”
session_donedescribed as changing data
“Call this when your next act is to wait for the user — the request is finished, you are blocked, or you need an answer.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs
- statusstring“How the request ended.”
- summarystring“One line on what happened; it becomes the notification's text.”
session_showreads or searches
“Read a guided-review session in full, as JSON: scope, objective, route, per-file state and summaries, proposals and their decisions, the files the scope is expected to contain, and any pending route …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- sessionIdstring“The session id from the READO GUIDED REVIEW prompt.”
review_contexton 5 other serversreads or searches
“Read one file's context in a guided review before reviewing it, as JSON: the session objective, the file's route entry (why it was ranked, related files), its state, its running summary and the propo…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- filestringrequired“Project-relative path, e.g.”
- sessionIdstring“The session id from the READO GUIDED REVIEW prompt.”
review_planon 3 other serverscreates or changes datadescribed as changing data
“Set a guided review's ranked route — the planning pass, once per session, before you review any file.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs, 1 required
- routearrayrequired“Every file to review, riskiest first.”
- sessionIdstring“The session id from the READO GUIDED REVIEW prompt.”
review_propose_route_changecreates or changes datadescribed as changing data
“Propose a new route for a guided review already under way — a file you found that must be reviewed, a reorder, a file to drop.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
3 inputs, 2 required
- reasonstringrequired“Why the route should change — what the human reads to decide.”
- routearrayrequired“The whole proposed route, not just what changes.”
- sessionIdstring“The session id from the READO GUIDED REVIEW prompt.”
review_propose_commentcreates or changes datadescribed as changing data
“Propose a finding on the code during a guided review — a bug, a refactor, a performance issue — anchored to a line range.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
6 inputs, 3 required
- bodystringrequired“The finding: what is wrong and why, in Markdown.”
- endinteger“Last line of the range, inclusive.”
- filestringrequired“Project-relative path, e.g.”
- lineintegerrequired“First line of the range, 1-based.”
- sessionIdstring“The session id from the READO GUIDED REVIEW prompt.”
- typestring“What the comment is about.”
review_proposecreates or changes datadescribed as changing data
“Propose a guided-review item that is not a finding on the code: a `question` for the human, a `follow-up` to do after the review, or `needs-context` when you cannot judge the code without information…”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
5 inputs, 2 required
- bodystringrequired“The question, follow-up or missing context, in Markdown.”
- filestring“Project-relative path it concerns, if any.”
- kindstringrequired“What you are raising.”
- lineinteger“Line it concerns, if any, 1-based.”
- sessionIdstring“The session id from the READO GUIDED REVIEW prompt.”
review_summarize_filecreates or changes datadescribed as changing data
“Record a file's mini-summary when you finish reviewing it in a guided review: what you checked, the risks you see, what comes next.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
3 inputs, 2 required
- filestringrequired“Project-relative path, e.g.”
- sessionIdstring“The session id from the READO GUIDED REVIEW prompt.”
- textstringrequired“The summary, a few lines, in Markdown.”
session_summarizecreates or changes datadescribed as changing data
“Record a guided review's overall recap once the routed files are done: what the review found, the risks that matter most, what is left.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- sessionIdstring“The session id from the READO GUIDED REVIEW prompt.”
- textstringrequired“The recap, in Markdown.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 27 tools
Says what it returns: 100% of 27 tools
States limits, defaults or errors: 0% of 27 tools
Says when to use it: 100% of 27 tools
Items covered per tool: 3.0 of 4 on average

Counted from the listing

Parameters with a description: 100% of 54
Tools with a description: 100% of 27
Typical description length: 373 characters

The tool set

Counted from the listing

Tools: 27
Size of the list: about 5,914 tokens for an agent to load (characters ÷ 4)
Naming: 27 of 27 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 27 of 27 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

No config: the MCP bundle is a file to install in a client that supports bundles, not a command.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Repository github.com/WatermelonBros/reado	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.WatermelonBros
GitHub owner: an organization (WatermelonBros)

Repository: github.com/WatermelonBros/reado
Stars: 30
Repository age: 91–180 days
Last push: 0–30 days ago
Archived: no
Security policy: SECURITY.md

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

5 of 5 record checks met · 4 do not apply

Not ranked by downloads: not an npm or PyPI package
#1,504 of 22,952 repositories by GitHub stars, tied with 23 others

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
Does not applyPackage names its licence with a standard (SPDX) identifierNot an npm or PyPI package.
Does not applyThe version the registry lists can be installed and is not withdrawnNot an npm or PyPI package.
Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
Does not applyNo known critical or high advisory in the package or its dependenciesNot an npm or PyPI package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.WatermelonBros/reado

Answered from the data above

Is io.github.WatermelonBros/reado safe to install?

We do not rate servers as safe or unsafe. 5 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 19 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is io.github.WatermelonBros/reado free to use?

Its website (reado.watermelon-studio.it/) describes a open-source pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Has io.github.WatermelonBros/reado been security tested?

Partly. 3 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.WatermelonBros/reado do?

It lists 27 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, send messages, run code or commands and control a browser or desktop. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.WatermelonBros/reado change or delete data?

19 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.WatermelonBros/reado publish a security policy?

Yes: its repository has a public security policy (github.com/watermelonbros/reado/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Where is the source code of io.github.WatermelonBros/reado?

In github.com/WatermelonBros/reado, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.callstack/agent-deviceagent-devicealso has tools that controls a browser or desktop, creates or changes data, runs code or commands, reads or searches, sends messagescompare with this one
io.github.A9T9/uivision-mcpUi.Vision MCPalso has tools that controls a browser or desktop, creates or changes data, runs code or commands, reads or searches, sends messagescompare with this one
io.github.tomyud1/godot-mcpalso has tools that controls a browser or desktop, creates or changes data, runs code or commands, reads or searches, sends messagescompare with this one
io.github.sapiom/mcpalso has tools that controls a browser or desktop, creates or changes data, runs code or commands, reads or searches, sends messagescompare with this one
io.github.iksnerd/adb-mcpadb-mcp: Android emulator and device control over adbalso has tools that controls a browser or desktop, creates or changes data, runs code or commands, reads or searches, sends messagescompare with this one
io.github.kivanccakmak/yaverYaveralso has tools that controls a browser or desktop, creates or changes data, runs code or commands, reads or searches, sends messagescompare with this one

Active servers whose topic is also “developer-tools” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

3 exercised9 not run (reason given)6 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised

Not run, with the reason · 9

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against

Does not apply to this server · 6

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
22 msConnected after 0 redirects.
Read the inventory: 27 tools, 6 resources, 0 prompts.
1,845 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

developer-tools

AI-classified · 2026-10-23

Pricing modelAI-classified

open-source

read from reado.watermelon-studio.it/ · 2026-10-23

“Free and open source · macOS, Windows, Linux · 2.1k downloads”

Programming language

TypeScript

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

resources, tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

mcpb

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here

Integrity hash

does not apply

package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here

Signature / provenance

does not apply

package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here

Dependency advisories

not checked

only npm and PyPI packages are audited

Popularity

does not apply

package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here

Publisher signals

owner: an organization · repository age: 91–180 days · stars: 10–99

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

your machine

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.WatermelonBros/reado: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.WatermelonBros/reado

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.WatermelonBros/reado)](https://protocolprobe.com/mcp/servers/io.github.WatermelonBros/reado)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology