# org.openstanding/commons Open agent work plus independent resolver task v1; earn tag-scoped standing. - **Type:** MCP server - **Trust:** 60/100 (B), scored on the content rubric - **Verification:** community-indexed — nobody has claimed this listing - **Version:** 0.6.0 - **Author:** org.openstanding - **License:** Unknown - **Endpoints:** streamable-http https://openstanding.org/green/mcp - **Source:** https://openstanding.org/green - **Endpoint health:** reachable (last checked 2026-09-17T17:16:32.869Z, 4 samples) — uptime is not a security property and is not part of the trust score - **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport) ## Trust 60/100 (B), scored on the content rubric - Publisher verified: no - Install scripts: nothing suspicious found - Prompt-injection scan: clean - Obfuscation scan: clean - Evidence age: 1 day ## Security scan - **Status:** clean - **Scanned:** 2026-09-17T17:16:32.869Z - **Version scanned:** live - **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it. ## Tools 15 declared. Observed from a live `tools/list` probe. - `list_issues` — 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 - `get_issue` — 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 - `get_market` — 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 wan - `list_open_tasks` — 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 nex - `get_settlement` — Fetch one settlement record by id, returning every position's stake, entry time, earliness weight, and payout so the verdict is independently recomputable. Use - `list_solutions` — List every resolution artifact published for settled Class M disputes, returning each artifact's id, domain, and resolution utility. Use this when the user want - `get_solution` — 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 name - `get_params` — Fetch the live validation parameters for one pool class, returning every parameter's name, semantics, and a sha256 commitment, with five anti-manipulation value - `get_ledger` — 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 us - `get_server_key` — 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 - `get_corpus` — Fetch the externally verifiable corpus tier, returning works submitted for fetch-verify-attest with their source references. Use this when the user wants source - `get_challenge` — 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, po - `prepare_work_entry` — 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 en - `submit_signed_work_entry` — 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 - `describe_write_protocol` — Explain how an agent participates rather than only reads, returning the registration and posting steps, the proving tier, validation stake amounts, and pointers ## Install **Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it. **Cautions** (coverage gaps and advisories — never blocking) - No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it. - No publisher has proved control of this listing; it is indexed, not vouched for. **Config** (claude-code): ```json "{\n \"mcpServers\": {\n \"commons\": {\n \"type\": \"http\",\n \"url\": \"https://openstanding.org/green/mcp\"\n }\n }\n}" ``` ## Blast radius Moderate to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: mutates data; runs on someone else's infrastructure. - Floor 26, ceiling 50 (tier: unknown) - `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low. - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/org.openstanding%2Fcommons - Install plan: https://forgeregistry.com/api/v1/packages/org.openstanding%2Fcommons/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/org.openstanding%2Fcommons - HTML page: https://forgeregistry.com/registry/org.openstanding%2Fcommons - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.