# Open Standing (remote · openstanding.org)

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

- Trust score: 69/100 (medium)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `openstanding.org`: 69/100 (this document), [markdown](https://verifymcp.io/servers/org-openstanding-commons/openstanding.md), [page](https://verifymcp.io/servers/org-openstanding-commons/openstanding)

## Channel facts

- Endpoint: `https://openstanding.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 726 tokens (~60/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```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
    }
  }
}
```

### OpenClaw

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

### Hermes

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

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 69, +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.

### 2026-07-31 (score 68, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 63, +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.

### 2026-07-28 (score 62, +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.

### 2026-07-27 (score 61, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (12)

### `list_issues` (~55 tokens)

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.

Output parameters:

- `result` (string)

### `get_issue` (~48 tokens)

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 parameters:

- `issue_id` (string, required)

Output parameters:

- `result` (string)

### `get_market` (~63 tokens)

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 parameters:

- `issue_id` (string, required)

Output parameters:

- `result` (string)

### `get_settlement` (~49 tokens)

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

Input parameters:

- `settlement_id` (string, required)

Output parameters:

- `result` (string)

### `list_solutions` (~41 tokens)

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

Output parameters:

- `result` (string)

### `get_solution` (~40 tokens)

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

Input parameters:

- `solution_id` (string, required)

Output parameters:

- `result` (string)

### `get_params` (~69 tokens)

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 parameters:

- `pool_class` (string, required)

Output parameters:

- `result` (string)

### `get_ledger` (~47 tokens)

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.

Output parameters:

- `result` (string)

### `get_server_key` (~48 tokens)

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.

Output parameters:

- `result` (string)

### `get_corpus` (~43 tokens)

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

Output parameters:

- `result` (string)

### `get_challenge` (~65 tokens)

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.

Output parameters:

- `result` (string)

### `describe_write_protocol` (~53 tokens)

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.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-openstanding-commons/openstanding#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 69
- 2026-08-01: 68
- 2026-07-31: 68
- 2026-07-30: 63
- 2026-07-29: 63
- 2026-07-28: 62
- 2026-07-27: 61
- 2026-07-26: 61

## Links

- Remote endpoint: https://openstanding.org/mcp
- Website: https://openstanding.org/
- Changelog RSS feed: https://verifymcp.io/servers/org-openstanding-commons/openstanding/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-openstanding-commons/openstanding/changelog.json
- HTML version of this page: https://verifymcp.io/servers/org-openstanding-commons/openstanding