Callout MCP server
jp.callout/calloutcallout.jpstreamable-httpv1.2.0Scanned
Places real phone calls for you in Japanese or English and returns the result and transcript.
5 tools: 1 can delete or cancel things and 4 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Callout MCP server can do
The Callout MCP server is published by callout.jp, a domain the MCP Registry verified. It has 5 tools. It can delete or cancel things (1 tool: callout_create_call). 4 tools only read.
1 tool brings in text other people can write (callout_create_call).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 1.2.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.
5 tools
Deletes or cancels 1Claude Code: deny
callout_create_callCreate an outbound phone call via the Callout voice-agent service.Reads text others writeNo findings
Why it is in this group
- The name "callout_create_call" says "create": a word for a change.
- The input addresses people (input.to): what it sends 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 Create an outbound phone call via the Callout voice-agent service. Returns immediately with a call_id — the call itself runs asynchronously. This is a side-effecting action that places a real phone call. A call lasts up to 4 minutes (one credit); for complex matters pass max_duration_seconds=480 to allow 8 minutes (a second credit, charged only if the call runs past 4 minutes). If the call may end with a booking, give a contact number from the destination's country (the hotel's or a tour guide's if the customer has none): a call whose objective or context holds an overseas number is not placed unless allow_foreign_contact_number=true. A booking, reservation, appointment or order whose objective and context give no phone number for the customer is refused with CALLBACK_NUMBER_NEEDED: ask the customer for the number the business has for them, add it ("Callback number: ...") and call again, or pass skip_callback_number=true.
Annotations the server declares
- title: Place a phone call
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Only reads 4Show 4 read-only tools
callout_get_call_resultGet the structured result of a completed call.No findings
Why it is in this group
- The name "callout_get_call_result" says "get": a word for reading.
Description, as the server wrote it Get the structured result of a completed call. Use this to decide what to do next in a workflow. outcome is one of ok (someone answered and the conversation took place, whatever came of it: read summary), needs_human (the other side will only deal with the user, or the matter needs the user's decision), needs_website (they said it must be done online), voicemail (an answering machine picked up and the agent left a message), voicemail_no_message (an answering machine or a no-answer announcement picked up and no message was left), fax, no_answer, busy, failed or unknown; next_recommended_action is none, retry_call, use_website, ask_user (the user must decide or supply something) or manual_followup; answered_by is "machine" or "fax" when the agent heard one, else null; voicemail_message is "left" (the message states who called and why), "unable" (no recording was offered, or only a goodbye was said) or "declined_by_agent" (the agent's instructions said not to leave one) when a machine picked up, else null. When someone spoke on the call, summary says what was said and how it ended, written from a machine transcript in the language of the call's instructions, and result_data has nextStep (what to do now), missingDetails (what the other side needed and the agent could not give: add them before calling again) and unclearPhrases (what could not be made out, quoted as heard). Right after a call ends this tool waits up to 45 seconds for that result.
Annotations the server declares
- title: Get call result
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
callout_get_call_statusGet the current status of a Callout call: queued (not dialed yet), initiated, ringing, in-progress (answered), or once it has ended Twilio's final status (completed, no-answer, bus…No findings
Why it is in this group
- The name "callout_get_call_status" says "get": a word for reading.
Description, as the server wrote it Get the current status of a Callout call: queued (not dialed yet), initiated, ringing, in-progress (answered), or once it has ended Twilio's final status (completed, no-answer, busy, failed, canceled).
Annotations the server declares
- title: Get call status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
callout_get_transcriptGet the transcript of a completed call.No findings
Why it is in this group
- The name "callout_get_transcript" says "get": a word for reading.
Description, as the server wrote it Get the transcript of a completed call.
Annotations the server declares
- title: Get call transcript
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
callout_wait_for_call_completionWait until a call reaches a terminal status or the timeout is reached.No findings
Why it is in this group
- The name "callout_wait_for_call_completion" says "wait": a word for reading.
Description, as the server wrote it Wait until a call reaches a terminal status or the timeout is reached. Useful for workflows where the call takes 1-3 minutes.
Annotations the server declares
- title: Wait for a call to end
- 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 private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- 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.
Looked at Nov 15, 2026, 13:20 UTC, unchanged since Nov 15, 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
- 1
- 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.callout.jp/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://mcp.callout.jp
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 destructive). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.callout.jp/mcp: tools/list returned 5 tools to an anonymous client, including callout_create_call (destructive)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http callout https://mcp.callout.jp/mcpclaude mcp add --transport http callout https://mcp.callout.jp/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__callout__callout_get_call_status",
"mcp__callout__callout_wait_for_call_completion",
"mcp__callout__callout_get_call_result",
"mcp__callout__callout_get_transcript"
],
"ask": [],
"deny": [
"mcp__callout__callout_create_call"
]
}
}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 callout. Review it before you use it.
Capability tags behind 1 rule
- mcp__callout__callout_create_call 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/jp.callout/callout/verify?hash=175f632225ebdae73a89517563f99d76cc2c62b0c818fd35ebbef6a6ec596ba5" | jq -e '.changed == false'Pinned hash 175f632225eb, from Nov 15, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/jp.callout/callout/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/jp.callout/callout)Source: MCP Registry. Synced Nov 15, 2026, 07:17 UTC.
Callout MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Callout MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 0 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 Callout MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: callout_create_call.
Can the Callout 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 Callout MCP server have?
- 5 tools: 1 destructive, 4 read. callout_create_call, callout_get_call_status, callout_wait_for_call_completion, callout_get_call_result and callout_get_transcript.
Does the Callout MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Callout MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Callout MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.