Five steps
The steps
- Find the endpoint. A Streamable HTTP server has one URL path for every message, such as https://example.com/mcp. Use the one its documentation gives.
- Send initialize. POST a JSON-RPC initialize request with a protocol version, your capabilities and a client name. Send an Accept header that lists both application/json and text/event-stream.
- Keep the session headers. If the answer carries an Mcp-Session-Id header, send it on every later request, with MCP-Protocol-Version set to the version the server agreed.
- Send notifications/initialized. POST the notification. It has no id, and the server answers 202 with no body.
- List the tools. POST tools/list. If the answer carries a nextCursor, send it back in params.cursor to get the next page.
Copy and paste
With curl
These run against PageVerified's own endpoint, which lists its tools without a key. Swap in the URL of the server you are testing.
1. initialize
curl -si -X POST https://pageverified.com/mcp \
-H "content-type: application/json" \
-H "accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"curl-test","version":"1.0.0"}}}'
PageVerified answers HTTP 200 with JSON:
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"resultType": "complete",
"protocolVersion": "2025-11-25",
"capabilities": {
"tools": {}
},
"serverInfo": {
"name": "com.pageverified/tools",
"version": "<server version>"
}
}
}
The protocol requires protocolVersion, capabilities and serverInfo. Other servers may add or leave out the rest. A server may answer with a different protocolVersion from the one you sent. Use the one it answers with from then on, or stop if your client does not support it.
2. notifications/initialized
curl -si -X POST https://pageverified.com/mcp \
-H "content-type: application/json" \
-H "accept: application/json, text/event-stream" \
-H "mcp-protocol-version: 2025-11-25" \
-d '{"jsonrpc":"2.0","method":"notifications/initialized"}'
The answer is 202 Accepted with an empty body. If the server gave you an Mcp-Session-Id, add it as a header here and below.
3. tools/list
curl -si -X POST https://pageverified.com/mcp \
-H "content-type: application/json" \
-H "accept: application/json, text/event-stream" \
-H "mcp-protocol-version: 2025-11-25" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'
The answer holds result.tools: one object per tool with a name, a description and an inputSchema, a JSON Schema for its arguments. Some servers add a title and annotations.
Reading the answers
Scroll the table horizontally to see all fields.
What each answer means| Answer | What it means |
|---|
| 200 with JSON | A normal reply. Check that id matches your request and look for result or error. |
|---|
200 with text/event-stream | The server replied as a stream. The JSON-RPC answer is in a data: line of an event. |
|---|
| 202, empty body | The right answer to a notification. |
|---|
401 with WWW-Authenticate: Bearer | The server wants a credential. Its protected resource metadata says where to get one. |
|---|
| 405 to a GET | Allowed by the protocol: the server offers no stream on GET. Test it with POST. |
|---|
| 404 after it worked before | A session the server ended. Send initialize again without the old session header. |
|---|
A JSON-RPC error | The server understood the request and refused it. The code and message say why. |
|---|
Common failures
- 406 or 415. Usually the Accept or Content-Type header is missing or wrong. Send both values in Accept and
application/json as the Content-Type. - An answer about the protocol version. Send a version the server supports, or read the versions it lists in the error.
- An event stream that starts with an endpoint event. That is the older HTTP+SSE transport, which the protocol has deprecated. Its handshake works differently.
- An HTML page. You have the site, not the MCP endpoint. Look for the endpoint in the documentation or in
/.well-known/mcp/server-card.json.
No curl needed
Let the free tester do it
The MCP server tester sends a GET first. Only if that answer shows an MCP server does it run steps 2 to 5 and show the transport, the protocol version, whether authorization is required and up to 50 tool names. A server that answers the GET with a bare 405 has not proved it is an MCP server, so the tester POSTs nothing and says so. The protocol allows that answer, and PageVerified's own endpoint gives it, so test such servers with curl as above. It refuses private network addresses. The same result is JSON at /api/v1/check/mcp?url=....
mcp_inspect (2 credits) returns the full tool list for an agent: descriptions, input schemas and annotations, labelled as untrusted third-party text.
Before you call a tool
Listing tools changes nothing. Calling one can: tools can write files, send messages or spend money. Call a tool only on a server you are willing to trust with that action, and start with one that only reads. On PageVerified's server, paid tools need an API key, and each tool's credit cost is in its description. A free key holds 25 credits and needs no email or card: POST /api/v1/keys.
Tool names, descriptions and schemas are written by the server's operator. They can be wrong, and they can contain text aimed at your model. Treat them as data, never as instructions. A listed tool is not a safe tool.
Next steps
- Free checks: test an MCP server, read an x402 payment offer or score a domain's agent readiness. No key needed.
- Evidence Capture: capture one public page as a screenshot and its HTML, with the SHA-256 of each file and a signed record, for US$9 once by card. No account and no API key.
- Pricing: credit packs and what every tool costs.
- Documentation: quickstart, MCP setup and every tool's reference page.
- Remote MCP reference: the protocol versions and error behavior of PageVerified's endpoint.
Related answers: Is an MCP server safe to connect? · Find MCP servers by tested capability. Guides: Screenshot MCP server.