HonkIO
ca.honkioPublished by honkio.caOfficial publisherv1.15.1Updated Nov 7, 2026
Canadian SMS and email API for AI agents: send SMS and email, verify phones, handle CASL consent.
Overview
HonkIO is a Canadian SMS and email API for AI agents, letting an assistant send messages, verify phone numbers and handle CASL consent.
- What you can do
- Send SMS and email messages from an assistant.
- Verify phone numbers and manage CASL consent records.
- Optionally register two tools for reading received email, enabled per connection.
- Connect either to a hosted remote endpoint or as a local npm process over stdio.
- When to use it
- Useful when an assistant needs to send SMS or email to Canadian recipients, or when a workflow must record consent and verify phone numbers before messaging.
- Requirements
- A HonkIO API key, supplied as the HONKIO_API_KEY environment variable for the local package or as an Authorization bearer header for the remote endpoint. OAuth is declared as required. The remote endpoint needs network access; the local option runs via npx with Node.js. Reading received email additionally requires HONKIO_MCP_READ_INBOX or the X-HonkIO-Read-Inbox header set to 1.
Installation
In SourceWeft
- Open HonkIO in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/ca.honkio%2Fmcp/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. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"honkio": {
"type": "http",
"url": "https://mcp.honkio.ca/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
11- v1.15.1LatestNov 7, 2026
- v1.14.1Nov 3, 2026
- v1.14.0Nov 1, 2026
- v1.13.2Oct 29, 2026
- v1.13.1Oct 17, 2026
- v1.13.0Oct 16, 2026
- v1.12.2Oct 14, 2026
- v1.12.1Oct 2, 2026
- v1.11.1Sep 27, 2026
- v1.9.0Sep 26, 2026
- v1.5.0Sep 16, 2026
Score
75% 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 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
- License10 pts
Declare a license in the repository or the registry entry.