← Back to search
Search • Rankings • TrustOps • Docs • Pricing • Claim/Manage
github-useorgx/orgx-mcp

useorgx/orgx-mcp

Organizational memory and agent orchestration MCP. Remember decisions, artifacts, tasks, and project context across Claude, ChatGPT, Cursor, and other agents.

JSON report • Policy • Badge metadata • History API •
• Global feed
DECISION SUMMARY

Block For Production

Score
n/a
Rank suppressed while production readiness shows a blocking verdict.
Confidence
High
Based on evidence completeness, recency, and validation density.
Evidence age
11.7h old
Freshness: fresh. Snapshot trustsnap_ad7042c87b02dc3b.
Top risk drivers
  • Trust Confidence
  • Tool Surface Design
  • Tool Snapshot Churn
Recommended actions
  • Make tools/list succeed unauthenticated when possible, or document the auth flow in the server card.
  • Fix the failing checks first, then revalidate to confirm the recovery path.
  • Compare tool enumeration outputs between runs and remove non-deterministic behavior.
Next action
revalidate, add safeguards, export policy
unauthenticated behavior not proven + failing live status
Compare alternatives Export policy Open report JSON Dispute this assessment
Observed Attention
No observed attention
No observed attention in the current 30-day window.
  • No segmented attention signals observed in the current window.
Bucketed signal based on recent segmented Verify telemetry. Crawler and evaluator activity is not treated as confirmed human demand.
Risk Compatibility Evidence Fix it Governance
Status
Failing
Score
n/a
Transport
streamable-http
Tools
0
Ownership
Unclaimed
Claim, revalidate, or manage this server
DISPUTE THIS ASSESSMENT

Dispute this assessment

If any published claim about this server -- its score, a risk flag, a capability classification, or its taxonomy -- is factually wrong, tell us what evidence shows and we will review it. This does not require claiming or verifying ownership of the server first.

Verify responds to disputes within 5 business days and resolves them within 15.

Dispute history

No disputes filed for this server.

Risk

Security posture
Tools analyzed
0
High-risk tools
0
Destructive tools
0
Exec tools
0
Egress tools
0
Secret tools
0
Bulk-access tools
0
Risk distribution
none
Tool capability & risk inventory

No tool inventory available from the latest validation run.

Write-action governance
Governance status
Not_Assessed
Safe to publish
✕
Auth boundary
oauth_or_auth_required
Blast radius
Low
High-risk tools
0
Confirmation signals
none
Safeguard count
0

Status detail: No write-action governance evidence is available yet.

ToolRiskFlagsSafeguards
No high-risk tools were detected on the latest run.
Action-controls diff

Need at least two validation runs before diffing action controls.

Critical alerts
High/critical-severity alerts
0
Production verdicts degrade quickly when high or critical-severity alerts are active.

Compatibility

Client compatibility verdicts

Client compatibility only means the server shape can work with a client. Production trust decision and write-action publishing are evaluated separately so a client-compatible server can still be blocked for production.

