Paceword Speed Reader MCP server
io.github.theluckystrike/speed-readertheluckystrikestreamable-httpv1.0.0Scanned
Learn to read faster with paced speed reading practice inside the chat.
3 tools: 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Paceword Speed Reader MCP server can do
The Paceword Speed Reader MCP server is published by the GitHub account theluckystrike. It has 3 tools. It can create or change data (2 tools: estimate_reading_time and run_reading_speed_test), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 8, 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.
3 tools
Changes things 2Claude Code: ask
estimate_reading_timeUse this when the user needs a reading-time or speaking-time estimate from text or a word count.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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use this when the user needs a reading-time or speaking-time estimate from text or a word count. Accepts text up to 20,000 characters or 1 to 2,000,000 words, plus 100 to 1,000 wpm or a reader type. Returns a 150 to 800 wpm table; it does not assess reading ability.
Annotations the server declares
- title: Estimate reading time
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
run_reading_speed_testUse this when the user wants an original timed reading-speed practice test with comprehension questions.1 finding
Why it is in this group
- The name "run_reading_speed_test" says "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "run_reading_speed_test" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "run_reading_speed_test" says "run": a word for a change.
Description, as the server wrote it Use this when the user wants an original timed reading-speed practice test with comprehension questions. Accepts short, medium, or long passages only. Returns the passage length and four multiple-choice questions with four options each; correct options stay in widget-only metadata. Do not use for medical or learning-disability assessment.
Annotations the server declares
- title: Run reading speed test
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
Only reads 1Show 1 read-only tool
show_speed_readerUse this when the user wants to practice reading supplied text one word at a time.No findings
Why it is in this group
- The name "show_speed_reader" says "show": a word for reading.
Description, as the server wrote it Use this when the user wants to practice reading supplied text one word at a time. Accepts up to 20,000 characters, 100 to 1,000 words per minute, and 1 to 4 words per flash. Returns the word count and scheduled reading time; it is a training aid and does not measure comprehension.
Annotations the server declares
- title: Show speed reader
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
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 private-data or untrusted-input or outbound.
- Reads private data0
- 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 out0
- 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:35 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
- 2
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://speed-reader.zovo.one/mcp: tools/list returned 3 tools to an anonymous client, including estimate_reading_time (write), run_reading_speed_test (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "run_reading_speed_test" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "run_reading_speed_test" says "run": a word for a change.
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 speed-reader https://speed-reader.zovo.one/mcpclaude mcp add --transport http speed-reader https://speed-reader.zovo.one/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__speed-reader__show_speed_reader"
],
"ask": [
"mcp__speed-reader__estimate_reading_time",
"mcp__speed-reader__run_reading_speed_test"
],
"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 speed-reader. Review it before you use it.
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.theluckystrike/speed-reader/verify?hash=4f5040ee3f05f3beb34ff1a51d2c1769925c608e6c68877cb4771d4ca1865ef9" | jq -e '.changed == false'Pinned hash 4f5040ee3f05, from Nov 8, 2026, 13:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.theluckystrike/speed-reader/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.theluckystrike/speed-reader)Source: MCP Registry. Synced Oct 22, 2026, 06:20 UTC.
Paceword Speed Reader MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Paceword Speed Reader MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Paceword Speed Reader MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Paceword Speed Reader MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Paceword Speed Reader MCP server have?
- 3 tools: 2 write, 1 read. estimate_reading_time, run_reading_speed_test and show_speed_reader.
Does the Paceword Speed Reader MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Paceword Speed Reader MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Paceword Speed Reader MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.