Skip to main content

MCP Server General FAQ

Mark Yatman
Updated

  • What data is available through the MCP Server to the LLM?

    • Data available to query when using the Channel99 MCP server connecting with your LLM, this schema can be found in the support documentation HERE.

  • Is there any personal data shared with the LLM from Channel99

    • No Contact information, user names, passwords or emails are shared through the Channel99 connection with any LLM. All data is shared at the domain level to prevent security/compliance complications.

  • Where is data processed and stored?

    • Data is stored within the Channel99 secured databases and only queried 

  • Does the model vendor have network access to anything other than the MCP tools we explicitly connect?

    • No

  • Is your MCP Server URL a universal URL or do you allow users to create custom MCP URLs?

    • Universal URL

  • What Read/Write Permissions does the MCP connection have to the Channel99 databases? 

    • Read Only

  • What auth standard do you use?

    • OAuth 2.1

  • Is data encrypted in transit and at rest?

    • Yes

  • Is there any other Documentation for Connection to well known LLMs?

  • Who within Channel99 (employees/teams) can access customer data and how is access audited?

    • Customer data is segregated by customer (database-per-customer). Channel99 uses monitoring and change logs to audit activity. For a precise list of roles and the employee access model (who can view decrypted data, privileged access process, and audit trail details), we should publish the internal access policy and an audit summary on request

  • What compliance attestations and security testing do you have?

    • Yes. Channel99 provides a read-only SQL API and export methods. Website ingestion data can be removed on request.

  • Do you share customer data with third parties?

    • Channel99 operates explicit vendor integrations (ad platforms and contracted data providers). Data is shared only with those third-party platforms for which a connector is configured and authorized by the customer. Examples: Google, Microsoft, LinkedIn, Facebook, Demandbase.

Related articles

Comments

0 comments

Please sign in to leave a comment.