Client compatibility: ChatGPT
Partially client-compatible
tools/list must succeed.; Transport compliance failed or did not complete successfully.
Confidence: high (77.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initialize • OK
  • tools_list • Error
  • transport_compliance_probe • Error
  • step_up_auth_probe • OK
  • connector_replay_probe • Missing — Frozen tool snapshots must survive refresh.
  • request_association_probe • Missing — Roots, sampling, and elicitation should stay request-scoped.
Client compatibility: Claude
Not client-compatible
tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool.
Confidence: high (77.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initialize • OK
  • tools_list • Error
  • transport_compliance_probe • Error
Write-action publishing
Publishing blocked
Active alert(s) affecting production readiness: Latest validation is failing, tools/list regressed, Auth mode changed.
Confidence: high (77.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history
Disagreements: none
  • action_safety_probe • Not_Assessed
Snapshot churn risk
Low
No material tool-surface churn detected in the latest comparison.
Confidence: high (77.5)
Evidence provenance
Winner: history
Supporting sources: history, live_validation
Disagreements: none
  • tool_snapshot_probe • Missing
  • connector_replay_probe • Missing
Client compatibility gate details
ChatGPT custom connector
Partially client-compatible
Remediation checklist
  • tools/list must succeed.
  • Transport compliance failed or did not complete successfully.
  • The tool surface is not limited to search/fetch-style read tools.
  • Not yet safe for company-knowledge use: requires a search/fetch-only surface with no export, bulk, mutating, or high-blast-radius exposure.
  • Not yet safe for the Messages API remote MCP path: requires OAuth, a compatible connector profile, and no pending connector-refresh risk.
  • Transport compliance issues should be resolved before wider client rollout.
Claude remote MCP
Not client-compatible
Remediation checklist
  • tools/list must succeed.
  • Transport behavior should match Claude-compatible HTTP expectations.
  • A useful Claude integration needs at least one exposed tool.
  • The tool surface is not limited to search/fetch-style read tools.
  • Not yet safe for company-knowledge use: requires a search/fetch-only surface with no export, bulk, mutating, or high-blast-radius exposure.
  • Not yet safe for the Messages API remote MCP path: requires OAuth, a compatible connector profile, and no pending connector-refresh risk.
Write-safe publishing
Blocked
Remediation checklist
  • Add confirmation or dry-run semantics for risky actions.
  • Production readiness is blocked by an active alert: Latest validation is failing.
  • Production readiness is blocked by an active alert: tools/list regressed.
  • Production readiness is blocked by an active alert: Auth mode changed.
Verdict traces
Production verdict
Metadata only
No live validation evidence exists yet for this entry.
Confidence: high (77.5)
Winning source: live_validation
Triggering alerts
  • server_failing • critical • Latest validation is failing
  • tools_list_regressed • critical • tools/list regressed
  • auth_mode_changed • high • Auth mode changed
Client verdict trace table
VerdictStatusChecksWinning sourceConflicts
openai_connectors Partially client-compatible initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe live_validation none
claude_desktop Not client-compatible initialize, tools_list, transport_compliance_probe live_validation none
unsafe_for_write_actions Publishing blocked action_safety_probe live_validation none
snapshot_churn_risk Low tool_snapshot_probe, connector_replay_probe history none
Publishability policy profiles
ChatGPT custom connector compatibility
Compatible with review
tools/list must succeed.; Transport compliance failed or did not complete successfully. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: No
  • Oauth Configured: Yes
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Claude remote MCP compatibility
Compatible with review
tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: No
  • Oauth Configured: Yes
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Compatibility fixtures
ChatGPT custom connector fixture
Degraded
tools/list must succeed.; Transport compliance failed or did not complete successfully.
  • remote_http_endpoint: Passes
  • oauth_discovery: Passes
  • frozen_tool_snapshot_refresh: Passes
  • request_association: Passes
Anthropic remote MCP fixture
Degraded
tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool.
  • remote_transport: Passes
  • tool_discovery: Likely to fail
  • auth_connect: Passes
  • safe_write_review: Degraded
Recommended for

No recommendation profile is available yet.

Evidence

Current trust snapshot
Snapshot ID
trustsnap_ad7042c87b02dc3b
Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.
Snapshot generated
Aug 09, 2026 07:16:31 AM UTC
All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.
Last validated
Aug 08, 2026 07:34:28 PM UTC
Age: 11.7h • evidence age tier: Verified in last 24h • display score: suppressed

Canonical machine links

Compare index
/compare.json
Compare API
/v1/compare?server=github-useorgx%2Forgx-mcp
Trust summary
/v1/servers/github-useorgx/orgx-mcp/trust-summary
Report JSON
/v1/servers/github-useorgx/orgx-mcp/report
Policy export
/v1/servers/github-useorgx/orgx-mcp/policy
Badge metadata
/v1/servers/github-useorgx/orgx-mcp/badge
Ledger evidence
/v1/servers/github-useorgx/orgx-mcp/ledger
Human compare URL
/compare?server=github-useorgx%2Forgx-mcp
Evidence confidence
Confidence score
77.5
Based on 10 recent validations, 27 captured checks, and validation age of 11.7 hours.
Live checks captured
27
More direct checks increase trust in the current verdict.
Validation age
11.7h
Lower age means fresher evidence.
Latest validation evidence
Latest summary
Failing
Validation profile
remote_mcp
Started
Aug 08, 2026 07:34:23 PM UTC
Latency
4288.0 ms

Failures

  • openid_configuration Client error '404 Not Found' for url 'https://mcp.useorgx.com/.well-known/openid-configuration' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
  • prompts_list Client error '400 Bad Request' for url 'https://mcp.useorgx.com' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
  • resources_list Client error '400 Bad Request' for url 'https://mcp.useorgx.com' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
  • tools_list Client error '400 Bad Request' for url 'https://mcp.useorgx.com' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
  • transport_compliance_probe Issues: missing protocol header, bad protocol not rejected, expired session not 404 (bad protocol=200, DELETE=204, expired session=200).

Checks

CheckStatusLatencyEvidence
action_safety_probe Not_Assessed n/a No write-action risk evidence recorded.
advanced_capabilities_probe OK n/a 4 capability signal(s): completions, prompts, resource links, resources.
connector_publishability_probe Error n/a Publishability blockers: tools list, transport compliance, action safety, tool surface.
connector_replay_probe Missing n/a No connector replay evidence recorded.
determinism_probe Missing n/a tools list unavailable
initialize OK 819.1 ms Protocol 2025-03-26
interactive_flow_probe OK n/a Check completed
oauth_authorization_server OK 10.7 ms authorization_endpoint, client_id_metadata_document_supported, code_challenge_methods_supported, grant_types_supported
oauth_protected_resource OK 11.1 ms 1 authorization server(s)
official_registry_probe Missing n/a Check completed
openid_configuration Error 18.5 ms Client error '404 Not Found' for url 'https://mcp.useorgx.com/.well-known/openid-configuration' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
probe_noise_resilience OK 80.6 ms Fetched https://mcp.useorgx.com/robots.txt
prompt_get Missing n/a no prompt name
prompts_list Error 611.6 ms Client error '400 Bad Request' for url 'https://mcp.useorgx.com' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
protocol_version_probe Warning n/a Claims 2025-03-26; 2 release(s) behind 2025-11-25.
provenance_divergence_probe Not_Assessed n/a Check completed
request_association_probe Missing n/a No request-association capabilities were advertised.
resource_read Missing n/a no resource uri
resources_list Error 345.4 ms Client error '400 Bad Request' for url 'https://mcp.useorgx.com' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
schema_divergence_probe Missing n/a no live tools
server_card OK 256.1 ms 5 prompt(s) exposed
session_resume_probe OK 542.8 ms 37 tool(s) exposed
step_up_auth_probe OK n/a Scopes=agents:read, agents:write, decisions:read, decisions:write, +4 more; broad scopes=agents:write, decisions:write, initiatives:write.
tool_snapshot_probe Missing n/a no tools
tools_list Error 271.1 ms Client error '400 Bad Request' for url 'https://mcp.useorgx.com' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
transport_compliance_probe Error 385.0 ms Issues: missing protocol header, bad protocol not rejected, expired session not 404 (bad protocol=200, DELETE=204, expired session=200).
utility_coverage_probe OK 32.3 ms Completions advertised; pagination supported; tasks error.
Raw evidence view
Show raw JSON evidence

Large evidence payload summarized to keep this page fast. Full raw evidence remains available from the JSON report.

{
  "checks": {
    "count": 27,
    "items": {
      "action_safety_probe": {
        "auth_present": true,
        "reason": "empty_observation_set",
        "safeguard_count": 0,
        "status": "not_assessed"
      },
      "advanced_capabilities_probe": {
        "status": "ok"
      },
      "connector_publishability_probe": {
        "status": "error"
      },
      "connector_replay_probe": {
        "reason": "no_tools",
        "status": "missing"
      },
      "determinism_probe": {
        "reason": "tools_list_unavailable",
        "status": "missing"
      },
      "initialize": {
        "http_status": 200,
        "latency_ms": 819.14,
        "payload_omitted": true,
        "status": "ok"
      },
      "interactive_flow_probe": {
        "status": "ok"
      },
      "oauth_authorization_server": {
        "http_status": 200,
        "latency_ms": 10.73,
        "payload_omitted": true,
        "status": "ok"
      },
      "oauth_protected_resource": {
        "http_status": 200,
        "latency_ms": 11.07,
        "payload_omitted": true,
        "status": "ok"
      },
      "official_registry_probe": {
        "status": "missing"
      },
      "openid_configuration": {
        "latency_ms": 18.49,
        "reason": "Client error '404 Not Found' for url 'https://mcp.useorgx.com/.well-known/openid-configuration'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "status": "error"
      },
      "probe_noise_resilience": {
        "http_status": 200,
        "latency_ms": 80.57,
        "status": "ok"
      },
      "prompt_get": {
        "reason": "no_prompt_name",
        "status": "missing"
      },
      "prompts_list": {
        "http_status": 400,
        "latency_ms": 611.6,
        "payload_omitted": true,
        "reason": "Client error '400 Bad Request' for url 'https://mcp.useorgx.com'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
        "status": "error"
      },
      "protocol_version_probe": {
        "status": "warning"
      },
      "provenance_divergence_probe": {
        "status": "not_assessed"
      },
      "request_association_probe": {
        "reason": "no_request_association_capabilities_advertised",
        "status": "missing"
      },
      "resource_read": {
        "reason": "no_resource_uri",
        "status": "missing"
      },
      "resources_list": {
        "http_status": 400,
        "latency_ms": 345.4,
        "payload_omitted": true,
        "reason": "Client error '400 Bad Request' for url 'https://mcp.useorgx.com'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
        "status": "error"
      },
      "schema_divergence_probe": {
        "reason": "no_live_tools",
        "status": "missing"
      },
      "server_card": {
        "http_status": 200,
        "latency_ms": 256.11,
        "payload_omitted": true,
        "status": "ok",
        "tool_count": 37,
        "tool_names_preview": [
          "orgx_bootstrap",
          "orgx_search",
          "orgx_inspect",
          "orgx_recommend",
          "orgx_write",
          "orgx_attach",
          "orgx_act",
          "manage_lifecycle",
          "orgx_plan",
          "orgx_spawn",
          "orgx_decide",
          "orgx_submit_receipt",
          "orgx_emit_activity",
          "orgx_request_attention",
          "orgx_poll_attention",
          "orgx_ack_attention",
          "orgx_request_question",
          "orgx_poll_question",
          "orgx_emit_execution_graph",
          "approve_decision",
          "reject_decision",
          "get_agent_status",
          "get_initiative_pulse",
          "scaffold_initiative",
          "spawn_agent_task"
        ]
      },
      "session_resume_probe": {
        "http_status": 200,
        "latency_ms": 542.79,
        "payload_omitted": true,
        "status": "ok",
        "tool_count": 37,
        "tool_names_preview": [
          "approve_decision",
          "reject_decision",
          "get_agent_status",
          "query_org_memory",
          "get_initiative_pulse",
          "spawn_agent_task",
          "handoff_task",
          "recommend_next_action",
          "manage_lifecycle",
          "get_operator_chronicle",
          "check_execution_readiness",
          "orgx_emit_activity",
          "orgx_request_attention",
          "orgx_poll_attention",
          "orgx_ack_attention",
          "orgx_request_question",
          "orgx_poll_question",
          "orgx_emit_execution_graph",
          "consolidate_pr",
          "orgx_bootstrap",
          "orgx_inspect",
          "orgx_search",
          "orgx_recommend",
          "orgx_write",
          "orgx_attach"
        ]
      },
      "step_up_auth_probe": {
        "status": "ok"
      },
      "tool_snapshot_probe": {
        "reason": "no_tools",
        "status": "missing"
      },
      "tools_list": {
        "http_status": 400,
        "latency_ms": 271.08,
        "payload_omitted": true,
        "reason": "Client error '400 Bad Request' for url 'https://mcp.useorgx.com'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
        "status": "error"
      },
      "transport_compliance_probe": {
        "latency_ms": 385.03,
        "protocol_header_present": false,
        "status": "error"
      },
      "utility_coverage_probe": {
        "latency_ms": 32.28,
        "status": "ok"
      }
    },
    "omitted_count": 0
  },
  "failures": {
    "count": 5,
    "items": {
      "openid_configuration": {},
      "prompts_list": {},
      "resources_list": {},
      "tools_list": {},
      "transport_compliance_probe": {}
    },
    "omitted_count": 0
  },
  "message": "Raw evidence is summarized in HTML to keep server detail pages fast. Use the JSON report or evidence API for the full payload.",
  "remote_url": "https://mcp.useorgx.com",
  "server_card": {
    "name": null,
    "raw_payload_omitted": false,
    "version": null
  },
  "server_identifier": "github-useorgx/orgx-mcp",
  "truncated": true
}
Known versions
  • No versions recorded.
Validation history
7 day score delta
n/a
30 day score delta
n/a
Recent healthy ratio
0%
Freshness
11.7h
TimestampStatusScoreLatencyTools
Aug 08, 2026 07:34:28 PM UTC Failing 10.0 4288.0 ms 0
Aug 08, 2026 07:34:11 AM UTC Failing 10.0 3508.9 ms 0
Aug 07, 2026 07:34:03 PM UTC Failing 10.0 4023.0 ms 0
Aug 07, 2026 07:33:52 AM UTC Failing 10.0 3401.1 ms 0
Aug 06, 2026 07:33:19 PM UTC Failing 10.0 5048.9 ms 0
Aug 06, 2026 07:32:15 AM UTC Failing 10.8 3475.0 ms 0
Aug 05, 2026 11:30:53 PM UTC Failing 10.8 3601.6 ms 0
Aug 05, 2026 07:29:38 PM UTC Failing 18.0 8684.4 ms 0
Validation timeline
ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
Aug 08, 2026 07:34:28 PM UTC Failing 10.0 2025-03-26 oauth_supported 0 0 auth_mode_changed
Aug 08, 2026 07:34:11 AM UTC Failing 10.0 unknown unknown 0 0 none
Aug 07, 2026 07:34:03 PM UTC Failing 10.0 unknown unknown 0 0 none
Aug 07, 2026 07:33:52 AM UTC Failing 10.0 unknown unknown 0 0 none
Aug 06, 2026 07:33:19 PM UTC Failing 10.0 unknown unknown 0 0 none
Aug 06, 2026 07:32:15 AM UTC Failing 10.8 unknown unknown 0 0 none
Aug 05, 2026 11:30:53 PM UTC Failing 10.8 unknown unknown 0 0 none
Aug 05, 2026 07:29:38 PM UTC Failing 18.0 unknown unknown 0 0 none
Aug 04, 2026 02:00:37 AM UTC Failing 23.0 unknown unknown 0 0 none
Aug 02, 2026 09:18:22 PM UTC Failing 23.0 unknown unknown 0 0 none
Recent validation runs
Recent validation runs for this MCP server
StartedStatusSummaryLatencyChecks
Aug 08, 2026 07:34:23 PM UTC Completed Failing 4288.0 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, schema_divergence_probe, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Aug 08, 2026 07:34:07 AM UTC Completed Failing 3508.9 ms
Aug 07, 2026 07:33:59 PM UTC Completed Failing 4023.0 ms
Aug 07, 2026 07:33:48 AM UTC Completed Failing 3401.1 ms
Aug 06, 2026 07:33:14 PM UTC Completed Failing 5048.9 ms
Aug 06, 2026 07:32:11 AM UTC Completed Failing 3475.0 ms
Aug 05, 2026 11:30:49 PM UTC Completed Failing 3601.6 ms
Aug 05, 2026 07:29:29 PM UTC Completed Failing 8684.4 ms
Aug 04, 2026 02:00:32 AM UTC Completed Failing 4769.6 ms
Aug 02, 2026 09:18:18 PM UTC Completed Failing 4065.6 ms
Public server reputation
Validation success 7d
0.0
Validation success 30d
0.0
Mean time to recover
n/a
Breaking diffs 30d
0
Registry drift frequency 30d
0
Snapshot changes 30d
0
Incident & change feed
TimestampEventDetails
Aug 08, 2026 07:34:28 PM UTC Latest validation: failing Score 16.7 with status failing.
Aug 08, 2026 07:34:28 PM UTC Auth mode changed Auth mode moved from unknown to oauth_supported.
Aug 05, 2026 11:01:03 AM UTC Score corrected (post-1.0.503 remediation, R1 zero-anchoring) Prior: 23.04. Corrected: 16.38.
Capabilities
Use-case taxonomy
development communication productivity automation
Benchmark tasks
Benchmark taskStatusEvidence
Discover tools Likely to fail
  • initialize • OK
  • tools_list • Error
Read-only fetch flow Likely to fail
  • resource_read • Missing
  • read_only_tool_surface • Missing
OAuth-required connect Passes
  • oauth_protected_resource • OK
  • step_up_auth_probe • OK
Safe write flow with confirmation Likely to fail
  • action_safety_probe • Not_Assessed
Utility coverage
Probe status
OK
Completions
advertised
Completion probe target: { "type": "resource", "uri": "" }
Pagination
supported
No nextCursor evidence.
Tasks
Error
Advertised: yes
Transport compliance drilldown
Probe status
Error
Transport
streamable-http
Session header
yes
Protocol header
no
Bad protocol response
200
DELETE teardown
204
Expired session retry
200
Last-Event-ID visible
no

Issues: missing_protocol_header, bad_protocol_not_rejected, expired_session_not_404

Request association
Status
Missing
Advertised capabilities
none
Observed idle methods
none
Violating methods
none
Probe HTTP status
n/a
Issues
none
Connector replay
Status
Missing
Backward compatible
✕
Would break after refresh
✕
Added tools
none
Removed tools
none
Additive output changes
none
Required-argument replay breaks
ToolAdded required argsRemoved required args
No required-argument replay breaks detected.
Output-schema replay breaks
ToolRemoved propertiesAdded properties
No output-schema replay breaks detected.
Tool snapshot diff & changelog

Need at least two validation runs before building a tool changelog.

Validation diff
Score delta
0
Summary changed
no
Tool delta
0
Prompt delta
0
Auth mode changed
yes
Write surface expanded
no
Protocol regressed
no
Registry drift changed
no

Regressed checks: action_safety_probe, connector_publishability_probe, openid_configuration, prompts_list, provenance_divergence_probe, resources_list, tools_list, transport_compliance_probe

Improved checks: advanced_capabilities_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, probe_noise_resilience, server_card, session_resume_probe, step_up_auth_probe, utility_coverage_probe

Newly assessed dimensions: none

No longer assessed dimensions: none

ComponentPreviousLatestDelta
No component deltas between the latest two runs.
Registry & provenance divergence
Probe status
Error
Direct official match
no
Drift fields
homepage registry_identifier registry_source remote_url
FieldRegistryLive server card
Titlen/aOrgX MCP — Organizational Continuity for AI Agents
Versionn/a1.1.4
Homepagen/an/a
Active alerts
  • Latest validation is failing (critical)
    Core MCP flows did not validate successfully on the latest run.
  • tools/list regressed (critical)
    Tool discovery became less reliable on the latest run.
  • Auth mode changed (high)
    Auth mode changed from unknown to oauth_supported.
Aliases & registry graph
IdentifierSourceCanonicalScore
github-useorgx/orgx-mcp github_topic_registry yes n/a
useorgx/orgx-mcp glama_registry no n/a
Alias consolidation
Canonical identifier
github-useorgx/orgx-mcp
Duplicate aliases
1
Registry sources
github_topic_registry glama_registry
Remote URLs
Homepages
Source disagreements
FieldWhat differsObserved values
Registry source Multiple registries or registry sync paths claim this same canonical server. github_topic_registry glama_registry
Remote URL Aliases currently point at different MCP endpoints, which can indicate mirrors, stale registry data, or a real endpoint split. https://glama.ai/mcp/servers/m4dnfhbbru https://mcp.useorgx.com
Homepage Registry entries disagree on the primary homepage for this server. https://glama.ai/mcp/servers/m4dnfhbbru https://mcp.useorgx.com
Registry identifier Different registry-specific identifiers resolve to the same canonical server record here. github_topic_registry:useorgx/orgx-mcp glama_registry:m4dnfhbbru

Fix it

Why this score?
Access & Protocol
25/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
11/56
How well the tool/resource interface communicates and behaves under automation.
Security Posture
12/36
How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.
Reliability & Trust
6/24
Operational stability, consistency, and trustworthiness over time.
Discovery & Governance
11/28
How well the server is documented, listed, and governed in public registries.
Adoption & Market
4/8
Adoption clues and public evidence that the server is intended for external use.
Algorithmic score breakdown
Auth Operability
4/4
Measures whether auth discovery and protected access behave predictably for clients.
Error Contract Quality
0/4
Grades machine-readable error structure, status alignment, and remediation hints.
Rate-Limit Semantics
2/4
Checks whether quota/throttle responses are deterministic and automation-friendly.
Schema Completeness
0/4
Completeness of tool descriptions, parameter docs, examples, and schema shape.
Backward Compatibility
4/4
Stability score across tool schema/name drift relative to prior validations.
SLO Health
0/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
4/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
0/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
0/4
Confidence-adjusted reliability score that penalizes low evidence volume.
Abuse/Noise Resilience
1/4
How well the server preserves core behavior in the presence of noisy traffic patterns.
Prompt Contract
2/4
Quality of prompt metadata, argument shape, and prompt discoverability for clients.
Resource Contract
3/4
How completely resources and resource templates describe URIs, types, and usage shape.
Discovery Metadata
2/4
Homepage, docs, icon, repository, support, and license coverage for directory consumers.
Registry Consistency
2/4
Agreement between stored registry metadata, live server-card data, and current validation output.
Installability
1/4
How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.
Session Semantics
1/4
Determinism and state behavior across repeated MCP calls, including sticky-session surprises.
Tool Surface Design
0/4
Naming clarity, schema ergonomics, and parameter complexity across the tool surface.
Result Shape Stability
0/4
Stability of declared output schemas across validations, with penalties for drift or missing shapes.
OAuth Interop
4/4
Depth and client compatibility of OAuth/OIDC metadata beyond the minimal protected-resource check.
Recovery Semantics
0/4
Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.
Maintenance Signal
1/4
Versioning, update recency, and historical validation cadence that indicate active stewardship.
Adoption Signal
2/4
Directory presence and distribution clues that suggest the server is intended for external use.
Freshness Confidence
1/4
Confidence that recent validations are current enough and dense enough to trust operationally.
Transport Fidelity
3/4
Whether declared transport metadata matches the observed endpoint behavior and response formats.
Spec Recency
2/4
How close the server’s claimed MCP protocol version is to the latest known public revision.
Session Resume
4/4
Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.
Step-Up Auth
4/4
Whether OAuth metadata and WWW-Authenticate challenges support granular, incremental consent instead of broad upfront scopes.
Transport Compliance
1/4
Checks session headers, protocol-version enforcement, session teardown, and expired-session behavior.
Utility Coverage
3/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
1/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
2/4
How ready the server looks for client catalogs and managed connector programs.
Tool Snapshot Churn
0/4
Stability of the tool surface across recent validations, including add/remove and output-shape drift.
Connector Replay
0/4
Whether a previously published frozen connector snapshot would remain backward compatible after the latest tool refresh.
Request Association
0/4
Whether roots, sampling, and elicitation appear tied to active client requests instead of arriving unsolicited on idle sessions.
Interactive Flow Safety
4/4
Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.
Official Registry Presence
3/4
Whether the server appears directly or indirectly in the official MCP registry.
Safety Transparency
3/4
Clarity of docs, auth disclosure, support links, and other trust signals visible to integrators.
Tool Capability Clarity
0/4
How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.
Destructive Operation Safety
1/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
1/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
1/4
Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.
Data Exfiltration Resilience
0/4
Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.
Least Privilege Scope
1/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
1/4
Assesses secret-bearing tools, token leakage risk, and whether the public surface avoids obvious secret exposure.
Supply Chain Signal
0/4
Public metadata signal for repository, changelog, license, versioning, and recency that supports supply-chain trust.
Input Sanitization Safety
0/4
Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.
Tool Namespace Clarity
0/4
Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.
Actionable remediation
SeverityRemediationWhy it mattersRecommended action
Critical Ensure tools/list succeeds consistently Tools discovery is the minimum viable contract for most MCP clients and directories. Make tools/list succeed unauthenticated when possible, or document the auth flow in the server card.
Playbook
  • Make `tools/list` deterministic across repeated calls.
  • Document or relax auth requirements for discovery routes.
  • Check that tool names, descriptions, and schemas remain stable across deploys.
Critical Respond to latest validation is failing Core MCP flows did not validate successfully on the latest run. Fix the failing checks first, then revalidate to confirm the recovery path.
Playbook
  • Fix the failing checks first.
  • Review the latest incident feed and validation diff for the first regression.
  • Revalidate once the remediation lands.
Critical Respond to tools/list regressed Tool discovery became less reliable on the latest run. Compare tool enumeration outputs between runs and remove non-deterministic behavior.
High Align session and protocol behavior with Streamable HTTP expectations Clients increasingly rely on MCP-Protocol-Version, session teardown, and expired-session semantics. Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.
Playbook
  • Return `Mcp-Session-Id` and `Mcp-Protocol-Version` headers consistently on streamable HTTP responses.
  • Honor `DELETE` session teardown and return `404` when a deleted session is reused.
  • Reject invalid protocol-version headers with `400 Bad Request`.
High Resolve conflicting endpoints across registry aliases Registry aliases for this canonical server currently resolve to different live MCP endpoints (https://glama.ai/mcp/servers/m4dnfhbbru, https://mcp.useorgx.com). An agent following one registry entry reaches a different server than one following another. Confirm which endpoint is canonical, correct or retire the stale registry entry, and re-sync so every alias agrees on one remote_url.
Playbook
  • Identify which of the listed remote_url values is the operator's actual, currently-maintained endpoint.
  • Update or remove the registry entries pointing at any other endpoint (a mirror, a stale fork, or a decommissioned deployment).
  • Re-run registry sync and confirm the alias-consolidation view shows a single remote_url before treating this as resolved.
High Respond to auth mode changed Auth mode changed from unknown to oauth_supported. Document the new auth posture and confirm protected-resource and challenge metadata still match reality.
Medium Adopt a current MCP protocol revision Older protocol revisions reduce compatibility with newer clients and registry programs. Advertise a current MCP protocol revision (2025-06-18 or later) in both the initialize response and the MCP-Protocol-Version header.
Playbook
  • Update the server's advertised protocol version to a current MCP revision (2025-06-18 or later).
  • Return the negotiated version consistently in both the `initialize` response and the `MCP-Protocol-Version` header.
  • Revalidate and confirm `protocol_version_probe` reports `ok`.
Medium Close connector-publishing gaps Connector catalogs care about protocol recency, session behavior, auth clarity, and tool-surface stability.
Medium Publish OpenID configuration OIDC metadata improves token validation and client compatibility. Expose /.well-known/openid-configuration with issuer, jwks_uri, and supported grants.
Playbook
  • Serve `/.well-known/openid-configuration` with `issuer`, `jwks_uri`, `authorization_endpoint`, and `token_endpoint`.
  • List supported grant types in `grant_types_supported` and scopes in `scopes_supported`.
  • Revalidate and confirm the `openid_configuration` check returns `ok`.
Medium Raise Adoption & Market score Adoption clues and public evidence that the server is intended for external use. Increase external documentation and directory coverage so users can discover and evaluate the server.
Medium Raise Interface Quality score How well the tool/resource interface communicates and behaves under automation. Improve schemas, error contracts, and recovery messages so agents can reason about the surface automatically.
Medium Raise Reliability & Trust score Operational stability, consistency, and trustworthiness over time. Stabilize behavior over time and reduce failure drift between validation runs.
Medium Raise Security Posture score How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs. Reduce destructive, egress, exec, secret, and freeform-input risk across the exposed tool surface.
Playbook
  • Classify each tool by read/write/delete/exec/network capability and confirm the classification is intentional.
  • Gate high-risk tools behind scoped auth, narrow their schemas, and document safeguards such as allowlists or dry-run paths.
  • Revalidate after the risky tools are tightened so the security posture score reflects the current surface.
Medium Repair prompts/list or stop advertising prompts Prompt metadata should either work live or be removed from the advertised capability set. Only advertise prompts if prompts/list works and prompt arguments are documented.
Playbook
  • Only advertise prompts that are actually accessible.
  • Add prompt descriptions and argument docs.
  • Run a live `prompts/list` check after any prompt changes.
Medium Repair resources/list or stop advertising resources Resource metadata should either work live or be removed from the advertised capability set. Only advertise resources if resources/list works and resources expose stable URIs/types.
Playbook
  • Only advertise resources with stable URIs and read semantics.
  • Add MIME/type hints where possible.
  • Run a live `resources/list` and `resources/read` check after updates.
Low Publish or reconcile the server in the official MCP registry Official registry presence improves discovery confidence and cross-source consistency.
Point loss breakdown
ComponentCurrentPoints missing
Trust Confidence 0/4 -4.0
Tool Surface Design 0/4 -4.0
Tool Snapshot Churn 0/4 -4.0
Tool Namespace Clarity 0/4 -4.0
Tool Capability Clarity 0/4 -4.0
Task Success 0/4 -4.0
SLO Health 0/4 -4.0
Schema Completeness 0/4 -4.0
Result Shape Stability 0/4 -4.0
Request Association 0/4 -4.0
Recovery Semantics 0/4 -4.0
Input Sanitization Safety 0/4 -4.0
Compatibility profiles
OpenAI Connectors
77.8
partial
tools/list must succeed.; Transport compliance failed or did not complete successfully.
Connector URL: https://mcp.useorgx.com
# Complete OAuth in the client when prompted.
# Server: github-useorgx/orgx-mcp
Claude Desktop
50.0
blocked
tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool.
{
  "mcpServers": {
    "orgx-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.useorgx.com"]
    }
  }
}
Smithery
60.0
partial
Tool discovery must succeed.; Machine-readable failure semantics should be present.
smithery mcp add "https://mcp.useorgx.com"
Generic Streamable HTTP
66.7
partial
tools/list must succeed.; Session behavior should be predictable.
curl -sS https://mcp.useorgx.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Governance

MCP TrustOps

TrustOps turns this report into operational controls: freshness SLAs, authenticated validation, semantic benchmarks, policy exports, alert subscriptions, badges, cost/compliance metadata, and runtime routing. Fresh trusted index decisions stay separate from long-tail inventory so stale scores do not masquerade as current evidence.

Evidence age tier
Verified in last 24h
Policy SLA (contractual, distinct from the public 24h freshness window): 168.0h • confidence-weighted score (display score discounted for evidence age and confidence -- an internal TrustOps input, not the public score): n/a • evidence too old to display: ✕
Policy exports
Export policy
Formats: json, rego, yaml, github_action, gateway_config, client_report
Runtime routing
/v1/decide
Returns allowed tools, blocked tools, approval requirement, and reason.
Hosted runtime
Verify Hosted MCP
Deploy trusted servers from GitHub with secrets, egress controls, releases, rollback, and audit events.
Authenticated validation
✕
Premium publisher feature: paid authenticated runs verify scopes, write-action safeguards, and authorized tool execution.
Active trust badges
none
Semantic benchmarks
available
Templates cover GitHub, database, healthcare, web search, and CRM least-privilege jobs.
Supply chain
metadata signal
Deep scan checks are marked separately from public metadata signals.
Compliance metadata
✕
Terms, privacy, SOC 2, HIPAA, GDPR, retention, deletion, and audit-log fields are tracked as enterprise metadata.
Alert subscription types
Status changes Score drops or recovers Freshness SLA breach Validation schema drift OAuth or auth behavior changes Tool surface changes New or changed write tool Supply-chain signal changes Legal or compliance metadata changes
MCP Runtime hosting

Verify Hosted MCP turns a trusted server report into a managed remote MCP endpoint with GitHub deployment provenance, sandbox policy, encrypted secrets, release history, rollback, and audit/usage events.

Activation readiness
✕
Trusted hosted runtimes require fresh validation, a passing server state, a remote endpoint, and a minimum score.
Minimum tier
TrustOps
Publisher claim plus paid TrustOps tier are required before secrets or releases can be created.
Hosted endpoint
/hosted/{namespace}/{name}/mcp
The endpoint enforces egress allowlists and records audit/usage events.
Blockers
score_below_hosting_threshold server_not_healthy_or_degraded latest_validation_not_passing blocked_by_active_alerts blocked_by_production_readiness
DeploymentStatusEndpointRelease
No hosted runtime deployments yet.
Authenticated validation sessions

Public validation is free. Authenticated validation is paid and proves scoped behavior, write-action safeguards, and authenticated tool execution.

Latest profile
remote_mcp
Authenticated session used
✕
Public score isolation
✓
Preview endpoint
/v1/verify
CI preview endpoint
/v1/ci/preview
Install snippets
Openai Connectors
Connector URL: https://mcp.useorgx.com
# Complete OAuth in the client when prompted.
# Server: github-useorgx/orgx-mcp
Claude Desktop
{
  "mcpServers": {
    "orgx-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.useorgx.com"]
    }
  }
}
Smithery
smithery mcp add "https://mcp.useorgx.com"
Generic Http
curl -sS https://mcp.useorgx.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'
Agent access & tool surface
Live server tools
No live tool surface captured yet.
Observed from the latest live validation against https://mcp.useorgx.com. This is the target server surface, not Verify's own inspection tools.
Live capability counts
0 tools • 0 prompts • 0 resources
Counts come from the latest tools/list, prompts/list, and resources/list checks.
Inspect with Verify
search fetch search_servers recommend_servers get_server_report compare_servers
Use Verify itself to search, recommend, compare, and fetch the full report for github-useorgx/orgx-mcp.
Direct machine links
JSON report • Compare this server • Verify MCP API