Data handling and build provenance for the hosted Remote GitHub MCP service

[ChanghuLiu]

I am evaluating the hosted Remote GitHub MCP endpoint (https://api.githubcopilot.com/mcp/) for a read-only issue_read integration. The public documentation explains how the remote server is built from this repository and updated, but I could not find service-specific answers to these two questions:

1. Are MCP JSON-RPC tool-call arguments and results (request/response bodies) persisted or included in server/platform logs? If so, what retention period and controls apply? Please distinguish the Remote MCP service from Copilot Chat conversation history and ordinary GitHub audit logs.
2. Is a build/revision identifier exposed by the hosted endpoint, or can maintainers confirm how a deployed api.githubcopilot.com release maps to a source commit?

I understand internal infrastructure details may not be public. If these questions belong with GitHub Support or are answered in a Trust Center document, a pointer would help. No credentials or customer data are included here.