Skip to content

Wheeler Hubbell Publishing Standing Mark MCP server

io.github.wheelerhubbell/whp-standingwheelerhubbellstreamable-httpv1.2.0Scanned

Independent examination of claims and agent actions. 1.00 USDC on Base, not x402. Source-install.

8 tools: 1 do something that can't be undone, 4 change things and 3 only read.

Tools: 0 delete, 1 irreversible, 4 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • 1 finding

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Wheeler Hubbell Publishing Standing Mark MCP server can do

The Wheeler Hubbell Publishing Standing Mark MCP server is published by the GitHub account wheelerhubbell. It has 8 tools. It can do things that cannot be undone, such as sending, paying or publishing (whp_recover_purchase) and create or change data (4 tools: whp_evaluate, whp_authorize_x402_transaction, evaluate_decision and verify_standing_mark), but cannot delete data. 3 tools only read.

3 tools bring in text other people can write (evaluate_decision, retrieve_standing_mark and verify_standing_mark).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 11, 2026, version 1.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Can't be undone 1Claude Code: ask
  • whp_recover_purchaseRecover the original signed Standing Mark Record for a settled purchase_id or submission_hash without triggering a second payment charge.No findings

    Why it is in this group

    • The name "whp_recover_purchase" says "purchase": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Recover the original signed Standing Mark Record for a settled purchase_id or submission_hash without triggering a second payment charge.
Changes things 4Claude Code: ask
  • evaluate_decisionSubmit material for a paid Decision Integrity evaluation through the single door (POST /v1/evaluate).Reads text others writeNo findings

    Why it is in this group

    • The name "evaluate_decision" says "evaluate": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Submit material for a paid Decision Integrity evaluation through the single door (POST /v1/evaluate). Returns the exact x402 payment terms when no payment is attached; a payment signature is accepted only as the caller's own explicit, pre-authorized payment and is never created by this server. Payment buys the examination, never a favorable outcome.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • verify_standing_markIndependently verify an existing Standing Mark: Ed25519 signature over WHP-JCS-I1, recognized-issuer check, mark_id-to-record consistency, record completeness, governing Decision I…Reads text others write1 finding

    Why it is in this group

    • The name "verify_standing_mark" says "mark": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "verify_standing_mark" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "verify_standing_mark" says "mark": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Independently verify an existing Standing Mark: Ed25519 signature over WHP-JCS-I1, recognized-issuer check, mark_id-to-record consistency, record completeness, governing Decision Integrity version, and the claims the record cannot establish. Verification is free and never triggers an evaluation or payment. Verification does not prove the underlying proposition true and does not authorize any action.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • whp_authorize_x402_transactionPre-settlement Standing Mark Service guard for autonomous agent-to-agent x402 transactions.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Pre-settlement Standing Mark Service guard for autonomous agent-to-agent x402 transactions. Examines the proposed transaction through /v1/evaluate, mechanically verifies object binding and Ed25519 signature, and satisfies the pre-settlement evidence requirement only when finding_disposition === 'POSITIVE_STANDING_MARK' and 'EXECUTE' is in permitted_operations.
  • whp_evaluateWHP Standing Mark Service (POST /v1/evaluate): Submit material through the single evaluation door.No findings

    Why it is in this group

    • The name "whp_evaluate" says "evaluate": a word for a change.
    Description, as the server wrote it
    WHP Standing Mark Service (POST /v1/evaluate): Submit material through the single evaluation door. A sovereign Large Language Model given Decision Integrity Version 7 (The Continuous Work) examines whether the submitted record warrants the requested operation within stated scope and emits an object-bound, Ed25519-signed Standing Mark Record (POSITIVE_STANDING_MARK when established; NEGATIVE_STANDING_FINDING when not established). Payment buys the examination, never a favorable outcome.
Only reads 3Show 3 read-only tools
  • retrieve_standing_markRetrieve an issued Standing Mark record by mark_id, purchase_id, payment nonce, or idempotency key.Reads text others writeNo findings

    Why it is in this group

    • The name "retrieve_standing_mark" says "retrieve": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Retrieve an issued Standing Mark record by mark_id, purchase_id, payment nonce, or idempotency key. Zero charge; read-only; never triggers an evaluation or payment.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • whp_get_contractInspect the live WHP Standing Mark Service wire contract, data-handling disclosures, payment terms, and Developer Integration Rule without payment.No findings

    Why it is in this group

    • The name "whp_get_contract" says "get": a word for reading.
    Description, as the server wrote it
    Inspect the live WHP Standing Mark Service wire contract, data-handling disclosures, payment terms, and Developer Integration Rule without payment.
  • whp_retrieve_resultRetrieve a previously issued Standing Mark Record by purchase_id without triggering a second x402 payment charge.No findings

    Why it is in this group

    • The name "whp_retrieve_result" says "retrieve": a word for reading.
    Description, as the server wrote it
    Retrieve a previously issued Standing Mark Record by purchase_id without triggering a second x402 payment charge.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 13, 2026, 12:20 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
404
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 404.

Posture changes

  1. Nov 13, 2026
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
  2. Nov 6, 2026
    • HTTP status of an anonymous initialize: 404 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2025-06-18

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "verify_standing_mark" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "verify_standing_mark" says "mark": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 3 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
  2. Tools7 added, 3 removed, 1 changed.+7 added−3 removed~1 changedView diff
  3. PostureRemote posture changed. HTTP status of an anonymous initialize: 404 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 3 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 404 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2025-06-18

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__whp-standing__whp_retrieve_result",
      "mcp__whp-standing__retrieve_standing_mark",
      "mcp__whp-standing__whp_get_contract"
    ],
    "ask": [
      "mcp__whp-standing__whp_evaluate",
      "mcp__whp-standing__whp_authorize_x402_transaction",
      "mcp__whp-standing__whp_recover_purchase",
      "mcp__whp-standing__evaluate_decision",
      "mcp__whp-standing__verify_standing_mark"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as whp-standing. Review it before you use it.

Capability tags behind 3 rules
  • mcp__whp-standing__evaluate_decision untrusted-input
  • mcp__whp-standing__retrieve_standing_mark untrusted-input
  • mcp__whp-standing__verify_standing_mark untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.wheelerhubbell/whp-standing/verify?hash=ece27b4cd737efcee2215433bf5304e988fa986035f01bd47e0b55342a733798" | jq -e '.changed == false'

Pinned hash ece27b4cd737, from Nov 11, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.wheelerhubbell/whp-standing/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.wheelerhubbell/whp-standing
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.wheelerhubbell/whp-standing.svg)](https://radar.anlyon.com/servers/io.github.wheelerhubbell/whp-standing)

Source: MCP Registry · repository. Synced Nov 13, 2026, 18:18 UTC.

Wheeler Hubbell Publishing Standing Mark MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Wheeler Hubbell Publishing Standing Mark MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Wheeler Hubbell Publishing Standing Mark MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Wheeler Hubbell Publishing Standing Mark MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: whp_recover_purchase.

What tools does the Wheeler Hubbell Publishing Standing Mark MCP server have?

8 tools: 1 irreversible, 4 write, 3 read. whp_recover_purchase, whp_evaluate, whp_authorize_x402_transaction, evaluate_decision, verify_standing_mark, whp_retrieve_result, retrieve_standing_mark and whp_get_contract.

Does the Wheeler Hubbell Publishing Standing Mark MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Wheeler Hubbell Publishing Standing Mark MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Wheeler Hubbell Publishing Standing Mark MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.