eyestill
Registry code: d53f7e4405e633d4
EyeStill opens web pages, public-domain books and text from the conversation in a speed reader view (read_with_eyestill).
- endpoint
- https://eyestill.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is eyestill live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is eyestill free to use?
- Not measured yet.
- What tools does eyestill have?
- 2 tools: eyestill_fetch_text, read_with_eyestill.
- Is eyestill safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 2 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
eyestill_fetch_text unknown 1h ago
Used by the EyeStill reader view to load the text of a page or book, or its next part.
{ "type": "object", "properties": { "url": { "type": "string" }, "book": { "type": "string" }, "offset": { "type": "integer", "minimum": 0 } }, "additionalProperties": false }arguments 16 linesread_with_eyestill unknown 1h ago
Opens text in EyeStill, a speed reader shown in the chat as an interactive view. The view shows one word at a time at a single point of focus (RSVP) on a 3D drum, with play, pause, speed (100 to 1,000 words per minute) and position controls. Takes exactly one of: url (a public web article, page or plain-text file; the server extracts its readable text), book (title and/or author of a public-domain book, fetched from Project Gutenberg), or text (any text, such as text from the conversation or an answer composed for reading in the view). Text is displayed while it streams in, so reading can start before it is complete. The text is shown only in the view; the result reports its title and word count. Plain prose reads best: Markdown, tables and code appear as raw text. A text can be opened at a word number (start_word, as reported by the reader's context) or at the first place a phrase appears, such as a chapter heading (start_at). While the user reads, the view shares the current position and passage as context.
{ "type": "object", "properties": { "url": { "type": "string", "description": "Address of a public web page, article or .txt file" }, "wpm": { "type": "integer", "maximum": 1000, "minimum": 100, "description": "Starting speed in words per minute; 300 if omitted" }, "book": { "type": "string", "description": "Title and/or author of a public-domain book, e.g. \"Moby Dick Melville\"" }, "text": { "type": "string", "description": "Text to read, e.g. from the conversation or an answer written for the reader; shown as it streams in" }, "title": { "type": "string", "description": "Optional title shown above the reader (for text)" }, "start_at": { "type": "string", "description": "A phrase to start reading from, e.g. a chapter heading like \"CHAPTER 30\"" }, "start_word": { "type": "integer", "minimum": 0, "description": "Word number to start reading from, e.g. where the reader stopped" } }, "additionalProperties": false }arguments 37 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idd53f7e4405e633d4.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/d53f7e4405e633d4/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/d53f7e4405e633d4?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.