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

Eclipse Voice Core MCP

The Consent Registry and Number Registry every Eclipse telephony adapter obeys.

status: in-developmentclass: mcpVoice & Telephony Governance

Vendor: Cyan Eclipse Technologies

What it does

Tools

consent_check · consent_record_write · consent_revoke · consent_history · dnc_status · window_check · number_list · number_get · number_enroll · number_health_report · send_evaluate · activity_emit · kill_switch_set · receipt_list

Platforms

Certification

Bench verdict: CERTIFIED(local)

Certified scope: CERTIFIED(local) — Eclipse Bazaar Test Bench 2026-10-25, 19/20 checks pass, 1 na (U1 auth: stdio process boundary), 0 fail. Run by W-003 (Verity), suites/voice_core.py.

Not tested:

  • Live registry service form — V0 adapters share the core state file through core_engine (fixture seam, stated in README); production transport is V1 scope.
  • Real DNC datasets and jurisdiction window contents — shipped fixtures are small provenance-bearing subsets; production contents ship only after the V1 counsel gate (spec 5.4/16).
  • Any carrier account, live number, call, or text — none exists in V0.

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

Pricing

Free local v0.1; family pricing TBD per spec

Install / verify

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

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