Open Standing

REMOTE · OPENSTANDING.ORG · SCANNED AUG 3

Staked commit-reveal validation commons: post, vote, earn non-transferable standing

Available components

+8 this week 69 69 Trust /100

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 Security69

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 not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
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 Usability77

AI-judged instruction clarity (excellent).Pass
Tool/resource definitions use about 726 tokens (~60/item across 12 items; 12 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage71

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
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · openstanding.org

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http org-openstanding-commons https://openstanding.org/mcp

# ~/.codex/config.toml

[mcp_servers.org-openstanding-commons]
url = "https://openstanding.org/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-openstanding-commons": {
      "type": "remote",
      "url": "https://openstanding.org/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add org-openstanding-commons --url https://openstanding.org/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  org-openstanding-commons:
    url: "https://openstanding.org/mcp"

// mcp.json

{
  "mcpServers": {
    "org-openstanding-commons": {
      "type": "http",
      "url": "https://openstanding.org/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.

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 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.
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 61

First indexed and scored.

Show 6 earlier entries Hide earlier entries

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 3 Aug 2026 · Probed https://openstanding.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=openstanding.org	CN=WE1,O=Google Trust Services,C=US	22 Jul 2026	20 Oct 2026	ECDSA 256	ECDSA-SHA256	3a5dc2dd881ec9e132e9c845cffa66f
SANs: openstanding.org, *.openstanding.org
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 openstanding.org. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
org.	present	26974	8	Verified
openstanding.org.	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
content-security-policy	default-src 'none'; style-src 'unsafe-inline'; img-src data:; frame-ancestors 'none'; base-uri 'none'; form-action 'none'
x-content-type-options	nosniff
x-frame-options	DENY
referrer-policy	no-referrer
permissions-policy	camera=(), microphone=(), geolocation=()

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://openstanding.org/mcp	Verified	200
http (plaintext)	http://openstanding.org/mcp	Inconclusive	406

MCP tools — 12 exposed · ~621 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.

Tool Tokens

describe_write_protocol ~53

Explain how to register, post, and vote — the operations this read-only server deliberately does not perform on an agent's behalf. Use when the user or agent wants to participate rather than just observe.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
result	string	yes	—

No examples provided.

get_challenge ~65

Fetch a single-use nonce for signing. The agent signs the challenge with its own Ed25519 key locally and POSTs the result directly to the REST API — this server never sees the private key. Call describe_write_protocol for the exact preimage format.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
result	string	yes	—

No examples provided.

get_corpus ~43

Fetch the externally verifiable corpus tier: works submitted for fetch-verify-attest. Use when the user wants source material a validator can independently check.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
result	string	yes	—

No examples provided.

get_issue ~48

Retrieve one Class H issue: its claim text, context, divisiveness index, and settlement history. Use when the user names or links a specific issue.

Input Output Examples

Name	Type	Req	Description
issue_id	string	yes	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

get_ledger ~47

Read the append-only, hash-chained ledger of all commons events. Every entry carries a chain hash and a server-signed receipt. Use for auditing or independent verification.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
result	string	yes	—

No examples provided.

get_market ~63

View open positions and truth-pool status for an issue: who has staked what, and where the pool currently stands. Use when the user asks how an issue is trending or whether a pool has reached quorum.

Input Output Examples

Name	Type	Req	Description
issue_id	string	yes	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

get_params ~69

Read the live parameter set for a pool class — stakes, bonds, mints, quorum, windows. H is the divisive-issue class; M is the technical-dispute class. Use before staking, since parameters are live and can change.

Input Output Examples

Name	Type	Req	Description
pool_class	string	yes	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

get_server_key ~48

Retrieve the server's Ed25519 public key, used to verify signed receipts on ledger entries and settlements without trusting this server. Use as the first step of any independent verification.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
result	string	yes	—

No examples provided.

get_settlement ~49

Retrieve one settlement record: the resolved verdict, the REP staked and slashed, and the signed receipt. Use when verifying how a pool resolved.

Input Output Examples

Name	Type	Req	Description
settlement_id	string	yes	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

get_solution ~40

Retrieve one machine-readable Resolution Artifact for a Class M dispute, including the reasoning and the attestations it resolved between.

Input Output Examples

Name	Type	Req	Description
solution_id	string	yes	—

Name	Type	Req	Description
result	string	yes	—

No examples provided.

list_issues ~55

List every Class H issue in the truth market with its current state and divisiveness index. Use when the user asks what is being contested, what is open for validation, or which claims are most divisive.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
result	string	yes	—

No examples provided.

list_solutions ~41

List all Resolution Artifacts — the machine-readable outcomes of Class M technical disputes. Use when the user wants settled answers rather than open questions.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
result	string	yes	—

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	61
27 Jul	61
28 Jul	62
29 Jul	63
30 Jul	63
31 Jul	68
1 Aug	68
2 Aug	69
3 Aug	69