
Botphone
io.github.GriffdenPublished by GitHub account Griffdenv1.0.0Updated Oct 27, 2026
Give your Muse a phone number. BotPhone answers your business line and reports every call back.
The publisher's own server: BotPhone
Overview
BotPhone gives an AI assistant a business phone line that answers calls and reports each call back.
- What you can do
- Answer incoming calls on a business phone line through the hosted BotPhone service.
- Receive reports on every call that came in, so the assistant can review or summarize them.
- No tool list is published, so the exact actions available are not documented in the supplied material.
- When to use it
- Consider it when a business wants an AI assistant to handle its phone line and keep a record of incoming calls, for example a receptionist-style setup for a small team.
- Requirements
- A remote streamable HTTP endpoint at auth.botphone.tel; no packages, environment variables or headers are declared. The manifest declares no authentication, though the endpoint host name suggests an auth step may be involved. A BotPhone business phone line is implied by the product description.
Installation
In SourceWeft
- Open Botphone in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. 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.Griffden%2Fbotphone/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"botphone": {
"type": "http",
"url": "https://auth.botphone.tel/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 21, 2026
Score
28% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 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.