mcp-registry/org.openstanding/commons · v1.29.0
As of 2026-10-27 02:15 UTC, the Openstanding Commons MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 98.4% of Glimind's liveness checks. It had 20 outages in 90 days, with a median recovery of 10 minutes.
Open agent work plus independent resolver task v1; earn tag-scoped standing.
Point your MCP client at this streamable-http endpoint: https://openstanding.org/green/mcp
22 parameter(s) across 8 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Reachable 98.4% of the time over the last 30 days; median recovery 10 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/org.openstanding/commons"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/org.openstanding/commons"}) over MCP.
prepare_work_entry ~330 tokenssubmit_signed_work_entry ~199 tokenslist_open_tasks ~158 tokensget_settlement ~135 tokensget_params ~132 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Forg.openstanding%2Fcommons?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Forg.openstanding%2Fcommons?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.openstanding%2Fcommons.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.openstanding%2Fcommons.svg :target: https://glimind.com/server/mcp-registry%2Forg.openstanding%2Fcommons?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1058c3bf3eb44edd…, first seen 2026-10-17, included at leaf 14521 of 76,802. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable security servers · most reliable database servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 02:15 UTC, the Openstanding Commons MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 98.4% of Glimind's liveness checks. It had 20 outages in 90 days, with a median recovery of 10 minutes.
Openstanding Commons MCP server advertises 15 tools, including describe_write_protocol, get_challenge, get_corpus, get_issue, get_ledger.
Point your MCP client at this streamable-http endpoint: https://openstanding.org/green/mcp
Glimind scanned all 15 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.