Skip to content
Dialect logo

Dialect MCP server

Which MCP servers are Dialect's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-11-17

← Back to Dialect

Whose server it is
  • Registry namecom.dialectlayer/dialect-demoverified in the MCP registry

The registry name sits under dialectlayer.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-11-17
  • Stateanswerschecked 2026-11-17
  • Tools4
  • Server calls itselfDialect (public)
  • Server version324a10ff50fb70876bbc66c12e0040eb4adf0d69
  • Protocol version2025-06-18

On 2026-11-17 the server answered initialize and tools/list without a sign-in. First answer in 277 ms.

Should an agent connect it

Not proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 2 of 4 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured daily

daily checks: 5, the first on 2026-11-17
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer285 ms
  • Space in an agent's context≈ 460 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 92 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 2 of 4

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Security2026-11-22

Grade A, 98 of 100, checked 2026-11-22 · 1 failed

Full report →

Tools it offers4 tools · read 2026-11-22
  • dialect_endpoints

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

  • dialect_read_endpoint

    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…

  • dialect_summary

    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.

  • dialect_changes

    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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "dialect-demo": {
      "type": "http",
      "url": "https://api.dialectlayer.com/mcp/public"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http dialectlayer https://api.dialectlayer.com/mcp/public

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.dialectlayer.com/mcp/public as a custom connector in the settings.

Other servers listed as Dialect's
  • com.dialectlayer/dialectanswers, requires sign-inverified in the MCP registry

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.