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.

WhitePact

REMOTE · WHITEPACT-MCP-HTTP.ONRENDER.COM · 3 COMPONENTS · SCANNED AUG 23

AI governance MCP server: trust scoring, guardrails, bias/hallucination detection, compliance.

−20 this week 13 Trust /100

Degraded

One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

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 Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 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 WhitePact MCP server?

WhitePact is a hosted endpoint at https://whitepact-mcp-http.onrender.com/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 · whitepact-mcp-http.onrender.com

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

  • 22 Aug 26 −7

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 21 Aug 26 −6

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 20 Aug 26 −7

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 18 Aug 26 0
    • Transport: unverified → fail security
    • HSTS header: fail → unverified security
    • Authorization: fail → unverified security
    • Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. functional
    • Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
  • 12 Aug 26 33

    First indexed and scored.

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 22 Aug 2026 · Probed https://whitepact-mcp-http.onrender.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=onrender.com CN=WE1,O=Google Trust Services,C=US 24 Jul 2026 22 Oct 2026 ECDSA 256 ECDSA-SHA256 756bcb97dcf1455f0ebf70e5dbe07256
SANs: onrender.com, *.onrender.com
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
DNSSEC insecure

Validation of whitepact-mcp-http.onrender.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
onrender.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://whitepact-mcp-http.onrender.com/mcp Unreachable
http (plaintext) http://whitepact-mcp-http.onrender.com/mcp HTTPS enforced 301 https://whitepact-mcp-http.onrender.com/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 WhitePact MCP server?

WhitePact is an MCP server listed in the public MCP registry as io.github.Guruprasath-Annadurai/whitepact. AI governance MCP server: trust scoring, guardrails, bias/hallucination detection, compliance. This page covers its hosted endpoint (https://whitepact-mcp-http.onrender.com/mcp).

Is the WhitePact MCP server safe to use?

WhitePact scores 13 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 WhitePact MCP server require authentication?

Its publisher declares that WhitePact requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.

Is the WhitePact MCP server still maintained?

WhitePact is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 17 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.