Kaspa Explained MCP

This Cloudflare Worker exposes a public, read-only MCP endpoint for Kaspa Explained.

Agent Access

Agents and MCP clients should use this remote HTTP MCP URL:

https://remote-mcp-server-authless.parker2017.workers.dev/mcp

Check health here:

https://remote-mcp-server-authless.parker2017.workers.dev/health

Discovery card:

https://remote-mcp-server-authless.parker2017.workers.dev/.well-known/mcp.json

Do not use https://mcp.kaspaexplained.com/mcp; the custom domain is not part of the current setup.

Public endpoint:

https://remote-mcp-server-authless.parker2017.workers.dev/mcp

Health check:

https://remote-mcp-server-authless.parker2017.workers.dev/
https://remote-mcp-server-authless.parker2017.workers.dev/health

Discovery aliases:

https://remote-mcp-server-authless.parker2017.workers.dev/.well-known/mcp.json
https://remote-mcp-server-authless.parker2017.workers.dev/.well-known/mcp-server-card
https://remote-mcp-server-authless.parker2017.workers.dev/.well-known/mcp/server-card.json

What It Does

The Worker fetches the public Kaspa Explained agent index:

https://kaspaexplained.com/agent-index.json

It then exposes MCP tools for agents:

• get_kaspa_explained_index - return index metadata, scope, and guidance.
• search_kaspa_explained - search public Kaspa Explained pages and reference files.
• read_kaspa_explained - read one public page or reference file by path or URL.
• check_kaspa_claim - retrieve claim-checking context and cited passages.
• get_kaspa_status_context - return compact status context for Toccata, smart contracts, and claims.

Design

This server is deliberately simple and cheap:

• No embeddings.
• No vector database.
• No server-side LLM answering.
• No wallet, account, private-data, or write tools.

The calling AI agent supplies the model. This MCP server only retrieves public, source-labeled Kaspa Explained content and reminds agents to keep mainnet, ecosystem-live, testnet, targeted, roadmap, research, and unsupported claims separate.

Auth is not required while the tools are public and read-only. Add authentication before exposing private sources or write-capable tools.

Client Examples

Use the remote HTTP endpoint in MCP clients that support hosted MCP servers:

{
	"mcpServers": {
		"kaspa-explained": {
			"type": "http",
			"url": "https://remote-mcp-server-authless.parker2017.workers.dev/mcp"
		}
	}
}

Example files are in examples/:

• examples/mcp-servers.remote-http.json
• examples/servers.remote-http.json

After deployment, verify the access point before adding it to clients:

curl https://remote-mcp-server-authless.parker2017.workers.dev/health

The response should include status: "ok" and list the available tool names.

If a browser or plain GET request to /mcp returns Not Acceptable: Client must accept text/event-stream, the Worker is reachable. MCP clients must connect using the remote HTTP MCP protocol and include Accept: application/json, text/event-stream.

The .well-known discovery URLs are public JSON documents for agents and registries. They advertise where to connect, but clients should still call MCP initialize and runtime list methods such as tools/list after connecting.

Development

Install dependencies:

npm install

Run locally:

npm run dev

Type-check:

npm run type-check

Deploy:

npm run deploy

If deploying from a non-interactive environment, set CLOUDFLARE_API_TOKEN first.