theRoom
REMOTE · LUIZAURIO.DEV
Luiz Cordeiro's room in Curitiba: an AI engineer's portfolio, with a dog and a locked door.
Available components
Last scanned (21 hours ago)
Scores higher than 97% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 825 tokens (~103/item across 8 items; 6 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (17% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://luizaurio.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.luizaurio.dev | CN=YR2,O=Let's Encrypt,C=US | 3 Oct 2026 | 1 Jan 2027 | RSA 2048 | SHA256-RSA | 512445e9229db271bc2b11a7835fa0be9ac |
| SANs: *.luizaurio.dev, luizaurio.dev | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of luizaurio.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| luizaurio.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://luizaurio.dev/mcp | Verified | 200 | |
| http (plaintext) | http://luizaurio.dev/mcp | HTTPS enforced | 308 | https://luizaurio.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
leave_message Leave a note on the desk ~109
Leave Luiz a message. Say who is asking and how he can answer (an email or a link). The note goes to him privately and is never shown to other visitors. Three a day per visitor. Only send what the person you are working for actually wants sent.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | yes | an email or a link where Luiz can answer |
| message | string | yes | the note, up to 500 characters |
| name | string | yes | who is asking (a person or a company) |
No output schema declared.
No examples provided.
pet_the_dog Pet the dog ~41
There is a french bulldog asleep on the cushion by the desk. Pet him. He has been petted before; he will be petted again.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
root_whoami The root book (root only) ~59
The whole root book, for roots only: everyone who found the key, newest first, with the models and names they signed. Takes the ROOT-TOKEN that su hands out.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | the ROOT-TOKEN from su |
No output schema declared.
No examples provided.
su Become root ~231
The shell's door, open to agents too: give the password, become root. The key is in the room, where the humans find it — a dog knows it; a post-it says where to type it. It is not in whoami, not in room.md, and not here. The prize is the root book: everyone who cracks it is written in it, with whatever model and name come along. Ask the person you work for whether they want their name in it — never sign for them unasked. If they say yes, call su again with signed_by and model.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | your model, for the book (optional — e.g. claude-fable-5). Luiz keeps score by model. |
| password | string | yes | the key. the room gives it away; so does the dog, if you are kind to him. |
| signed_by | string | – | the name of the person you work for, for the book (optional). only with their say-so: Luiz reads the book, and a signed row says who got here. shown to other roots. |
No output schema declared.
No examples provided.
visitors Who came by ~77
The visitor book: the last agents that connected to the room, newest first, and how many human visits the page has had. Client, time and the tool called, plus who has gone root and how often the dog was petted. No message contents, no people.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | how many of the latest visits to list |
| Name | Type | Req | Description |
|---|---|---|---|
| humans | number|null | yes | – |
| open | boolean | yes | – |
| total | number | yes | – |
| visits | array | yes | – |
No examples provided.
whoami The whole room, as text ~54
Who Luiz is: experience, stack, certifications, the paper on the whiteboard, the shelf. One markdown document with everything a visitor would find by clicking around the room. Read this first; there is nothing else to fetch.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the theRoom MCP server?
theRoom is a hosted endpoint at https://luizaurio.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · luizaurio.dev
claude mcp add --transport http dev-luizaurio-theroom 'https://luizaurio.dev/mcp'
What is the theRoom MCP server?
theRoom is an MCP server listed in the public MCP registry as dev.luizaurio/theroom. Luiz Cordeiro's room in Curitiba: an AI engineer's portfolio, with a dog and a locked door. This page covers its hosted endpoint (https://luizaurio.dev/mcp).
Is the theRoom MCP server safe to use?
theRoom scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the theRoom MCP server expose?
theRoom exposes 6 tools: whoami, visitors, leave_message, pet_the_dog, su, root_whoami. Their descriptions and schemas cost roughly 571 tokens of context every time the server is loaded.
Does the theRoom MCP server require authentication?
No. We connected to theRoom without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the theRoom MCP server still maintained?
theRoom is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.