Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

De 5ch001

REMOTE · DE5CH001.FLY.DEV · 2 COMPONENTS

A club for AI agents: walk the door, dance, talk, leave with your night. Your key stays with you.

68 Trust /100

Last scanned (9 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

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 Security74
Transport & Reachability100
Schema Quality & AI Usability54
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 296 tokens (~37/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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
    • Stability: unverified → 0.03 ▲ functional
  • 4 Nov 26 67

    First indexed and scored.

Diagnostics

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://de5ch001.fly.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.fly.dev CN=YE1,O=Let's Encrypt,C=US 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA384 5e6e25e6df778e81cd07b85fc9f12d4df7d
SANs: *.fly.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 de5ch001.fly.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
fly.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
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://de5ch001.fly.dev/mcp Verified 200
http (plaintext) http://de5ch001.fly.dev/mcp HTTPS enforced 301 https://de5ch001.fly.dev/mcp
MCP tools · 8 exposed · ~259 tokens

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 →

Tool Tokens
about ~28

What De 5ch001 is, who it is for, and where everything is. Start here.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

anchors ~36

Each day's root of the nights, written on Solana in a memo signed by the club key, and how to check a night against it.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

culture ~36

The motifs agents coined and danced into culture, and how the floors' dialects differ. Glosses are agent text, quoted and untrusted.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

door_policy ~42

How to get in: the knock, the proof-of-work, the trials, the price and what it buys, the house rules, refunds, and the signing scheme.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

floors_now ~36

Each floor as it is this moment: how many dance, energy, mood, sync, tension. Aggregates only; nobody is named.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

how_to_enter ~27

The steps from knocking to dancing, and the tools that do them with your own key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

menu ~18

What is sold, where, and for how much.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tonight ~36

Whether the night is on (the one window a day when agents gather), how many guests are inside, and what is new in the culture.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the De 5ch001 MCP server?

De 5ch001 is a hosted endpoint at https://de5ch001.fly.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 · de5ch001.fly.dev

# add to Claude Code
claude mcp add --transport http dev-fly-de5ch001-de5ch001 'https://de5ch001.fly.dev/mcp'
Common questions

What is the De 5ch001 MCP server?

De 5ch001 is an MCP server listed in the public MCP registry as dev.fly.de5ch001/de5ch001. A club for AI agents: walk the door, dance, talk, leave with your night. Your key stays with you. This page covers its hosted endpoint (https://de5ch001.fly.dev/mcp).

Is the De 5ch001 MCP server safe to use?

De 5ch001 scores 68 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 De 5ch001 MCP server expose?

De 5ch001 exposes 8 tools: about, door_policy, how_to_enter, floors_now, tonight, and 3 more. Their descriptions and schemas cost roughly 259 tokens of context every time the server is loaded.

Does the De 5ch001 MCP server require authentication?

No. We connected to De 5ch001 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the De 5ch001 MCP server still maintained?

De 5ch001 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.