Skip to content

MCP servers › com.dialyne › dialyne

MCP server · registry snapshot 2026-11-07 · last tested 2026-11-07

dialyne MCP server

Registry name com.dialyne/dialyne

by dialyne.com · domain (the registry's namespace rule)repository owner on GitHub: dialyne (organization)Source ↗Website ↗

Real phone calls in France for AI agents: dial +33 numbers, menus, hold, AI disclosure. — the publisher's description

5 of 5 record checks metRead-only · tools listed 2026-11-07version 1.0.0streamable HTTP12 tools

Summary

com.dialyne/dialyne is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain dialyne.com. Its linked repository is github.com/dialyne/dialyne-mcp; GitHub reports its owner as dialyne, an organization. On 2026-11-07 ProtocolProbe connected to it in read-only mode and read its inventory: 12 tools, 0 resources and 0 prompts.

Record checks

5 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
12
Last tested
2026-11-07

Tool list size

10,814 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (12 tools). Counted with Anthropic's token counter on 2026-11-09, from the tool list we read on 2026-11-07. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-07 (mcp.dialyne.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 6 tools whose name or declaration suggests they change data (place_phone_call, answer_call_question, transfer_call_to_user, schedule_callback, cancel_call and 1 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-07.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-07
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-11-07 (registry, as of the 2026-11-07 snapshot)
First listed version
2026-11-07 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-07
Package and repository
checked 2026-11-07
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-06, listed on 2026-11-07 with version 1.0.0 (published 2026-11-07).

Source: the official MCP Registry list on 2026-11-06 and on 2026-11-07.

What it is

What does this server offer?

Observed inventory
12tools
0resources
0prompts

None of its 12 tools are described as changing anything. For 12 the reading was uncertain, so no mark is shown.

  • place_phone_callon 1 other server

    “Place a real outbound phone call to a number in France (+33) and get back a written result: a voice agent carries out the task you describe (book a table, move an appointment, ask a business a questi…”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    10 inputs, 2 required
    • phone_numberstringrequired“Number to call, French only.”
    • taskstringrequired“What the call must achieve, in plain English or French (10-2000 characters): the goal, on whose behalf (the user's name), the facts the callee may ask for (dat…”
    • languagestring or null“Language spoken on the call: 'fr' (French), 'en' (English) or 'auto' (starts in French, switches to English if the callee speaks English).”
    • scheduled_atstring or null“When to PLACE the call (not the time of the booking or appointment: that goes in task).”
    • voicestring or null“Optional voice: '1' Solène (female, calm), '2' Gaspard (male, warm), '3' Coralie (female, lively), '4' Marius (male, deep), '5' Bella (female, premium, most ex…”
    • voice_settingsnull“Optional tuning, only if the user asks for it (omit otherwise: the account settings, already optimal, apply).”
    • idempotency_keystring or null“Optional unique key (letters, digits, '-', '_', '.', ':'; max 64) for this call request.”
    • ai_disclosurestring“'standard' (default, recommended): the voice agent says it is an AI assistant in its opening line.”
    • callee_informed_confirmationstring or null“Required with ai_disclosure='callee_already_informed' (10-300 characters): the user's confirmation, in their words, of who the callee is and how they know an A…”
    • outside_hoursstring or null“Obsolete, accepted and ignored: no calling-hours window is imposed any more.”
  • “Get the status and written result of a call placed with place_phone_call (outcome, summary, pending question, transcript on request), optionally waiting for news.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 1 required
    • call_idstringrequired“The call_id returned by place_phone_call or list_calls (e.g.”
    • wait_secondsinteger“Seconds (0-50) to wait for news before returning: returns early when the callee answers, the call goes on hold, the voice agent asks a question, a transfer pro…”
    • after_event_idinteger“Return only events after this id: pass last_event_id from the previous get_call response.”
    • response_formatstring“'concise' (default): status, outcome, summary, pending question and key events.”
  • answer_call_questionon 2 other servers

    “Send the user's answer to a question the voice agent asked during a live call (shown by get_call as pending_question) and get confirmation that it was relayed.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    3 inputs, 2 required
    • call_idstringrequired“The call_id of the live call (or of an ended call awaiting its callback with a pending_question).”
    • answerstringrequired“The user's answer, as the voice agent should relay it to the callee (1-1000 characters), e.g.”
    • question_idstring or null“pending_question.question_id from get_call.”
  • transfer_call_to_user

    “Transfer a live call to the user's own phone so they can talk to the callee themselves, and get the transfer request confirmed.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • call_idstringrequired“The call_id of the live call to hand over.”
    • user_phone_numberstringrequired“The user's own phone number to ring, French only (+33…, mobile 06/07 accepted), e.g.”
  • schedule_callbackon 2 other servers

    “Schedule a new attempt of a finished call (same number, same task) at the time the user chose and get the scheduled time back, for instance when the callee said 'call back tomorrow after 3 pm'.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • call_idstringrequired“The call_id of a finished call (status completed).”
    • callback_atstringrequired“When to call again, ISO 8601, e.g.”
  • cancel_call

    “Cancel a call that is scheduled or in progress (including a scheduled callback or automatic retry) and get the cancelled status back.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • call_idstringrequired“The call_id of the scheduled or live call to cancel.”
  • “List this account's calls, newest first, and get for each one its call_id, phone number, status, outcome, task and one-line summary.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • querystring“Optional text searched in the task, the summary, the transcript and the phone number (e.g.”
    • outcomestring or null“Optional filter on the call outcome.”
    • limitinteger“Maximum number of calls returned (1-50).”
  • get_account_balanceon 12 other servers

    “Read the remaining call time on this account and get the minutes of conversation left on the prepaid credit (subscription minutes included, with their expiry date) and the account limits (simultaneou…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • hold_call_question

    “Get one more minute to answer the voice agent's pending question: the request is passed to the voice agent, which asks the callee.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 1 required
    • call_idstringrequired“The call_id of the live call whose voice agent is waiting for an answer.”
    • question_idstring or null“pending_question.question_id from get_call.”
  • place_batch_calls

    “Place the same call to a list of numbers in France (Pro and Enterprise plans) and get back a batch_id with one call_id per number.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    6 inputs, 2 required
    • phone_numbersarrayrequired“Numbers to call, French only, copied as given ('01 42 00 00 00' or +33…); 100 at most.”
    • taskstringrequired“The same task for every call, as in place_phone_call (goal, on whose behalf, facts, limits).”
    • namestring or null“Optional batch name, e.g.”
    • languagestring or null“Language of the calls; omit for the account default.”
    • voicestring or null“Optional voice; omit for the account default.”
    • scheduled_atstring or null“When to start (ISO 8601 with time zone).”
  • get_batch_calls

    “Get the progress and results of a batch of calls: counts by status, successes, refused numbers and, for each call, its call_id, status, outcome and summary.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • batch_idstringrequired“The batch_id returned by place_batch_calls (e.g.”
  • configure_agent_identity

    “Read or change how the voice agent introduces itself on the user's calls: name, tone, opening line, answer to "who is calling?", introduction and the AI mention in the opening.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    9 inputs
    • first_namestring or null“Name the voice agent gives (e.g.”
    • tonestring or null“Tone of voice: 'warm' (recommended), 'neutral', 'formal' or 'upbeat'.”
    • opening_linestring or null“Custom opening line, spoken word for word when the callee answers, before the purpose of the call; may use {prenom} (agent name) and {operateur} (user's announ…”
    • who_is_calling_answerstring or null“Custom answer when the callee asks who the agent is calling for.”
    • introductionstring or null“Custom answer when the callee asks who the agent is.”
    • ai_mention_in_openingboolean or null“true (recommended): the opening line says the agent is a virtual assistant.”
    • reset_to_recommendedboolean“true: drop every deviation (keeps first_name and tone).”
    • accept_responsibilityboolean“Set true ONLY after you showed the user the warning text returned by this tool and the user explicitly accepted it in their own words.”
    • warning_versionstring or null“The warning.version the user accepted (from a previous call of this tool).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-07.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 43
Tools with a description
100% of 12
Typical description length
1,092 characters

The tool set

Counted from the listing

Tools
12
Size of the list
about 10,550 tokens for an agent to load (characters ÷ 4)
Naming
12 of 12 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 12 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-07 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://mcp.dialyne.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "dialyne": {
      "url": "https://mcp.dialyne.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "dialyne": {
      "type": "http",
      "url": "https://mcp.dialyne.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"dialyne","type":"http","url":"https://mcp.dialyne.com/mcp"}'
Claude Code
claude mcp add --transport http dialyne https://mcp.dialyne.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "dialyne": {
      "type": "streamableHttp",
      "url": "https://mcp.dialyne.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "dialyne": {
      "httpUrl": "https://mcp.dialyne.com/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.dialyne]
url = "https://mcp.dialyne.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "dialyne": {
      "url": "https://mcp.dialyne.com/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.dialyne.com/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint mcp.dialyne.com/mcpSession openedmatchesour test · 2026-11-07
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-07
Repository github.com/dialyne/dialyne-mcpOpens publiclymatchesapi.github.com · 2026-11-07

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
com.dialyne
GitHub owner
an organization (dialyne)
Repository
github.com/dialyne/dialyne-mcp
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

Source: the registry entry and api.github.com · 2026-11-07; security policy read from GitHub · 2026-11-07.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

5 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-07 (security policy 2026-11-07). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about com.dialyne/dialyne

Answered from the data above

Who publishes com.dialyne/dialyne?

The registry ties the namespace com.dialyne to the domain dialyne.com; only its owner can publish under it. Its linked repository is github.com/dialyne/dialyne-mcp; GitHub reports its owner as dialyne, an organization. These are facts from the registry and GitHub, not a rating.

Is com.dialyne/dialyne safe to install?

We do not rate servers as safe or unsafe. 5 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does com.dialyne/dialyne need an API key or sign-in?

It opened a session without any credential on 2026-11-07. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.dialyne/dialyne been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Does com.dialyne/dialyne publish a security policy?

Yes: its repository has a public security policy (github.com/dialyne/dialyne-mcp/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Where is the source code of com.dialyne/dialyne?

In github.com/dialyne/dialyne-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-07
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-07, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,274 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 12 tools, 0 resources, 0 prompts.
  4. 4,759 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-07; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
not stated
GitHub detects no source language in this repository (docs-only or empty)
Hosting type
registry · 2026-11-07
MCP capability
experimental, prompts, resources, tools
our test · 2026-11-07
Transport
streamable HTTP
registry · 2026-11-07
Required credentials
none declared
registry · 2026-11-07 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-07
Lifecycle status
registry · 2026-11-07
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: an organization · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-11-07
Maintenance
api.github.com · 2026-11-07
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-07

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.dialyne/dialyne: MCP server record.” Data checked 2026-11-07. https://protocolprobe.com/mcp/servers/com.dialyne/dialyne

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 5 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.dialyne/dialyne)](https://protocolprobe.com/mcp/servers/com.dialyne/dialyne)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology