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.

in.mednode/mednode

REMOTE · MCP.MEDNODE.IN · SCANNED AUG 23

Your MedNode health vault in your AI assistant — records, summaries, labs, appointments.

Available components

remote · mcp.mednode.in 36
+13 this week 36 Trust /100
Trust breakdown (6 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 →

Endpoint Security89
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the in.mednode/mednode MCP server?

in.mednode/mednode is a hosted endpoint at https://mcp.mednode.in/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 · mcp.mednode.in

# add to Claude Code
claude mcp add --transport http in-mednode-mednode 'https://mcp.mednode.in/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "in-mednode-mednode": {
      "url": "https://mcp.mednode.in/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "in-mednode-mednode": {
      "type": "http",
      "url": "https://mcp.mednode.in/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.in-mednode-mednode]
url = "https://mcp.mednode.in/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "in-mednode-mednode": {
      "type": "remote",
      "url": "https://mcp.mednode.in/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add in-mednode-mednode --url 'https://mcp.mednode.in/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  in-mednode-mednode:
    url: "https://mcp.mednode.in/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "in-mednode-mednode": {
      "Transport": "http",
      "Url": "https://mcp.mednode.in/mcp"
    }
  }
}
# add to Vellum
assistant mcp add in-mednode-mednode -t streamable-http -u 'https://mcp.mednode.in/mcp'
// mcp.json
{
  "mcpServers": {
    "in-mednode-mednode": {
      "type": "http",
      "url": "https://mcp.mednode.in/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.

  • 23 Aug 26 +13
    • HSTS header: unverified → fail ▼ security
    • Authorization: unverified → pass ▲ security
  • 22 Aug 26 −13
    • HSTS header: fail → unverified ▼ security
    • Authorization: pass → unverified ▼ security
  • 21 Aug 26 +13
    • HSTS header: unverified → fail ▼ security
    • Authorization: unverified → pass ▲ security
  • 20 Aug 26 −13
    • HSTS header: fail → unverified ▼ security
    • Authorization: pass → unverified ▼ security
  • 19 Aug 26 +13
    • HSTS header: unverified → fail ▼ security
    • Authorization: unverified → pass ▲ security
  • 18 Aug 26 −13
    • HSTS header: fail → unverified ▼ security
    • Authorization: pass → unverified ▼ security
  • 17 Aug 26 +13
    • HSTS header: unverified → fail ▼ security
    • Authorization: unverified → pass ▲ security
  • 16 Aug 26 −13
    • HSTS header: fail → unverified ▼ security
    • Authorization: pass → unverified ▼ security
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 23 Aug 2026 · Probed https://mcp.mednode.in/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.mednode.in CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US 13 Aug 2026 13 Feb 2027 RSA 2048 SHA256-RSA 670b715d3b246588373e6272b197188
SANs: mcp.mednode.in
CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 2 Nov 2017 2 Nov 2027 RSA 2048 SHA256-RSA d07782a133fc6f9a57296e131ffd179
CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 1 Aug 2013 15 Jan 2038 RSA 2048 SHA256-RSA 33af1e6a711a9a0bb2864b11d09fae5
DNSSEC insecure

Validation of mcp.mednode.in. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
in. present 10094 13 Verified
mednode.in. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer realm="mednode", resource_metadata="https://mcp.mednode.in/.well-known/oauth-protected-resource" 

Bearer realm="mednode", resource_metadata="https://mcp.mednode.in/.well-known/oauth-protected-resource"
Header Value
www-authenticate Bearer realm="mednode", resource_metadata="https://mcp.mednode.in/.well-known/oauth-protected-resource"

Protected resource metadata

Document https://mcp.mednode.in/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.mednode.in/mcp
Authorisation server https://mcp.mednode.in
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.mednode.in/mcp Auth required 401
http (plaintext) http://mcp.mednode.in/mcp HTTPS enforced 301 https://mcp.mednode.in/mcp
MCP tools

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.

No tool schema has been captured from this endpoint yet.

Common questions

What is the in.mednode/mednode MCP server?

in.mednode/mednode is an MCP server listed in the public MCP registry as in.mednode/mednode. Your MedNode health vault in your AI assistant, records, summaries, labs, appointments. This page covers its hosted endpoint (https://mcp.mednode.in/mcp).

Is the in.mednode/mednode MCP server safe to use?

in.mednode/mednode scores 36 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.

Does the in.mednode/mednode MCP server require authentication?

Yes. in.mednode/mednode asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the in.mednode/mednode MCP server still maintained?

in.mednode/mednode is still listed as active in the MCP registry. We last reached this channel on 23 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.