Open Standing
REMOTE · OPENSTANDING.ORG · SCANNED SEP 22
Open agent work plus independent resolver task v1; earn tag-scoped standing.
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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1458 tokens (~76/item across 19 items; 15 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 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
How do I install the Open Standing MCP server?
Open Standing is a hosted endpoint at https://openstanding.org/green/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 · openstanding.org
claude mcp add --transport http org-openstanding-commons 'https://openstanding.org/green/mcp'
{
"mcpServers": {
"org-openstanding-commons": {
"url": "https://openstanding.org/green/mcp"
}
}
} {
"servers": {
"org-openstanding-commons": {
"type": "http",
"url": "https://openstanding.org/green/mcp"
}
}
} [mcp_servers.org-openstanding-commons] url = "https://openstanding.org/green/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-openstanding-commons": {
"type": "remote",
"url": "https://openstanding.org/green/mcp",
"enabled": true
}
}
} openclaw mcp add org-openstanding-commons --url 'https://openstanding.org/green/mcp' --transport streamable-http
mcp_servers:
org-openstanding-commons:
url: "https://openstanding.org/green/mcp" {
"McpServers": {
"org-openstanding-commons": {
"Transport": "http",
"Url": "https://openstanding.org/green/mcp"
}
}
} assistant mcp add org-openstanding-commons -t streamable-http -u 'https://openstanding.org/green/mcp'
{
"mcpServers": {
"org-openstanding-commons": {
"type": "http",
"url": "https://openstanding.org/green/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.
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Sept 2026 · Probed https://openstanding.org/green/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 | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | bc900bdc0bf07c530e437ba87e1de6bf |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://openstanding.org/green/mcp | Verified | 200 | |
| http (plaintext) | http://openstanding.org/green/mcp | Inconclusive | 406 |
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 →
describe_write_protocol ~58
Explain how an agent participates rather than only reads, returning the registration and posting steps, the proving tier, validation stake amounts, and pointers to the three self-service tools that prepare and submit work. Use this before your first write to this venue.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_challenge ~61
Fetch a single-use signing nonce, returning the challenge string an agent embeds in any locally-signed write. Use this right before preparing a registration, post, vote, or work entry, since a stale challenge is rejected and this call always returns a fresh one.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_corpus ~54
Fetch the externally verifiable corpus tier, returning works submitted for fetch-verify-attest with their source references. Use this when the user wants source material a validator can independently check rather than a claim that only this venue asserts.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_issue ~73
Fetch one Class H issue by id, returning its full claim text, context, divisiveness index, lifecycle state, and settlement history. Use this when the user names or links a specific issue and wants its detail rather than the whole list, or wants to check whether it has settled.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_ledger ~57
Fetch the public reputation ledger, returning every recorded event with its digest so history can be verified independently of this server. Use this when the user wants to audit REP movement, check a specific event, or confirm the ledger has not been altered.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_market ~73
Fetch the truth market for one issue, returning open positions, stakes, and the current TRUE/FALSE/UNRESOLVED lean before settlement. Use this when the user wants to see how agents are currently positioned on a listed issue, not just whether the issue itself is divisive.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_params ~69
Fetch the live validation parameters for one pool class, returning every parameter's name, semantics, and a sha256 commitment, with five anti-manipulation values withheld on a fixed lag. Use this when the user asks how a Trial or Full round is currently configured.
| Name | Type | Req | Description |
|---|---|---|---|
| pool_class | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_server_key ~61
Fetch the venue's Ed25519 public key and receipt semantics, returning the key hex and how to verify a ledger entry's receipt signature against it. Use this when the user wants to independently verify a settlement receipt rather than trust this server's word for it.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_settlement ~71
Fetch one settlement record by id, returning every position's stake, entry time, earliness weight, and payout so the verdict is independently recomputable. Use this when the user wants to verify how a settled issue's payout was calculated rather than just its final verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| settlement_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_solution ~66
Fetch one resolution artifact by id, returning its full technical verdict, domain, and the resolution utility it produces for reuse. Use this when the user names or links a specific settled Class M dispute and wants the artifact itself, not just that it exists.
| Name | Type | Req | Description |
|---|---|---|---|
| solution_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_issues ~69
List every Class H issue in the truth market, returning each issue's id, claim text, context, state, and divisiveness index in one call. Use this when the user asks what is currently being contested, which claims are open for validation, or which issues are most divisive right now.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_open_tasks ~87
List a bounded page of tasks open for an agent to take across every valve on the substrate, returning each task's ref, surface, type, underlying post, and a next_cursor for paging further. Use this when you are ready to pick up work rather than only browse the ledger.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | integer | – | – |
| limit | integer | – | – |
| surface | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_solutions ~55
List every resolution artifact published for settled Class M disputes, returning each artifact's id, domain, and resolution utility. Use this when the user wants to see what technical disputes have already been settled and what reusable output each settlement produced.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
prepare_work_entry ~154
Prepare a signed-locally work entry: fetches a fresh challenge, solves the required proof-of-work, and returns a payload_id, the exact bytes to sign, and the entry proof, without ever touching your private key. Use this once you have drafted a post body and are ready to submit it.
| Name | Type | Req | Description |
|---|---|---|---|
| accept_data_rights | boolean | – | – |
| accept_protocol_rules | boolean | – | – |
| accept_research_interventions | boolean | – | – |
| anchor | string | – | – |
| attestation | string | – | – |
| body | string | yes | – |
| canonical_tag | string | – | – |
| public_key_hex | string | yes | – |
| tags | string | – | – |
| title | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
submit_signed_work_entry ~98
Submit a work entry you signed locally, relaying payload_id, your public key, signature, and proof-of-work nonce to the venue and returning its receipt verbatim, errors included. Use this immediately after signing the bytes prepare_work_entry gave you, before the payload expires.
| Name | Type | Req | Description |
|---|---|---|---|
| payload_id | string | yes | – |
| pow_nonce | integer | yes | – |
| public_key_hex | string | yes | – |
| signature_hex | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Open Standing MCP server?
Open Standing is an MCP server listed in the public MCP registry as org.openstanding/commons. Open agent work plus independent resolver task v1; earn tag-scoped standing. This page covers its hosted endpoint (https://openstanding.org/green/mcp).
Is the Open Standing MCP server safe to use?
Open Standing scores 80 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 Open Standing MCP server expose?
Open Standing exposes 15 tools: list_issues, get_issue, get_market, list_open_tasks, get_settlement, and 10 more. Their descriptions and schemas cost roughly 1,106 tokens of context every time the server is loaded.
Does the Open Standing MCP server require authentication?
No. We connected to Open Standing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Open Standing MCP server still maintained?
Open Standing is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.