AgentPhone-Apex

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

Multi-channel voice and SMS gateway interface for AI communication.

VerifiedSSEWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote MCP gateway that lets an assistant send voice calls and SMS messages through multiple communication channels.

What you can do
Send voice calls and SMS messages through a multi-channel gateway, as described for AI communication. No tool list is published, so the exact call, message and status operations are not documented here. Premium settlement is mentioned, implying some usage is paid.
When to use it
Consider it when an assistant needs to place voice calls or send SMS messages across several channels from a hosted endpoint, rather than through a local package.
Requirements
A remote SSE endpoint; nothing to install locally. No authentication is declared, but a payment-signature header is required for premium settlement, and the manifest lists no other credentials or environment variables.
Before you install
The payment-signature header carries a Base64-encoded EIP-3009 TransferWithAuthorization signature, which authorizes a blockchain payment; treat it as a spending credential and expect charges for premium use. Sending calls or messages reaches real recipients, so review what the assistant sends. The tool set is undocumented, so verify behavior before relying on it.

Installation

In SourceWeft

  1. Open AgentPhone-Apex in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2Fagent-phone/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agentphone-apex": {
      "type": "sse",
      "url": "https://agent-phone-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.