"Debugging WebRTC SDK Implementation Issues in Visual Studio 2019" matching MCP tools:

• get_api_operation

  Cannon Studio

  Return public docs for Cannon Studio developer API operations and payload shapes. Public read-only: no auth, no state changes, no charges; use this before estimate_generation_cost or create_generation_request when operation/input fields are unclear.

  Connector

• buy_studio

  moltdj

  Buy a Studio subscription for $25 USDC (30 days). Requires authentication. This endpoint returns HTTP 402 with x402 payment instructions. Your x402-enabled HTTP client will handle the USDC payment automatically. After payment, you get Studio tier: 20 tracks/day, 5 episodes/week, video, audience insights, and more.

  Connector

• get_contact_info

  symbols-of-wealth-studio

  Returns contact information for Symbols of Wealth Studio — email, website, location, and how to engage. Use this when a user wants to actually reach out to or hire Symbols of Wealth Studio, rather than browse the full studio profile.

  Connector

• get_contact_info

  Symbols of Wealth Studio

  Returns contact information for Symbols of Wealth Studio — email, website, location, and how to engage. Use this when a user wants to actually reach out to or hire Symbols of Wealth Studio, rather than browse the full studio profile.

  Connector

• run_code

  Hatchable

  Execute arbitrary JS in the project's isolate runtime. The SDK is pre-imported into local scope — `db`, `auth`, `email`, `storage`, `ai`, `agent`, `cache`, `knowledge`, `memory`, `tasks`, `scheduler`, `browser`, `run`, `approval` are ready to use without import. `process.env` and global `fetch` also work. `return` to produce the `result` field. Top-level `import` and dynamic `import('hatchable')` are NOT supported in this REPL — the bindings above are how you reach the SDK. Use this as a REPL: probe the database, verify a computation, test an API shape before committing it to a file. Nothing is persisted — the snippet runs once and disappears. Caps: 5s default timeout (max 30s), 256 KB max source length. Example: run_code({ project_id, code: ` const { rows } = await db.query("SELECT count(*) FROM users"); return rows[0]; `})

  Connector

• get_checkout_link

  Cannon Studio

  Return the first-party Cannon Studio checkout or inquiry URL for a selected offering. Public read-only: no auth, no state changes, no charges; use list_offerings first to get a valid product_key.

  Connector

• parse_sdp

  Sipflow

  [cost: free (pure CPU, no network) | read-only] Parse a Session Description Protocol body and return a structured view: origin, session, timing, per-media codecs (rtpmap + fmtp), direction, DTLS setup + fingerprint, ICE credentials + candidates, rtcp-mux, BUNDLE groups, fax-relay (`m=image udptl t38` plus the `a=T38Fax*` attribute family), and crypto attributes. Useful for debugging WebRTC ↔ SIP interop (codec negotiation, DTLS-SRTP fingerprints, ICE candidate gathering, bundle alignment), and for inspecting fax negotiation (T.38 reinvite SDP, `T38FaxMaxBuffer`/`T38FaxUdpEC`/`T38FaxRateManagement`) without an LLM having to re-derive the SDP grammar each call. Pair with: `compare_sdp_offer_answer` when the user has both halves of the negotiation (including T.30→T.38 reinvites); `webrtc_sip_checklist` for the bridge-config angle.

  Connector

• baselight_sdk_get_results

  baselight

  Retrieve results from a previously executed SDK job using the resultId from `sdk-query-execute`. If the query is complete, returns results immediately. If still pending, polls for up to 1 more minute. Use this after `sdk-query-execute` returns PENDING status.

  Connector

• list_sessions

  waysway

  List all in-memory session summaries. Useful for debugging only.

  Connector

• places

  connect

  Places (locations) in the catalogue — studios, galleries, museums, storage, fair venues. action "list": find places or resolve a place_id (optional filters: search, place_type) — read-only. action "create": add a new place — write. TRIGGER for create: "my studio in Bushwick," "stored at," "I keep it at," or any mention of a specific location for works. Places are optional — only create when the user mentions a location; include city/country when known.

  Connector

