For developers
What a client needs to know about the server, and how to call it without an assistant in between.
The protocol as we serve it
-
Streamable HTTP at
https://api.publicwww.com/mcp: one JSON-RPC message perPOST(a batch is accepted too), answers are plainapplication/json. No server-sent events, no sessions - every request carries its token.GETis405. -
Both generations of the protocol are served at the same URL: the
revisions with the
initializehandshake (2024-11-05 to 2025-11-25) and 2026-07-28 withserver/discover, where the version and client capabilities travel inparams._metaof every request andMcp-Method/Mcp-Namemust match the body. -
Without a token,
initialize,server/discover,ping,tools/list, resources and theread_docstool work. Any other call, a body that is not JSON or a token that was deleted is401, with aWWW-Authenticateheader naming the protected resource metadata (RFC 9728), from which an OAuth client finds the authorization server. The message says whether the token is missing or not valid, anderror.datalinks to the instructions. The flow is in OAuth 2.1 for applications. -
Tools:
search,account,read_docsand eight for clusters, described in Tools. Resources: this documentation and the price list in Markdown -publicwww://docsandpublicwww://docs/<page>, optionally with?lang=. No prompts, and the lists do not change between calls. -
Without a token, the
server card
describes the server: name, address, protocol versions and links. It is
listed in
https://publicwww.com/.well-known/ai-catalog.json. The tool list is not part of the card; it comes fromtools/list. -
Outside MCP, every page of this documentation is also Markdown at its
address plus
index.md(/docs/api/limits/index.md) or at the address itself withAccept: text/markdown, the prices at/prices.md, everything in one file at/llms-full.txt, and the map at/llms.txt.
Calling it with curl
The server keeps no state between calls, so a tool can be called straight away, without the handshake:
curl https://api.publicwww.com/mcp \
-H "Authorization: Bearer $PUBLICWWW_TOKEN" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"search","arguments":{"query":"\"angular.min.js\"","rows":3}}}'
With the same headers, -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
lists the tools with their input schemas. These calls and an account check, as one
script: mcp-curl.sh.
For a script that only needs search results, the REST API is the simpler road: the same search and token, with CSV, NDJSON and the other formats.
Next Technologies