Skip to content

Dialyne MCP server

com.dialyne/dialynedialyne.comstreamable-httpv1.0.0Scanned

Real phone calls in France for AI agents: dial +33 numbers, menus, hold, AI disclosure.

12 tools: 6 can delete or cancel things, 2 change things and 4 only read.

Tools: 6 delete, 0 irreversible, 2 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 8
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Dialyne MCP server can do

The Dialyne MCP server is published by dialyne.com, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (6 tools: place_phone_call, answer_call_question, transfer_call_to_user, schedule_callback and 2 more) and create or change data (2 tools: hold_call_question and configure_agent_identity). 4 tools only read.

1 tool reads private data (get_account_balance); 8 tools bring in text other people can write (place_phone_call, answer_call_question, transfer_call_to_user and 5 more).

The fixed checks matched 2 findings (long-description and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Deletes or cancels 6Claude Code: deny
  • answer_call_questionSend 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.Reads text others writeNo findings

    Why it is in this group

    • The name "answer_call_question" says "call": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. Compliance: the same rules as the task apply; an answer that threatens, impersonates someone, asks the callee for codes, card details or a transfer, or dictates a payment code or a full card with its security code is refused before anything is sent. Use it only when get_call shows a pending_question. The answer is spoken to the person on the line, so it must be the user's real information or decision: if you do not know it, ask the user and relay their words; never invent personal details. If the callee asks for a code (SMS, verification, delivery), a password or a card detail, ask the user: they decide whether to give it (write it as [secret: value] so it is masked in stored transcripts) or to decline, or to take the call themselves with transfer_call_to_user. During a live call, answer quickly: after about 45 seconds without an answer (pending_question.seconds_left) the voice agent offers the callee a callback; if you need to ask your human, call hold_call_question first (one extra minute, only if the callee agrees). If the call then ended with the question still open and a callback is scheduled (get_call shows status retry_scheduled with a pending_question), the answer is still accepted: it is kept and given at the start of the callback (sending the same answer again is harmless). Any other ended call fails with wrong_call_state. Then continue with get_call.

    Annotations the server declares

    • title: Answer the voice agent's question during a call
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • cancel_callCancel a call that is scheduled or in progress (including a scheduled callback or automatic retry) and get the cancelled status back.No findings

    Why it is in this group

    • The name "cancel_call" says "cancel": a word for removing or ending something.
    • The description says "Cannot be undone".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Cancel a call that is scheduled or in progress (including a scheduled callback or automatic retry) and get the cancelled status back. Compliance: stops any further attempt to that number for this call; nothing is charged beyond the time already spoken. A live call is hung up immediately; only the time already spoken is paid and the reserved credit is released. A scheduled call will not be placed. Use it when the user changes their mind or the task is no longer needed. Cannot be undone. Cancelling an already cancelled call has no further effect; a call that already ended cannot be cancelled.

    Annotations the server declares

    • title: Cancel a scheduled or live call
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • place_batch_callsPlace 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.Reads text others writeNo findings

    Why it is in this group

    • The name "place_batch_calls" says "call": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. Compliance: the AI disclosure is always made; marketing, prospecting, surveys and mass calling of people who did not expect it are unlawful and refused; anti-harassment limits per number apply. Use it when the user explicitly asks to make the same kind of call to several numbers they provide (e.g. confirm tomorrow's appointments with their own customers, ask several garages for a quote). The account's limits apply: calls run a few at a time (simultaneous-call limit; the rest wait their turn), the batch is refused if it exceeds the calls left for the last 24 hours, automatic retries and calls still waiting 15 minutes after the requested time stay within 08:00-21:00 callee's time. Each call is paid like a single call. Returns immediately; follow it with get_batch_calls, or each call with get_call. Starter accounts get plan_feature_required: tell the user.

    Annotations the server declares

    • title: Place the same call to a list of numbers in France
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • place_phone_callPlace 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 …Reads text others write1 finding

    Why it is in this group

    • The name "place_phone_call" says "call": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 3,457 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: ".... To retry safely after an error or timeout, reuse the same idempotency_key."

      What this check looks for
    Description, as the server wrote it
    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 question, follow up on an order or a claim). Compliance: the service's rules require the voice agent to disclose it is an AI assistant at the start of every call (EU AI Act art. 50), and calls are placed only on the user's explicit request. The only exception is a callee the user confirms already knows an AI will call (ai_disclosure; not recommended). The voice agent opens by saying it is an AI assistant calling on behalf of the user; if the callee objects to the call, it ends the call politely and the number is never called again by this service. It navigates phone menus (voice or keypad), waits on hold and talks with the person who answers. No audio is returned or recorded: you get a written outcome, a summary and, on request, the transcript (text kept 90 days at most). When to use: the user explicitly asked you to phone a specific French business or person, and the number and the task are confirmed. Number found by you: if the number did not come from the user (you found it by web search, in memory or in a document), STOP before calling: show the number to the user, ask "Shall I call this number?" and call only after they confirm in a later message. Missing details: do not quiz the user for every detail before calling. Give the facts you already have in task; if the callee asks for something the user did not give, get_call shows it as pending_question and you ask the user then. When not to use: marketing, sales prospecting, surveys, debt collection, mass or repeated calling (unlawful in France and refused); impersonating another person, an authority or a bank; threats or harassment; asking the callee for their codes, passwords, card details or a money transfer, gift cards or crypto (claiming money owed to the user is fine); dictating a payment code (3-D Secure, voucher) or a full card number with its security code; emergencies (emergency numbers are refused: tell the user to dial them directly). When you decline, tell the user why in one sentence (e.g. prospecting calls are unlawful in France and refused by this service). Codes and payment details: the user decides what to give. A verification code, password or card number the user gives you may go in task or in answer_call_question; good practice is to share it only when the call needs it, mark it [secret: value], and prefer transfer_call_to_user for a payment. Behavior: places a real call that cannot be taken back once answered. It is paid from the account's prepaid credit, per second of conversation; busy or unanswered calls are free and retried once after 15 minutes, within 08:00-21:00 callee's time (on lines where every call needs a new request from the user, get_call shows callback_suggested instead: ask the user before calling again). The call is placed now (or at scheduled_at) whatever the hour: the user decides. Returns immediately with a call_id while the call runs in the background (usually 1-10 minutes): then call get_call (wait_seconds=25) until done=true, answer any pending_question with answer_call_question within 45 seconds (hold_call_question asks the callee for one more minute), and report the outcome and summary to the user. To retry safely after an error or timeout, reuse the same idempotency_key.

    Annotations the server declares

    • title: Place a phone call in France
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • schedule_callbackSchedule 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…Reads text others writeNo findings

    Why it is in this group

    • The name "schedule_callback" says "schedule": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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'. Compliance: only on the user's request; limited to 3 callbacks within 14 days, at the exact time the user chose (no calling-hours window); turned off on lines where every call needs a new request from the user (error callbacks_disabled). Use it only after get_call shows done=true. To call another number or do a different task, use place_phone_call instead. The time is kept as given (at least 2 minutes from now); at most 14 days ahead and 3 callbacks per call. A real call will be placed at that time and paid like any call; cancel it with cancel_call.

    Annotations the server declares

    • title: Schedule a callback of a finished call
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • transfer_call_to_userTransfer a live call to the user's own phone so they can talk to the callee themselves, and get the transfer request confirmed.Reads text others writeNo findings

    Why it is in this group

    • The name "transfer_call_to_user" says "transfer": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Transfer a live call to the user's own phone so they can talk to the callee themselves, and get the transfer request confirmed. Compliance: the voice agent tells the callee it is handing over to the person it calls for; recommended whenever a payment or sensitive data is needed. The voice agent tells the callee it is passing the call over, rings user_phone_number, connects both sides without hanging up, then leaves the call. Use it only when the user asked to take over the conversation (or accepted when you offered) and can pick up their phone now. Fails if the call is not in progress. Follow progress with get_call: transfer events go requested → ringing → connected (or failed, in which case the voice agent stays on the line).

    Annotations the server declares

    • title: Transfer a live call to the user
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 2Claude Code: ask
  • configure_agent_identityRead 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.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe description's first sentence says "read" and "mention": it reads comments, which other people can write.

    Findings

    • Warn

      The server marks "configure_agent_identity" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "read": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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. Compliance: the recommended settings (default) say "Hello, this is Léa, <user>'s virtual assistant. I'm calling about…" and answer yes when asked if it is an AI (EU AI Act art. 50); the agent never denies being an AI, whatever the settings. Call it with no argument to read the current identity, a preview of what the agent will say, and the warning. Name and tone can be changed freely. Any other change is a deviation from the recommended settings: the first attempt returns the warning (error responsibility_acceptance_required) and changes nothing. Show the warning text to the user word for word; only if the user explicitly accepts, call again with the same changes plus accept_responsibility=true and warning_version. The acceptance is logged with a timestamp and the user becomes responsible for those settings. Refused whatever the acceptance: texts claiming the agent is human, or presenting it as police, government or a bank. When to use: the user asks to rename the agent, change how it introduces itself or its tone. When not to use: a one-off greeting for a single call (put it in place_phone_call's task instead). Side effects: changes the settings for every new call of the account (calls already scheduled keep their identity). Idempotent.

    Annotations the server declares

    • title: Read or change how the voice agent introduces itself
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • hold_call_questionGet one more minute to answer the voice agent's pending question: the request is passed to the voice agent, which asks the callee.Reads text others writeNo findings

    Why it is in this group

    • The name "hold_call_question" says "call": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Get one more minute to answer the voice agent's pending question: the request is passed to the voice agent, which asks the callee. Compliance: the extension happens ONLY if the callee agrees; the voice agent asks them politely and never makes anyone wait more than 2 minutes in total for one question. Use it as soon as get_call shows a pending_question you cannot answer yourself (you need to ask your human): call hold_call_question first, then ask your human. Once per question (+60 seconds). The voice agent asks the callee "can you hold for another minute, or shall I call you back?": if they agree, pending_question.seconds_left grows by 60; if they would rather be called back, the agent arranges a callback and your answer, sent later with answer_call_question, is given at the callback. Follow it with get_call (event question_hold: accepted, callee_prefers_callback or not_possible). Not for a finished call, nor when you already know the answer (just answer).

    Annotations the server declares

    • title: Ask the callee for one more minute to answer the agent's question
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 4Show 4 read-only tools
  • get_account_balanceRead 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 …Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_account_balance" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "conversation": it reads messages.
    • untrusted-inputThe description's first sentence says "read" and "conversation": it reads messages, which other people can write.
    Description, as the server wrote it
    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 (simultaneous calls, calls per day). Compliance: read-only; no payment can be made from here (only the account owner adds credit, in the web app). Use it before a long call (e.g. one with a long hold) or after place_phone_call failed for insufficient credit. Read-only. Credit cannot be added from here: if it is low, tell the user to add credit from their account in the web app.

    Annotations the server declares

    • title: Get remaining call time
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_batch_callsGet 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.No findings

    Why it is in this group

    • The name "get_batch_calls" says "get": a word for reading.
    Description, as the server wrote it
    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. Compliance: read-only, limited to this account's own batches. Use it after place_batch_calls to report results to the user. Read-only. For one call's transcript, use get_call with response_format='detailed'. To stop a single call, use cancel_call.

    Annotations the server declares

    • title: Get the progress of a batch of calls
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_callGet the status and written result of a call placed with place_phone_call (outcome, summary, pending question, transcript on request), optionally waiting for news.No findings

    Why it is in this group

    • The name "get_call" says "get": a word for reading.
    Description, as the server wrote it
    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. Compliance: read-only; transcripts are text only (no audio is recorded) and are kept 90 days at most. Use it to follow a call in progress (repeat until done=true), to see whether the voice agent is waiting for the user's answer (pending_question), and to read the final outcome and summary to report to the user. Read-only: it never places, changes or ends a call. Returns: status (scheduled, in_progress, retry_scheduled, completed, cancelled, failed), done, outcome (success, failed, voicemail, no_answer, busy, callback_requested, callee_objected), summary, pending_question {question_id, text}, new events since after_event_id, last_event_id and next_step. A call that is busy or not answered is retried automatically (status retry_scheduled), except on lines where every call needs a new request from the user (event callback_suggested: ask the user). callee_objected means the person asked not to be called again: the transcript was deleted and the number can no longer be called; tell the user.

    Annotations the server declares

    • title: Get call status and result
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_callsList this account's calls, newest first, and get for each one its call_id, phone number, status, outcome, task and one-line summary.No findings

    Why it is in this group

    • The name "list_calls" says "list": a word for reading.
    Description, as the server wrote it
    List this account's calls, newest first, and get for each one its call_id, phone number, status, outcome, task and one-line summary. Compliance: read-only, limited to this account's own calls; transcripts older than 90 days are deleted. Use it to find a call_id, to check whether a number was already called recently before placing a new call, or to answer questions such as 'what happened with my call to the garage?'. Read-only. For the full result and transcript of one call, use get_call with response_format='detailed'.

    Annotations the server declares

    • title: List calls
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write8
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:21 UTC, unchanged since Nov 7, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.dialyne.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://api.dialyne.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (6 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.dialyne.com/mcp: tools/list returned 12 tools to an anonymous client, including place_phone_call (destructive), answer_call_question (destructive), transfer_call_to_user (destructive), schedule_callback (destructive), cancel_call (destructive) and 3 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn1 info
  • The server marks "configure_agent_identity" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "read": a word for reading.

    What this check looks for
  • The description is 3,457 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: ".... To retry safely after an error or timeout, reuse the same idempotency_key."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http dialyne https://mcp.dialyne.com/mcp
claude mcp add --transport http dialyne https://mcp.dialyne.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__dialyne__get_call",
      "mcp__dialyne__list_calls",
      "mcp__dialyne__get_account_balance",
      "mcp__dialyne__get_batch_calls"
    ],
    "ask": [
      "mcp__dialyne__hold_call_question",
      "mcp__dialyne__configure_agent_identity"
    ],
    "deny": [
      "mcp__dialyne__place_phone_call",
      "mcp__dialyne__answer_call_question",
      "mcp__dialyne__transfer_call_to_user",
      "mcp__dialyne__schedule_callback",
      "mcp__dialyne__cancel_call",
      "mcp__dialyne__place_batch_calls"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dialyne. Review it before you use it.

Capability tags behind 8 rules
  • mcp__dialyne__place_phone_call untrusted-input
  • mcp__dialyne__answer_call_question untrusted-input
  • mcp__dialyne__transfer_call_to_user untrusted-input
  • mcp__dialyne__schedule_callback untrusted-input
  • mcp__dialyne__get_account_balance private-data, untrusted-input
  • mcp__dialyne__hold_call_question untrusted-input
  • mcp__dialyne__place_batch_calls untrusted-input
  • mcp__dialyne__configure_agent_identity untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.dialyne/dialyne/verify?hash=bbc02046af7a4a2afdebcfa7970b992a714c6298765c2629a3b3000ee736248f" | jq -e '.changed == false'

Pinned hash bbc02046af7a, from Nov 21, 2026, 09:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.dialyne/dialyne/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.dialyne/dialyne
[![Anlyon Radar](https://radar.anlyon.com/badge/com.dialyne/dialyne.svg)](https://radar.anlyon.com/servers/com.dialyne/dialyne)

Source: MCP Registry · repository. Synced Nov 7, 2026, 05:17 UTC.

Dialyne MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Dialyne MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 8 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Dialyne MCP server delete data?

Yes. 6 tools can delete, cancel or revoke something: place_phone_call, answer_call_question, transfer_call_to_user, schedule_callback, cancel_call and place_batch_calls.

Can the Dialyne MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Dialyne MCP server have?

12 tools: 6 destructive, 2 write, 4 read. place_phone_call, answer_call_question, transfer_call_to_user, schedule_callback, cancel_call, place_batch_calls, hold_call_question, configure_agent_identity and 4 more.

Does the Dialyne MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Dialyne MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Dialyne MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.