Eclipse Bazaar · products.json · verdicts.json · llms.txt

Eclipse Trunk MCP

The governed Twilio adapter: every call and text under consent + mandate.

status: in-developmentclass: mcpVoice & Telephony Adapters

Vendor: Cyan Eclipse Technologies

What it does

Tools

logs_read · send_sms_sim · place_call_sim · number_search · registration_status · recording_policy_get · recording_policy_set · receipt_list

Platforms

Certification

Bench verdict: CERTIFIED(simulator)

Certified scope: CERTIFIED(simulator) — Eclipse Bazaar Test Bench 2026-10-25, 16/17 checks pass, 1 na (U1 auth: stdio process boundary), 0 fail. Run by W-003 (Verity), suites/trunk.py. Run 1 FAILED card retained in results/ — bench-suite self-defect (T4 absolute receipt count vs cumulative suite ledger), fixed and re-run clean as run 2; no product defect.

Not tested:

  • Live Twilio account actions — the vendor's official MCP surfaces (docs discovery + Labs execution server) are the V1 wrap targets; V0 ships against Twilio-shaped fixtures + a local stub only, and the build-time probe of which vendor surface executes is a V1 step (spec 12).
  • Number provisioning and release — search only in V0; provisioning is T2 and release is T3 at V1 behind the owner account.
  • WhatsApp / RCS channel consent inheritance — spec 12 flags per-channel verification at build; no channel beyond voice/SMS is modeled in V0.

Bench scorecard (evidence): https://eclipsebazaar.com/cards/eclipse-trunk-mcp-2026-10-25-2.json

Pricing

Free local v0.1; family pricing TBD per spec

Install / verify

docker run -i ghcr.io/cyan-eclipse-technologies-llc/eclipse-trunk-mcp:latest

Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).