Try a new MCP server without guessing what your client supports
Use the July 2026 protocol revision and a read-only tool to check a client–server pairing.

In this article
Identify the revision on both ends
The July 28, 2026 revision introduced a stateless core. Older examples often start with an initialize handshake. Write down the exact host, server package, SDK version and supported revisions. A recent upload date on a server package says little about which protocol its client speaks.
Connect one bounded tool
Choose a maintained server with a harmless read-only operation and documented sample input, such as reading a test note. Create a disposable fixture containing the phrase “cobalt lantern.” In the host’s MCP settings, use the server’s documented executable and arguments for stdio, or its documented endpoint for HTTP. Grant access only to the fixture where the server supports scoping.
Test discovery separately from execution
Use the host or MCP Inspector to list the advertised tools. Record one tool name and its input schema. Invoke it with the fixture, then with a missing filename. A useful pairing returns the known phrase on success and an intelligible error for missing input. Save the actual results beside the client and server versions.
Diagnose the right layer
If there is no connection, check the launch command or URL and transport first. If discovery fails, compare supported revisions. If discovery succeeds but a call fails, inspect the input schema and permissions. Remove the test entry after the trial and revoke any temporary credentials you issued.
Know which process owns the failure
The host is the application the user talks to. Its MCP client connects to a server that publishes capabilities. With stdio, the client usually starts a child process. Check the executable path, the working directory and which configuration that child receives. With HTTP, the server runs separately. Start with its documented endpoint and authentication requirements, then check what the client reports for discovery. This decomposition keeps you from treating every error as a model failure.
Test one real call after discovery. A server can list a tool correctly but reject the arguments, lack access to the file or return a result the host cannot display. Capture the exact tool name, the shape of the inputs and the error class. Keep credentials and private fixture contents out of shared logs.
What to verify before an upgrade
Build a compatibility matrix with the current client/server pair and one candidate upgrade. For each pair, check connection, discovery, one successful call and one predictable failure. Change one version at a time. An extension such as Tasks adds capabilities only when the pair supports the relevant extension. A core protocol date alone leaves that question open.
Choose an example with clear expected behavior. A notes lookup should return the fixture text for a valid note and a useful error for a missing note, while leaving the fixture untouched. If a new server asks for broad permissions to demonstrate a read-only feature, first see whether it can be run with a separate account or a sample directory. Document how to restore the previous server configuration.
Primary sources
MCP · Protocol versioning · MCP · Released roadmap update · MCP Ruby SDK · Protocol versions · MCP InspectorRead next Local or cloud? Follow the work.