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.

Dialect demo

REMOTE · API.DIALECTLAYER.COM

Try Dialect with no account: read-only public endpoints, like a live NASA test chamber door.

70 Trust /100

Last scanned (20 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 21 Nov 2026.

Category IoT and Hardware

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
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 442 tokens (~110/item across 4 items; 4 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 Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 0
    • Server version: ecc2c88254339e5b038163f4f668e2fc4db92d19 → 17e487c0dab596618167d37425fb83db13ecaece functional
  • 19 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.

  • 18 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 6c64ded70c33aece85eb5ea901bb08734c39ea6d → ecc2c88254339e5b038163f4f668e2fc4db92d19 functional
  • 17 Nov 26 69

    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 21 Nov 2026 · Probed https://api.dialectlayer.com/mcp/public

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.dialectlayer.com CN=Amazon RSA 2048 M01,O=Amazon,C=US 20 Oct 2026 5 May 2027 RSA 2048 SHA256-RSA 96acca9a7c8080b0117ad4fb4d12bfe
SANs: api.dialectlayer.com, api-aws.dialectlayer.com
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.dialectlayer.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
dialectlayer.com. No DS 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://api.dialectlayer.com/mcp/public Verified 200
http (plaintext) http://api.dialectlayer.com/mcp/public HTTPS enforced 301 https://api.dialectlayer.com:443/mcp/public
MCP tools · 4 exposed · ~292 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
dialect_changes ~88

Use to see what changed: each reading that changed a field, newest first, with its value, whether it was read sure and when, over the last last_s seconds (default an hour). Side effects: none.

NameTypeReqDescription
last_sinteger––
limitinteger––
namestringyesThe public endpoint's name, like chamber-a, from dialect_endpoints

No output schema declared.

No examples provided.

dialect_endpoints ~30

Use first: the endpoints anyone may read, each with its name and title. Side effects: none.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

dialect_read_endpoint ~92

Use to read a public endpoint now: each field's question, value, whether it was read sure, why not, and since when (Unix seconds) it has held, plus the last 24 hours summed and its latest changes. A value read unsure is what it leaned to. Side effects: none.

NameTypeReqDescription
namestringyesThe public endpoint's name, like chamber-a, from dialect_endpoints

No output schema declared.

No examples provided.

dialect_summary ~82

Use for how long or how often over a time: each value's sure seconds, share of the window and how many times it was entered, over the last last_s seconds (default a day). Side effects: none.

NameTypeReqDescription
last_sinteger––
namestringyesThe public endpoint's name, like chamber-a, from dialect_endpoints

No output schema declared.

No examples provided.

Install

How do I install the Dialect demo MCP server?

Dialect demo is a hosted endpoint at https://api.dialectlayer.com/mcp/public, 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 · api.dialectlayer.com

# add to Claude Code
claude mcp add --transport http com-dialectlayer-dialect-demo 'https://api.dialectlayer.com/mcp/public'
Common questions

What is the Dialect demo MCP server?

Dialect demo is an MCP server listed in the public MCP registry as com.dialectlayer/dialect-demo. Try Dialect with no account: read-only public endpoints, like a live NASA test chamber door. This page covers its hosted endpoint (https://api.dialectlayer.com/mcp/public).

Is the Dialect demo MCP server safe to use?

Dialect demo scores 70 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 Dialect demo MCP server expose?

Dialect demo exposes 4 tools: dialect_endpoints, dialect_read_endpoint, dialect_summary, dialect_changes. Their descriptions and schemas cost roughly 292 tokens of context every time the server is loaded.

Does the Dialect demo MCP server require authentication?

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

Is the Dialect demo MCP server still maintained?

Dialect demo is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Dialect demo MCP server?

VerifyMCP ran 13 checks on Dialect demo, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.