MCP Server Check
Connect to a remote MCP server, inspect its tools, and run a confirmed call.
Connect a server
Public HTTPS endpoints on port 443 only. Redirects and private networks are blocked.
- URL & securityWaiting
- AuthenticationWaiting
- Protocol negotiationWaiting
- Tool discoveryWaiting
Select a tool to review its schema and prepare a call.
Input JSON Schema
Read onlyArguments
JSON object · 64 KiB maxResult
Credentials pass through ComUtil only for the requested connection and are retained only inside an encrypted browser-session envelope.
Model Context Protocol servers expose tools, resources, and prompts that an AI client can call. A server check confirms that a remote endpoint completes the MCP handshake, reports the protocol version it negotiated, lists the tools it advertises, and returns a usable result for a real call, all before you wire the server into Claude Code, Codex, or any other client configuration.
The check runs in stages. The URL is validated first: only public HTTPS endpoints on port 443 are accepted, and redirects, IP-literal hosts, and private or reserved addresses are refused. The client then opens a Streamable HTTP session and negotiates a protocol version through initialize, calls tools/list, and renders each tool with its input schema. A tools/call runs only after you confirm the exact tool and arguments, because the annotations a server publishes about its own tools are not trusted.
- Confirming that a freshly deployed remote MCP endpoint answers initialize and tools/list
- Checking whether an OAuth 2.1 server completes authorization before you add it to a client config
- Reproducing a failing tool call without editing your local client configuration
- Reading the input schema a server advertises before writing prompts or code against it
- Verifying a hosted MCP endpoint from a machine that is not your development box
- The protocol version negotiated during initialize
- Every advertised tool with its description and input JSON Schema
- Whether the endpoint accepted Streamable HTTP, since legacy SSE is not supported
- The authentication outcome for Bearer tokens, API keys, and OAuth 2.1
- Text, structured content, and metadata returned by a confirmed tool call
https://mcp.example.com/mcp
Protocol negotiated, 12 tools discovered
Authorization: Bearer <token>
Credential accepted, tools/list returned 3 tools
{"query": "release notes", "limit": 5}
Text plus structured content returned in 412 ms
Does this host or run an MCP server for me?
No. It connects to a server you already run or subscribe to and reports what that server answers. Nothing is deployed or hosted here.
Why are only HTTPS endpoints on port 443 accepted?
The connection is opened from the ComUtil side, so localhost, private ranges, IP-literal hosts, and redirects are refused. Without that limit the check could be pointed at infrastructure that is not yours.
Where do my tokens and API keys go?
They are used for the connection you asked for and kept only inside an encrypted browser-session envelope. It expires within eight hours and stops working when you disconnect or the browser session ends.
Does it support the legacy HTTP with SSE transport?
No. Only Streamable HTTP is supported. If a server still exposes the older SSE endpoint, point the check at its Streamable HTTP path instead.
Can a tool run without my approval?
No. Every call needs a final confirmation that shows the exact tool name and arguments, because a server can describe its own tools inaccurately.