---
title: Sudhanva MCP server
description: Connection, lifecycle, tools, resources, and transport details for the public sudhanva.me Model Context Protocol servers.
canonical: https://sudhanva.me/developers/mcp/
last-updated: 2026-10-01
---

# Sudhanva MCP server

Connect to `https://sudhanva.me/mcp` with MCP Streamable HTTP. The endpoint is
stateless and accepts individual JSON-RPC 2.0 messages with HTTP POST.

The current `2026-07-28` revision uses per-request metadata and
`server/discover`; it does not use an initialization handshake. The server also
supports handshake-based revisions `2025-11-25`, `2025-06-18`,
`2025-03-26`, and `2024-11-05`. The server does not offer a standalone GET
stream, so GET returns HTTP 405.

Origins: The server accepts requests with no `Origin` header, any `https://`
origin, and `http://localhost`, `http://127.0.0.1`, or `http://[::1]` on any
port. Any other origin, including plain `http://` hosts and `null`, gets
HTTP 403. The server echoes an accepted origin in `Access-Control-Allow-Origin`
with `Vary: Origin`.

Errors: For the 2024 and 2025 revisions, an unknown method, tool, or resource
returns HTTP 200 with a JSON-RPC error. With `2026-07-28`, it returns HTTP 400
with the JSON-RPC error. Invalid JSON, an invalid JSON-RPC message, a null `id`,
and an unsupported `MCP-Protocol-Version` header return 400. The server checks
tool arguments against each tool's `inputSchema`. From `2025-11-25` on, invalid
arguments return a tool result with `isError: true`. Older revisions return
`-32602`. `ping` works in every revision.

Read-only tools:

- `get_public_profile`
- `list_published_articles`
- `list_case_studies`

Pass `slug` to `list_published_articles` for an exact lookup. The server also
answers `get_published_article` calls with a `slug`, although that name is not
listed in `tools/list`.

All three read-only tools set `_meta.ui.resourceUri` to the interactive
`ui://sudhanva/profile-explorer` MCP App resource. Read the resource with
`resources/read`. It returns `text/html;profile=mcp-app`. The view uses the
official `@modelcontextprotocol/ext-apps` client. Hosts without MCP Apps support
still get the text and `structuredContent` fallbacks.

The action tools are at a separate endpoint, `https://sudhanva.me/mcp/product`:

- `get_profile_insight_capabilities`
- `create_profile_insight`
- `get_profile_insight`

- [Server card](https://sudhanva.me/.well-known/mcp/server-card.json)
- [Official MCP Registry entry](https://registry.modelcontextprotocol.io/v0.1/servers/me.sudhanva%2Fpublic-profile/versions/1.4.2)
- [Smithery listing](https://smithery.ai/servers/nsudhanva/public-profile)
- [Product MCP server card](https://sudhanva.me/.well-known/mcp/product-server-card.json)
- [ARD catalog](https://sudhanva.me/.well-known/ard.json)
- [AI catalog](https://sudhanva.me/.well-known/ai-catalog.json)
- [Developer documentation](https://sudhanva.me/docs/)