OrgX MCP — Organizational Continuity for AI Agents
REMOTE · MCP.USEORGX.COM · 2 COMPONENTS · SCANNED AUG 3
Make AI work resumable, reviewable, and provable across agents.
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 →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify sse. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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 · mcp.useorgx.com
claude mcp add --transport http com-useorgx-orgx-mcp https://mcp.useorgx.com/sse
[mcp_servers.com-useorgx-orgx-mcp] url = "https://mcp.useorgx.com/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-useorgx-orgx-mcp": {
"type": "remote",
"url": "https://mcp.useorgx.com/sse",
"enabled": true
}
}
} openclaw mcp add com-useorgx-orgx-mcp --url https://mcp.useorgx.com/sse --transport streamable-http
mcp_servers:
com-useorgx-orgx-mcp:
url: "https://mcp.useorgx.com/sse" {
"mcpServers": {
"com-useorgx-orgx-mcp": {
"type": "http",
"url": "https://mcp.useorgx.com/sse"
}
}
} 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.
- 31 Jul 26 +12
- 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 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 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 22
First indexed and scored.
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://mcp.useorgx.com/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=useorgx.com | CN=WE1,O=Google Trust Services,C=US | 20 Jul 2026 | 18 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 76efb333f8e2a6d00e74c714b9a471a1 |
| SANs: useorgx.com, mcp.useorgx.com | ||||||
| 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 mcp.useorgx.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| useorgx.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://mcp.useorgx.com/.well-known/oauth-protected-resource/sse", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://mcp.useorgx.com/.well-known/oauth-protected-resource/sse", error="invalid_token", error_description="Missing or invalid access token"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self' https://*.clerk.accounts.dev https://clerk.useorgx.com https://accounts.useorgx.com; img-src 'self' data: https:; font-src 'self' data: https:; style-src 'self' 'unsafe-inline' https:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; connect-src 'self' https://mcp.useorgx.com https://useorgx.com https://www.useorgx.com https://*.useorgx.com https://*.clerk.accounts.dev https://clerk.useorgx.com https://accounts.useorgx.com wss:; worker-src 'self' blob:; frame-src 'self' https://*.clerk.accounts.dev https://clerk.useorgx.com https://accounts.useorgx.com; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), fullscreen=(self) |
| www-authenticate | Bearer realm="OAuth", resource_metadata="https://mcp.useorgx.com/.well-known/oauth-protected-resource/sse", error="invalid_token", error_description="Missing or invalid access token" |
Protected resource metadata
| Document | https://mcp.useorgx.com/.well-known/oauth-protected-resource/sse |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.useorgx.com/sse |
| Authorisation server | https://mcp.useorgx.com |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://mcp.useorgx.com/sse | Auth required | 401 | |
| http (plaintext) | http://mcp.useorgx.com/sse | Inconclusive | 401 |
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.
No tool schema has been captured from this endpoint yet.