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 · API.WHEELERHUBBELLPUBLISHING.COM

Paid, signed evaluations of structured claims and supporting sources. MCP; x402 on Base.

58 Trust /100

Last scanned (23 hours ago)

Scores higher than 43% of remote servers

Reachable. Last reached 4 Nov 2026.

Category AI and Machine Learning

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 Usability37
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 433 tokens (~61/item across 7 items; 4 tools + 3 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 55% 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 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
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.

  • 3 Nov 26 +1

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

  • 1 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 31 Oct 26 56

    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 4 Nov 2026 · Probed https://api.wheelerhubbellpublishing.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.wheelerhubbellpublishing.com CN=YE2,O=Let's Encrypt,C=US 16 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA384 5b61db55357884ebcc97635c91540d1c70e
SANs: api.wheelerhubbellpublishing.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 api.wheelerhubbellpublishing.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
wheelerhubbellpublishing.com. 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://api.wheelerhubbellpublishing.com/mcp Verified 200
http (plaintext) http://api.wheelerhubbellpublishing.com/mcp HTTPS enforced 301 https://api.wheelerhubbellpublishing.com/mcp
MCP tools · 4 exposed · ~384 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_evaluate ~213

Evaluate a proposition under Decision Integrity Protocol and receive an Ed25519-signed Standing determination. Calling without payment returns the exact 1 USDC Base payment challenge. Pass payment_signature to settle and receive the signed determination.

NameTypeReqDescription
api_keystring–Optional WHP subscription API key (Developer, Team, or Institutional tier) bypassing x402 challenge.
claimstringyesThe claim or proposition to evaluate (also accepts aliases: text, prompt, content).
idempotency_keystring–Optional idempotency key for safe execution recovery.
payment_signaturestring–Base64 or JSON x402 v2 payment authorization for 1 USDC on Base (network eip155:8453 to 0x1050eddd8282623b0c263ed6bdbd42370bbc28d3).
provenanceobject–Optional provenance graph or supporting evidence.
subjectstring–Optional subject/context of the proposition (defaults to claim summary).

No output schema declared.

No examples provided.

whp_standing_contract ~41

Discover WHP Standing: Machine-verifiable standing under explicit authority and bounds. Includes exact profile, schema, authority prerequisites and owner-authorized payment contract.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

whp_standing_evaluation ~82

Request a WHP Standing Evaluation. First call returns the exact HTTP 402 payment terms. Supply only the buyer’s own pre-authorized payment signature on retry. Paying does not establish standing; a failed assessment has no Mark.

NameTypeReqDescription
client_proofstring––
payment_signaturestring––
submission_rawstringyes–

No output schema declared.

No examples provided.

whp_standing_result ~48

Retrieve the exact original WHP Standing Mark or negative assessment bytes with buyer authentication, without another charge.

NameTypeReqDescription
client_proofstringyes–
purchase_idstringyes–

No output schema declared.

No examples provided.

Install

How do I install the WHP Standing MCP server?

WHP Standing is a hosted endpoint at https://api.wheelerhubbellpublishing.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 · api.wheelerhubbellpublishing.com

# add to Claude Code
claude mcp add --transport http wheelerhubbell-whp-standing 'https://api.wheelerhubbellpublishing.com/mcp'
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. Paid, signed evaluations of structured claims and supporting sources. MCP; x402 on Base. This page covers its hosted endpoint (https://api.wheelerhubbellpublishing.com/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_evaluate, whp_standing_contract, whp_standing_evaluation, whp_standing_result. Their descriptions and schemas cost roughly 384 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.