Checking a remote MCP server ​

A project can store someone else's MCP server, capture its catalog, and call a tool again with the same arguments. This is not an MCP key. A key is issued on the profile and lets an agent call ComplexQA.

The server address is https only. Auth kind is Bearer or OAuth. A server without authorization is not connected.

Next ​

1. Add a server: a Bearer token or OAuth consent, a catalog capture, and a fixed snapshot.
2. Save and call a tool: an argument template and another run.

The snapshot lists sections, tools, resources, resource templates, and prompts. A resource, a resource template, and a prompt are read from the catalog. They are not executed. Only a tool is called.

On the snapshot and on the result, protocol revision is one of 2025-03-26, 2025-06-18, 2025-11-25, 2026-07-28. That is the revision ComplexQA used to speak with the server that time.

A server with status Disabled is not captured and is not called. Set the status back to Active to continue. The address of a saved server does not change: a new address is a new server.