HonkIO MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to HonkIO Canadian SMS, email and consent-management tools: Do received-email opt-ins and CASL consent controls remain separate from default message-send authority?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Canadian SMS/email operations with verification, number management and compliance controls.

What we know

Hosted/local MCP over HonkIO's live messaging API for SMS, email, verification, Canadian numbers, webhooks, account controls and compliance.

Maintenance / activity evidence

@honkio/mcp 1.12.1 published 2026-10-01T23:00:00.516Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Messaging, number/account/webhook and compliance operations according to credential. Writes: Send SMS/email; Provision/release numbers; Create/rotate/revoke API keys; Change webhooks/suppressions/account state; Execute erasure workflows.
API key/OAuth.
Sensitive access: Contacts, Message bodies, Phone numbers, Account balance, API keys, Webhook payloads

Can contact users and spend account balance; use test keys, consent controls and opt-in inbound reads.
Inbound text is explicitly treated as untrusted content.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do received-email opt-ins and CASL consent controls remain separate from default message-send authority?

The bounded review of the publisher's documented HonkIO Canadian SMS, email and consent-management tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Can contact users and spend account balance; use test keys, consent controls and opt-in inbound reads.
Inbound text is explicitly treated as untrusted content.
Messaging, number/account/webhook and compliance operations according to credential.
API key/OAuth.
Customer data is stored in Canada while processing may transit elsewhere; package docs give specific inbound-email retention windows.
Reviewed write actions: Send SMS/email; Provision/release numbers; Create/rotate/revoke API keys; Change webhooks/suppressions/account state; Execute erasure workflows
Sensitive access: Contacts, Message bodies, Phone numbers, Account balance, API keys, Webhook payloads
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Live sending/receiving requires verified setup and can incur charges.
CASL consent is enforced for commercial SMS; DNCL check is not available.
Inbound email reads are opt-in because third-party text can contain prompt injection.
Some REST features are intentionally not exposed as MCP tools.

Original activity observations

@honkio/mcp 1.12.1 published 2026-10-01T23:00:00.516Z

Technical identity

npm/@honkio/mcp

Exact implementation source: https://www.npmjs.com/package/@honkio/mcp ↗
Reviewed resource type: MCP Server
Repository identity: jeffcaldwellca/honkio
Package identity: npm:@honkio/mcp
Service endpoint: https://mcp.honkio.ca/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@honkio/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
honkio.ca/docs/api
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
honkio.ca/docs/webhooks/events
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
honkio.ca/docs/sms/pricing-and-limits#limits
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
honkio.ca/legal/privacy
Source material retained for this review.
Includes references whose attribution is not established.
GitHub repository ↗
jeffcaldwellca/honkio
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Hosted MCP supports browser OAuth or HONKIO_API_KEY as Authorization Bearer; live/test account modes differ.
publisher install or stdio launch · Claude Code only · Publisher instructions
claude mcp add --transport http honkio https://mcp.honkio.ca/mcp
Configure / authenticate
MCP100 setup guide
HonkIO distinguishes test and live keys; begin with test key, which simulates sends at no charge. Never use live number provisioning/sending for Setup check.
Check connection
Suggested check
Use a test API key to inspect account/tool status or dry-run verification. Do not send live SMS/email, provision a number, or incur charges.
Remove / uninstall / revoke
MCP100 setup guide
If you added this integration to Claude Code under the registration name `honkio`, run `claude mcp remove honkio` to unregister that client entry. In Claude Desktop, Cursor, VS Code or another host, delete/disable the corresponding named MCP registration in that host's settings and restart/reconnect. If you installed an npm package globally or operate a separate HTTP server, uninstall/stop it with its original deployment method. This does not delete user data or revoke service credentials.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate provider credential revocation · publisher documented: HonkIO: https://honkio.ca/dashboard/keys allows immediate API key revocation and hosted OAuth-agent disconnection. Official MCP tool `revoke_api_key` revokes a key; `rotate_api_key` replaces it. These tools mutate credentials; document, never execute for verification.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove honkio

Official Documentation & Sources

What it does

Hosted/local MCP over HonkIO's live messaging API for SMS, email, verification, Canadian numbers, webhooks, account controls and compliance.

Capability: Communication
Resource type: MCP Server
Industry: Telecommunications
Best fit: Canadian SMS/email operations with verification, number management and compliance controls.

Representative uses

Send SMS/email
Verify phones
Provision/release numbers
Inspect deliveries/dead letters
Register/replay webhooks
Read inbound messaging when explicitly enabled

Limitations

Live sending/receiving requires verified setup and can incur charges.
CASL consent is enforced for commercial SMS; DNCL check is not available.
Inbound email reads are opt-in because third-party text can contain prompt injection.
Some REST features are intentionally not exposed as MCP tools.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: API key/OAuth.
Permissions: Messaging, number/account/webhook and compliance operations according to credential.
Data handling: Customer data is stored in Canada while processing may transit elsewhere; package docs give specific inbound-email retention windows.
Cost: usage_based
Risk and cautions: Can contact users and spend account balance; use test keys, consent controls and opt-in inbound reads.

Access scope and cautions

Write actions: Send SMS/email Provision/release numbers Create/rotate/revoke API keys Change webhooks/suppressions/account state Execute erasure workflows
Sensitive access: Contacts Message bodies Phone numbers Account balance API keys Webhook payloads
Risk level: high
Security notes: Inbound text is explicitly treated as untrusted content.

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Send SMS/email; Verify phones; Provision/release numbers; Inspect deliveries/dead letters; Register/replay webhooks; Read inbound messaging when explicitly enabled.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @honkio/mcp. Recorded endpoint: https://mcp.honkio.ca/mcp. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: HONKIO_API_KEY (local); API_URL (optional); HONKIO_MCP_READ_INBOX=1 (optional inbound). No configuration values are supplied here. Prerequisites: HonkIO account; Node.js 20+ local; phone verification/provisioned number for live messaging. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: HonkIO API key or hosted OAuth; test/live keys are distinct.

Can it modify data or perform write operations?

Documented write actions include: Send SMS/email; Provision/release numbers; Create/rotate/revoke API keys; Change webhooks/suppressions/account state; Execute erasure workflows. Recorded permission boundary: Messaging, number/account/webhook and compliance operations according to credential.

What data-handling boundary should I consider?

Customer data is stored in Canada while processing may transit elsewhere; package docs give specific inbound-email retention windows. Recorded sensitive-access context: Contacts; Message bodies; Phone numbers; Account balance; API keys; Webhook payloads.

What limitations and risks should I check before use?

Can contact users and spend account balance; use test keys, consent controls and opt-in inbound reads. Live sending/receiving requires verified setup and can incur charges. CASL consent is enforced for commercial SMS; DNCL check is not available. Inbound email reads are opt-in because third-party text can contain prompt injection. Some REST features are intentionally not exposed as MCP tools. Inbound text is explicitly treated as untrusted content. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is usage based. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.

Is this an official MCP?

HonkIO is listed as First-party MCP in MCP100’s current evidence.