Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Sudhanva Public Profile

REMOTE · SUDHANVA.ME · SCANNED SEP 21

Read Sudhanva Narayana's public profile, production ML case studies, and technical writing.

Available components

+3 this week 86 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security77
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 217 tokens (~36/item across 6 items; 3 tools + 3 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 60% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
Install

How do I install the Sudhanva Public Profile MCP server?

Sudhanva Public Profile is a hosted endpoint at https://sudhanva.me/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · sudhanva.me

# add to Claude Code
claude mcp add --transport http nsudhanva-sudhanva-public-profile 'https://sudhanva.me/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "nsudhanva-sudhanva-public-profile": {
      "url": "https://sudhanva.me/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "nsudhanva-sudhanva-public-profile": {
      "type": "http",
      "url": "https://sudhanva.me/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.nsudhanva-sudhanva-public-profile]
url = "https://sudhanva.me/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nsudhanva-sudhanva-public-profile": {
      "type": "remote",
      "url": "https://sudhanva.me/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nsudhanva-sudhanva-public-profile --url 'https://sudhanva.me/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  nsudhanva-sudhanva-public-profile:
    url: "https://sudhanva.me/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "nsudhanva-sudhanva-public-profile": {
      "Transport": "http",
      "Url": "https://sudhanva.me/mcp"
    }
  }
}
# add to Vellum
assistant mcp add nsudhanva-sudhanva-public-profile -t streamable-http -u 'https://sudhanva.me/mcp'
// mcp.json
{
  "mcpServers": {
    "nsudhanva-sudhanva-public-profile": {
      "type": "http",
      "url": "https://sudhanva.me/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Probed https://sudhanva.me/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=sudhanva.me CN=WE1,O=Google Trust Services,C=US 22 Aug 2026 20 Nov 2026 ECDSA 256 ECDSA-SHA256 df933872705f08500e625c2f04336eda
SANs: sudhanva.me, nvidia.sudhanva.me, *.nvidia.sudhanva.me
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of sudhanva.me. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
me. present 45352 8 Verified
sudhanva.me. present 2371 13 Verified
sudhanva.me. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://sudhanva.me/mcp Verified 200
http (plaintext) http://sudhanva.me/mcp HTTPS enforced 301 https://sudhanva.me/mcp
MCP tools · 3 exposed · ~130 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_public_profile ~40

Get Sudhanva Narayana's published professional profile and expertise.

NameTypeReqDescription
include_linksbooleanInclude canonical profile and social links. Defaults to true.

No output schema declared.

No examples provided.

list_case_studies ~37

List published production ML case studies and verified outcomes.

NameTypeReqDescription
limitintegerMaximum case studies to return. Defaults to all five.

No output schema declared.

No examples provided.

list_published_articles ~53

List published technical writing by tag or retrieve one article by canonical slug.

NameTypeReqDescription
limitinteger
slugstringReturn one exact article instead of a list.
tagstring

No output schema declared.

No examples provided.

Common questions

What is the Sudhanva Public Profile MCP server?

Sudhanva Public Profile is an MCP server listed in the public MCP registry as io.github.nsudhanva/sudhanva-public-profile. Read Sudhanva Narayana's public profile, production ML case studies, and technical writing. This page covers its hosted endpoint (https://sudhanva.me/mcp).

Is the Sudhanva Public Profile MCP server safe to use?

Sudhanva Public Profile scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Sudhanva Public Profile MCP server expose?

Sudhanva Public Profile exposes 3 tools: get_public_profile, list_published_articles, list_case_studies. Their descriptions and schemas cost roughly 130 tokens of context every time the server is loaded.

Does the Sudhanva Public Profile MCP server require authentication?

No. We connected to Sudhanva Public Profile without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Sudhanva Public Profile MCP server still maintained?

Sudhanva Public Profile is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.