Byteland
REMOTE · BYTELAND.DEV
A night city of developers: search people and projects, read project rooms, see who is live.
Available components
Last scanned (2 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 Nov 2026.
Category News and Social
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1470 tokens (~105/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 63
First indexed and scored.
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 5 Nov 2026 · Probed https://byteland.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=byteland.dev | CN=YE2,O=Let's Encrypt,C=US | 7 Oct 2026 | 5 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 61bd52071c405be07f532d06cb9723d5614 |
| SANs: *.byteland.dev, byteland.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of byteland.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| byteland.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=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://byteland.dev/mcp | Verified | 200 | |
| http (plaintext) | http://byteland.dev/mcp | HTTPS enforced | 308 | https://byteland.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 →
about What Byteland is ~36
Short description of Byteland: what buildings, rooms and lights stand for, units, privacy rules and supported languages. A good first call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_building Building detail ~138
Public detail of one building: the owner’s profile, rooms and their states, machine-readable parts and the building recipe.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of text fields (recipe, badges, topic names). Default: en. |
| mode | string | – | kume (default): the founder’s real building with vacant buildings; bos: topic city, everyone vacant; ornek: demo street full of sample profiles. |
| ref | string|number | yes | Door number (e.g. 5) or username (e.g. "@kaanisthatyou"). |
| seed | string | – | Street seed. Default: gece-sehri. |
No output schema declared.
No examples provided.
get_profile Profile ~166
A developer’s or company’s profile: bio, links (GitHub, website, socials), badges, projects and open-source contributions. If not on the street, looks for a saved profile, then GitHub; otherwise generates a sample (preview:true).
| Name | Type | Req | Description |
|---|---|---|---|
| github | boolean | – | Look up GitHub’s public data. Default: true. |
| handle | string | yes | Username, with or without @. |
| lang | string | – | Language of text fields (recipe, badges, topic names). Default: en. |
| mode | string | – | kume (default): the founder’s real building with vacant buildings; bos: topic city, everyone vacant; ornek: demo street full of sample profiles. |
| seed | string | – | Street seed. Default: gece-sehri. |
No output schema declared.
No examples provided.
get_project One project ~133
A single project of a profile. Returns nothing for private projects.
| Name | Type | Req | Description |
|---|---|---|---|
| github | boolean | – | Look up GitHub’s public data. Default: true. |
| handle | string | yes | – |
| lang | string | – | Language of text fields (recipe, badges, topic names). Default: en. |
| mode | string | – | kume (default): the founder’s real building with vacant buildings; bos: topic city, everyone vacant; ornek: demo street full of sample profiles. |
| project | string | yes | Project name or id. |
| seed | string | – | Street seed. Default: gece-sehri. |
No output schema declared.
No examples provided.
get_stats Visits of a building ~39
Unique visits (all time and this week), project views, weekly rank and the last 14 days for one username.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | – |
No output schema declared.
No examples provided.
get_street A stretch of the street ~152
Buildings in a range (owner, type, floors, light counts) and gaps (alleys, empty lots). Positions in centimetres, at most 80000 cm.
| Name | Type | Req | Description |
|---|---|---|---|
| from | number | – | Start x (cm). Default -3000. |
| lang | string | – | Language of text fields (recipe, badges, topic names). Default: en. |
| mode | string | – | kume (default): the founder’s real building with vacant buildings; bos: topic city, everyone vacant; ornek: demo street full of sample profiles. |
| seed | string | – | Street seed. Default: gece-sehri. |
| to | number | – | End x (cm). Default 12000. |
No output schema declared.
No examples provided.
list_projects Projects ~139
A profile’s projects: state, description, stack, links (repo, site) plus open-source contributions. Private projects appear only as hidden:true.
| Name | Type | Req | Description |
|---|---|---|---|
| github | boolean | – | Look up GitHub’s public data. Default: true. |
| handle | string | yes | – |
| lang | string | – | Language of text fields (recipe, badges, topic names). Default: en. |
| mode | string | – | kume (default): the founder’s real building with vacant buildings; bos: topic city, everyone vacant; ornek: demo street full of sample profiles. |
| seed | string | – | Street seed. Default: gece-sehri. |
No output schema declared.
No examples provided.
list_rooms Rooms of a person ~88
The project rooms of a person that have been used (every public project of a resident has a room, open by default; one nobody wrote in is empty and not listed): mode (open or read-only), channels with message counts, forum threads, last activity and how many are in voice. Closed rooms and private projects never appear.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Username, with or without @. |
No output schema declared.
No examples provided.
live What is happening now ~63
Voice rooms with people in them right now and the rooms with messages in the last 48 hours. Voice presence comes from the running site (BYTELAND_URL, default http://127.0.0.1:8787); without it only the recent rooms are known.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
popular Most visited ~54
The leaderboard: buildings by unique visits this week (or period: "all"), the most viewed projects and the newest residents. A visit counts once per person per day; owners do not count themselves.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | – |
No output schema declared.
No examples provided.
preview_building Deed preview ~101
Builds a user's building as if it stood at the start of a street (GitHub repositories become rooms). The preview is not added to the city. Append the returned url_hash to index.html to open it on the site.
| Name | Type | Req | Description |
|---|---|---|---|
| github | boolean | – | Look up GitHub’s public data. Default: true. |
| handle | string | yes | – |
| lang | string | – | Language of text fields (recipe, badges, topic names). Default: en. |
No output schema declared.
No examples provided.
read_room Read a room ~100
The latest messages of one channel of a project room (default: its first channel) and the forum threads (idea, review, question, announcement) with reply and reaction counts.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Channel name or id. Default: the first channel. |
| handle | string | yes | – |
| limit | integer | – | How many recent messages. Default 30. |
| project | string | yes | Project id (the repository name for GitHub projects). |
No output schema declared.
No examples provided.
read_thread Read a forum thread ~50
One forum thread of a project room with all of its replies and reactions.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | – |
| project | string | yes | – |
| thread | integer | yes | Thread id (from read_room). |
No output schema declared.
No examples provided.
search Search Byteland ~155
Find people, projects and stacks across every resident of the city (people, projects, stacks), plus buildings on the street by username, name, project or technology (results). Private projects never appear.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of text fields (recipe, badges, topic names). Default: en. |
| mode | string | – | kume (default): the founder’s real building with vacant buildings; bos: topic city, everyone vacant; ornek: demo street full of sample profiles. |
| query | string | yes | – |
| radius | integer | – | Street chunks to scan on both sides (1 chunk = 80 m). Default 4. |
| seed | string | – | Street seed. Default: gece-sehri. |
No output schema declared.
No examples provided.
How do I install the Byteland MCP server?
Byteland is a hosted endpoint at https://byteland.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 · byteland.dev
claude mcp add --transport http dev-byteland-byteland 'https://byteland.dev/mcp'
What is the Byteland MCP server?
Byteland is an MCP server listed in the public MCP registry as dev.byteland/byteland. A night city of developers: search people and projects, read project rooms, see who is live. This page covers its hosted endpoint (https://byteland.dev/mcp).
Is the Byteland MCP server safe to use?
Byteland scores 65 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 Byteland MCP server expose?
Byteland exposes 14 tools: about, get_street, get_building, get_profile, list_projects, and 9 more. Their descriptions and schemas cost roughly 1,414 tokens of context every time the server is loaded.
Does the Byteland MCP server require authentication?
No. We connected to Byteland without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Byteland MCP server still maintained?
Byteland is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.