lettras
Registry code: bc3f90a92552471f
Use generate_word_search to build word-search puzzles in es, en, pt, fr, de or it, then fill_word_search to complete the empty cells with random letters (accents on or off). Accents and letters like Ñ and ẞ are kept as single cells.
- endpoint
- https://mcp.lettras.org/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 lettras live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is lettras free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does lettras have?
- 3 tools: fill_word_search, generate_word_search, list_languages.
- Is lettras 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 3 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.
list_languages open 1h ago
Languages Lettras supports, with the native letters each one adds to its grid alphabet.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesfill_word_search unknown 1h ago
Completes a word search: takes the grid from generate_word_search (empty cells are "-") and fills them with random letters in the chosen language, with accents on or off. Letters follow how common they are in that language. Pass the puzzle's words so the filler never creates an extra copy of one.
{ "type": "object", "required": [ "grid" ], "properties": { "grid": { "type": "array", "items": { "type": "array", "items": { "type": "string", "maxLength": 4, "minLength": 1 }, "maxItems": 30, "minItems": 1 }, "maxItems": 30, "minItems": 1, "description": "The grid from generate_word_search: rows of one-letter strings, \"-\" for empty cells." }, "lang": { "enum": [ "es", "en", "pt", "fr", "de", "it" ], "type": "string", "description": "Language of the letters. Default es." }, "seed": { "type": "integer", "minimum": 0, "description": "Repeatable filler. Omit for a different filler every time." }, "empty": { "type": "string", "maxLength": 4, "description": "What marks an empty cell. Default \"-\"." }, "words": { "type": "array", "items": { "type": "string", "maxLength": 30, "minLength": 1 }, "maxItems": 60, "description": "The hidden words, so the filler cannot create an extra copy of one." }, "accents": { "type": "boolean", "description": "true (default): use the language's accented/native letters (Ñ, Ç, Ã, Ä, ẞ…). false: plain A-Z only." } }, "additionalProperties": false }arguments 61 linesgenerate_word_search unknown 1h ago
Create a word-search puzzle (sopa de letras) from a list of words. Keeps native letters (Ñ, Ç, Ã, Ä, ẞ, È…) as one cell each. Returns the grid, where every word is hidden, and any words that did not fit. Empty cells are marked "-": call fill_word_search with the grid to complete it with random letters. The same seed always gives the same puzzle.
{ "type": "object", "required": [ "words", "rows", "cols" ], "properties": { "cols": { "type": "integer", "maximum": 30, "minimum": 6, "description": "Grid width. May differ from rows for a rectangular grid." }, "lang": { "enum": [ "es", "en", "pt", "fr", "de", "it" ], "type": "string", "description": "Language of the words. Default es." }, "rows": { "type": "integer", "maximum": 30, "minimum": 6, "description": "Grid height." }, "seed": { "type": "integer", "minimum": 0, "description": "Repeatable puzzles: same input and seed, same grid." }, "words": { "type": "array", "items": { "type": "string", "maxLength": 30, "minLength": 1 }, "maxItems": 60, "minItems": 1, "description": "Words to hide, in their normal spelling (accents kept)." }, "position": { "enum": [ "horizontal", "vertical", "mixed" ], "type": "string", "description": "horizontal = left to right only, vertical = top to bottom only, mixed = all 8 directions including diagonals." }, "clustering": { "type": "number", "maximum": 1, "minimum": 0, "description": "0 keeps words apart, 1 makes them cross. Default 0.5." }, "difficulty": { "type": "integer", "maximum": 4, "minimum": 1, "description": "Used when position is not set: 1 easy (right, down) to 4 expert (all 8 directions)." }, "classicMode": { "type": "boolean", "description": "Strip accents in the grid (ñ becomes N)." } }, "additionalProperties": false }arguments 76 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 idbc3f90a92552471f.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/bc3f90a92552471f/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/bc3f90a92552471f?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.