• generate_scaffold

  Senzing

  Generate SDK scaffold code for common workflows. Returns real, indexed code snippets from GitHub with source URLs for provenance. Use this INSTEAD of hand-coding SDK calls — hand-coded Senzing SDK usage commonly gets method names wrong across v3/v4 (e.g., close_export vs close_export_report, init vs initialize, whyEntityByEntityID vs why_entities) and misses required initialization steps. Languages: python, java, csharp, rust. Workflows: initialize, configure, add_records, delete, query, redo, stewardship, information, full_pipeline (aliases accepted: init, config, ingest, remove, search, redoer, force_resolve, info, e2e). V3 supports Python and Java only. Returns GitHub raw URLs — fetch each snippet to read the source code.

  Connector

• fix_site

  AEO Scanner

  Generate complete fix code for all AI visibility issues across AEO, GEO, and Agent Readiness. Returns working code you can apply directly — schema generation, robots.txt, sitemap, llms.txt, meta tags, structured data, citation signals, entity markup. Also returns two-tier score projections: quick wins (critical + high fixes only) and full implementation ceiling (all fixes). Content recommendations include research citations. Run scan_site first to see which issues exist. Pay per call ($5.00) via x402 — USDC on Base or Solana. On payment_required, the response includes the full x402 payload with payTo/amount/asset.

  Connector

• link_work_to_bibliography

  connect

  Associate a work with a bibliography entry — recording that a specific publication references or illustrates this work. Include page reference, plate number, or illustration details if available. Never ask the user for UUIDs — resolve work_id via search_works, and bibliography_id from the create_bibliography response. Side effect: if the work is signed, this puts it in `pending_resignature` — the authenticator must re-confirm in Raisonnai before a new VC issues. Tell the user. After success, ask if they'd like to see the updated work. Then call get_work to show the visual card.

  Connector

• get_device

  Trillboards DOOH Advertising

  Get detailed information about a specific device. WHEN TO USE: - Checking status of a single device - Getting device configuration details - Debugging device issues RETURNS: - device_id: Your internal device ID - trillboards_device_id: Internal Trillboards ID - fingerprint: Device fingerprint - name: Device name - status: online/offline - last_seen: Last heartbeat timestamp - location: Location details - specs: Device specifications - stats: Impression and earnings stats EXAMPLE: User: "Get details for vending machine 001" get_device({ device_id: "vending-001-nyc" })

  Connector

• tascan_list_issues

  TaScan

  List all issues for a task list (event). Returns open, acknowledged, and resolved issues with severity, type, and category. Use this to discover issues that need AI analysis via tascan_analyze_issue.

  Connector

• get_sdk_reference

  Senzing

  Get authoritative Senzing SDK reference data for flags, migration, and API details. Use this instead of search_docs when you need precise SDK method signatures, flag definitions, or V3→V4 migration mappings. Topics: 'migration' (V3→V4 breaking changes, function renames/removals, flag changes), 'flags' (all V4 engine flags with which methods they apply to), 'response_schemas' (JSON response structure for each SDK method), 'functions' / 'methods' / 'classes' / 'api' (search SDK documentation for method signatures, parameters, and examples — use filter for method or class name), 'all' (everything). Use 'filter' to narrow by method name, module name, or flag name

  Connector

• get_provenance_visual

  connect

  Display provenance as an interactive visual timeline. TRIGGER: "show provenance," "ownership history," "who owned this." For text-only provenance, use get_provenance instead.

  Connector

• test_webhook

  Trillboards DOOH Advertising

  Send a test event to a webhook endpoint. WHEN TO USE: - Verifying webhook endpoint is working - Testing integration during development - Debugging webhook delivery issues RETURNS: - success: Boolean indicating delivery success - response_code: HTTP response code from endpoint - response_time_ms: Response time in milliseconds - error: Error message if delivery failed EXAMPLE: User: "Test my webhook with a device.online event" test_webhook({ webhook_id: "wh_mmmpdbvj_8b7c5a59296d", event: "device.online" })

  Connector

• detect_runtime_capabilities

  webEmbedding

  Report the hosted Apps SDK intake runtime capabilities and explain when the local stdio MCP is required.

  Connector

• get_agency_info

  RE/MAX Studio 76 — Imóveis

  Retorna informações da RE/MAX Studio 76: contato, endereço, WhatsApp, horários. Use este tool para incluir o contato da imobiliária na resposta ao usuário, especialmente após apresentar imóveis de interesse.

  Connector