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.

WHP Standing

REMOTE · WHP-STANDING-LIVE-PRODUCTION.UP.RAILWAY.APP · SCANNED SEP 25

Verify signed JSON provenance through bounded COPY/COMPOSE. Payment never guarantees a Mark.

58 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 Security57
Transport & Reachability100
Schema Quality & AI Usability43
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 411 tokens (~41/item across 10 items; 4 tools + 6 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 20% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the WHP Standing MCP server?

WHP Standing is a hosted endpoint at https://whp-standing-live-production.up.railway.app/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 · whp-standing-live-production.up.railway.app

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

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 23 Sept 26 57

    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 25 Sept 2026 · Probed https://whp-standing-live-production.up.railway.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.up.railway.app CN=YE1,O=Let's Encrypt,C=US 29 Jul 2026 27 Oct 2026 ECDSA 256 ECDSA-SHA384 6da79bb561da3efeb0e751ca21abd3999fe
SANs: *.up.railway.app, up.railway.app
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of whp-standing-live-production.up.railway.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
railway.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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
Header Value
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://whp-standing-live-production.up.railway.app/mcp Verified 200
http (plaintext) http://whp-standing-live-production.up.railway.app/mcp HTTPS enforced 301 https://whp-standing-live-production.up.railway.app/mcp
MCP tools · 4 exposed · ~291 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
whp_standing_contract ~68

Discover WHP Standing: Verify whether signed JSON provenance preserves identity, authority, scope, jurisdiction, time, and operation through exact COPY or identity-preserving COMPOSE. Includes exact profile, schema, authority prerequisites, fresh probe URL, and 1 USDC Base x402 payment contract.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

whp_standing_evaluation ~110

Purchase one evaluation for 1 native USDC on Base mainnet (eip155:8453). Fetch a fresh submission example from /examples/submission.PROBE.json, submit it unchanged, read the x402 402 requirements, then replay with payment. Payment never guarantees a Mark.

NameTypeReqDescription
payerstring––
submission_rawstringyesExact UTF-8 JSON bytes. Fresh example: /examples/submission.PROBE.json
wallet_signaturestring––
NameTypeReqDescription
body_bytesstringyes–
headersobject––
http_statusintegeryes–

No examples provided.

whp_standing_recover ~68

Progress an already authorized pending purchase using its original durable payment. Supply only the purchase ID. Never sign another payment; if result retrieval says QUOTED, replay the original submission and identical saved wallet signature through whp_standing_evaluation.

NameTypeReqDescription
purchase_idstringyes–
NameTypeReqDescription
body_bytesstringyes–
headersobject––
http_statusintegeryes–

No examples provided.

whp_standing_result ~45

Retrieve the exact original WHP Standing Mark or negative assessment bytes by durable purchase ID, without another charge or WHP-specific signature.

NameTypeReqDescription
purchase_idstringyes–
NameTypeReqDescription
body_bytesstringyes–
headersobject––
http_statusintegeryes–

No examples provided.

Common questions

What is the WHP Standing MCP server?

WHP Standing is an MCP server listed in the public MCP registry as io.github.wheelerhubbell/whp-standing. Verify signed JSON provenance through bounded COPY/COMPOSE. Payment never guarantees a Mark. This page covers its hosted endpoint (https://whp-standing-live-production.up.railway.app/mcp).

Is the WHP Standing MCP server safe to use?

WHP Standing scores 58 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 WHP Standing MCP server expose?

WHP Standing exposes 4 tools: whp_standing_contract, whp_standing_evaluation, whp_standing_result, whp_standing_recover. Their descriptions and schemas cost roughly 291 tokens of context every time the server is loaded.

Does the WHP Standing MCP server require authentication?

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

Is the WHP Standing MCP server still maintained?

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