WHP Standing
REMOTE · STANDING-GUARD-SERVICE.LOVABLE.APP · SCANNED OCT 6
WHP Standing x402 on Base: evaluate, patch, ept/core 1 USDC; audit 2; priority 5; ping 0.10
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability35
- 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 220 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the WHP Standing MCP server?
WHP Standing is a hosted endpoint at https://standing-guard-service.lovable.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 · standing-guard-service.lovable.app
claude mcp add --transport http wheelerhubbell-whp-standing 'https://standing-guard-service.lovable.app/mcp'
{
"mcpServers": {
"wheelerhubbell-whp-standing": {
"url": "https://standing-guard-service.lovable.app/mcp"
}
}
} {
"servers": {
"wheelerhubbell-whp-standing": {
"type": "http",
"url": "https://standing-guard-service.lovable.app/mcp"
}
}
} [mcp_servers.wheelerhubbell-whp-standing] url = "https://standing-guard-service.lovable.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wheelerhubbell-whp-standing": {
"type": "remote",
"url": "https://standing-guard-service.lovable.app/mcp",
"enabled": true
}
}
} openclaw mcp add wheelerhubbell-whp-standing --url 'https://standing-guard-service.lovable.app/mcp' --transport streamable-http
mcp_servers:
wheelerhubbell-whp-standing:
url: "https://standing-guard-service.lovable.app/mcp" {
"McpServers": {
"wheelerhubbell-whp-standing": {
"Transport": "http",
"Url": "https://standing-guard-service.lovable.app/mcp"
}
}
} assistant mcp add wheelerhubbell-whp-standing -t streamable-http -u 'https://standing-guard-service.lovable.app/mcp'
{
"mcpServers": {
"wheelerhubbell-whp-standing": {
"type": "http",
"url": "https://standing-guard-service.lovable.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 6 Oct 26 64
First indexed and scored.
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 9 Oct 2026 · Probed https://standing-guard-service.lovable.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lovable.app | CN=WE1,O=Google Trust Services,C=US | 12 Aug 2026 | 10 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | bcdd7f0c8d0d96cc1341c264df25fbd6 |
| SANs: lovable.app, *.lovable.app | ||||||
| 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 insecure
Validation of standing-guard-service.lovable.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| lovable.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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://standing-guard-service.lovable.app/mcp | Verified | 200 | |
| http (plaintext) | http://standing-guard-service.lovable.app/mcp | HTTPS enforced | 301 | https://standing-guard-service.lovable.app/mcp |
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_proof | string | yes | – |
| payment_signature | string | – | – |
| submission_raw | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_proof | string | yes | – |
| purchase_id | string | yes | – |
No output schema declared.
No examples provided.
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. WHP Standing x402 on Base: evaluate, patch, ept/core 1 USDC; audit 2; priority 5; ping 0.10. This page covers its hosted endpoint (https://standing-guard-service.lovable.app/mcp).
Is the WHP Standing MCP server safe to use?
WHP Standing scores 64 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 3 tools: whp_standing_contract, whp_standing_evaluation, whp_standing_result. Their descriptions and schemas cost roughly 171 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 6 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.