← Back to search
Search • Rankings • TrustOps • Docs • Pricing • Claim/Manage
okareo-ai/okareo-mcp

Okareo MCP Server

Exposes Okareo's evaluation capabilities as MCP tools, enabling AI coding assistants to manage scenarios, register models, run evaluations, and execute multi-turn simulations directly from the editor.

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

Block For Production

Score
n/a
Percentile pending
Confidence
High
Based on evidence completeness, recency, and validation density.
Evidence age
5.2h old
Freshness: fresh. Snapshot trustsnap_070978f9e430b6b5.
Top risk drivers
  • Utility Coverage
  • Tool Surface Design
  • Tool Snapshot Churn
Recommended actions
  • Make tools/list succeed unauthenticated when possible, or document the auth flow in the server card.
  • Allow initialize to succeed consistently, or return a deterministic auth-required response with clear metadata.
  • Compare initialize responses between the latest two runs and restore the previous stable behavior.
Next action
revalidate, add safeguards, export policy
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
OK
Safe to publish
✓
Auth boundary
public_or_unclear
Blast radius
Low
High-risk tools
0
Confirmation signals
none
Safeguard count
0

Status detail: No unsafe write-action governance gaps detected on the latest validation.

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
Critical alerts
0
Production verdicts degrade quickly when critical 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
Not client-compatible
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Initialize must be reachable.; tools/list must succeed.; Transport compliance should be in good shape.; OAuth interoperability should be strong.
Confidence: high (77.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initialize • Error
  • tools_list • Skipped
  • transport_compliance_probe • Skipped
  • step_up_auth_probe • Missing
  • 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
Initialize must succeed or cleanly request auth.; 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 • Error
  • tools_list • Skipped
  • transport_compliance_probe • Skipped
Write-action publishing
Publishing allowed
Current write surface is bounded enough for cautious review with production policy controls.
Confidence: high (77.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history
Disagreements: none
  • action_safety_probe • OK
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
Not client-compatible
Remediation checklist
  • OpenAI connectors expect OAuth for remote server auth.
  • Dynamic client registration materially improves connector setup.
  • Initialize must be reachable.
  • tools/list must succeed.
  • Transport compliance should be in good shape.
  • OAuth interoperability should be strong.
Claude remote MCP
Not client-compatible
Remediation checklist
  • Initialize must succeed or cleanly request auth.
  • 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.
  • OAuth is not configured, so this client cannot authenticate without additional setup.
Write-safe publishing
Ready
Remediation checklist
  • No explicit blockers recorded.
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
  • initialize_regressed • critical • Initialize flow regressed
  • tools_list_regressed • critical • tools/list regressed
Client verdict trace table
VerdictStatusChecksWinning sourceConflicts
openai_connectors Not 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 allowed 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
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Initialize must be reachable.; tools/list must succeed.; Transport compliance should be in good shape.; OAuth interoperability should be strong. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: No
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Claude remote MCP compatibility
Compatible with review
Initialize must succeed or cleanly request auth.; 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: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Compatibility fixtures
ChatGPT custom connector fixture
Degraded
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Initialize must be reachable.; tools/list must succeed.; Transport compliance should be in good shape.; OAuth interoperability should be strong.
  • remote_http_endpoint: Passes
  • oauth_discovery: Degraded
  • frozen_tool_snapshot_refresh: Passes
  • request_association: Passes
Anthropic remote MCP fixture
Degraded
Initialize must succeed or cleanly request auth.; 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: Likely to fail
  • safe_write_review: Passes
Recommended for

No recommendation profile is available yet.

Evidence

Current trust snapshot
Snapshot ID
trustsnap_070978f9e430b6b5
Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.
Snapshot generated
Aug 05, 2026 09:12:53 PM UTC
All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.
Last validated
Aug 05, 2026 04:02:42 PM UTC
Age: 5.17h • evidence age tier: Verified in last 24h • display score: suppressed

Canonical machine links

Compare index
/compare.json
Compare API
/v1/compare?server=okareo-ai%2Fokareo-mcp
Trust summary
/v1/servers/okareo-ai/okareo-mcp/trust-summary
Report JSON
/v1/servers/okareo-ai/okareo-mcp/report
Policy export
/v1/servers/okareo-ai/okareo-mcp/policy
Badge metadata
/v1/servers/okareo-ai/okareo-mcp/badge
Ledger evidence
/v1/servers/okareo-ai/okareo-mcp/ledger
Human compare URL
/compare?server=okareo-ai%2Fokareo-mcp
Evidence confidence
Confidence score
77.5
Based on 10 recent validations, 26 captured checks, and validation age of 5.2 hours.
Live checks captured
26
More direct checks increase trust in the current verdict.
Validation age
5.2h
Lower age means fresher evidence.
Latest validation evidence
Latest summary
Failing
Validation profile
remote_mcp
Started
Aug 05, 2026 04:02:42 PM UTC
Latency
271.2 ms

Failures

  • initialize Expecting value: line 1 column 1 (char 0)
  • oauth_authorization_server no authorization server
  • oauth_protected_resource Client error '404 Not Found' for url 'https://glama.ai/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
  • openid_configuration no authorization server
  • server_card Client error '404 Not Found' for url 'https://glama.ai/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404

Checks

CheckStatusLatencyEvidence
action_safety_probe OK n/a No high-risk write, destructive, or exec tools detected.
advanced_capabilities_probe Missing n/a No advanced MCP capability signals detected.
connector_publishability_probe Error n/a Publishability blockers: initialize, tools list, protocol version, session resume, +4 more.
connector_replay_probe Missing n/a No connector replay evidence recorded.
determinism_probe Skipped n/a initialize unreachable
initialize Error 97.4 ms Expecting value: line 1 column 1 (char 0)
interactive_flow_probe Missing n/a Check completed
oauth_authorization_server Missing n/a no authorization server
oauth_protected_resource Error 56.8 ms Client error '404 Not Found' for url 'https://glama.ai/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
official_registry_probe Warning n/a Check completed
openid_configuration Missing n/a no authorization server
probe_noise_resilience OK 12.6 ms Fetched https://glama.ai/robots.txt
prompt_get Missing n/a not advertised
prompts_list Skipped n/a initialize unreachable
protocol_version_probe Missing n/a No protocol version was advertised.
provenance_divergence_probe OK n/a Check completed
request_association_probe Missing n/a No request-association capabilities were advertised.
resource_read Missing n/a not advertised
resources_list Skipped n/a initialize unreachable
server_card Error 89.5 ms Client error '404 Not Found' for url 'https://glama.ai/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
session_resume_probe Skipped n/a initialize unreachable
step_up_auth_probe Missing n/a No OAuth or incremental-scope signals detected.
tool_snapshot_probe Missing n/a no tools
tools_list Skipped n/a initialize unreachable
transport_compliance_probe Skipped n/a Session header=no, protocol header=no, bad protocol=n/a.
utility_coverage_probe Missing n/a No completions evidence; no pagination evidence; tasks skipped.
Raw evidence view
Show raw JSON evidence 
{
  "checks": {
    "action_safety_probe": {
      "details": {
        "auth_present": false,
        "confirmation_signals": [],
        "safeguard_count": 0,
        "summary": {
          "bulk_access_tools": 0,
          "capability_distribution": {},
          "destructive_tools": 0,
          "egress_tools": 0,
          "exec_tools": 0,
          "high_risk_tools": 0,
          "risk_distribution": {
            "critical": 0,
            "high": 0,
            "low": 0,
            "medium": 0
          },
          "secret_tools": 0,
          "tool_count": 0
        }
      },
      "latency_ms": null,
      "status": "ok"
    },
    "advanced_capabilities_probe": {
      "details": {
        "capabilities": {
          "completions": false,
          "elicitation": false,
          "prompts": false,
          "resource_links": false,
          "resources": false,
          "roots": false,
          "sampling": false,
          "structured_outputs": false
        },
        "enabled": [],
        "enabled_count": 0,
        "initialize_capability_keys": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "connector_publishability_probe": {
      "details": {
        "blockers": [
          "initialize",
          "tools_list",
          "protocol_version",
          "session_resume",
          "transport_compliance",
          "server_card",
          "tool_surface",
          "auth_flow"
        ],
        "criteria": {
          "action_safety": true,
          "auth_flow": false,
          "connector_replay": true,
          "initialize": false,
          "protocol_version": false,
          "remote_transport": true,
          "request_association": true,
          "server_card": false,
          "session_resume": false,
          "step_up_auth": true,
          "tool_surface": false,
          "tools_list": false,
          "transport_compliance": false
        },
        "high_risk_tools": 0,
        "tool_count": 0,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "error"
    },
    "connector_replay_probe": {
      "details": {
        "reason": "no_tools"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "determinism_probe": {
      "details": {
        "reason": "initialize_unreachable"
      },
      "latency_ms": null,
      "status": "skipped"
    },
    "initialize": {
      "details": {
        "error": "Expecting value: line 1 column 1 (char 0)",
        "url": "https://glama.ai/mcp/servers/mgrr2j1cxk"
      },
      "latency_ms": 97.36,
      "status": "error"
    },
    "interactive_flow_probe": {
      "details": {
        "oauth_supported": false,
        "prompt_available": false,
        "risk_hits": [],
        "safe_hits": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_authorization_server": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_protected_resource": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://glama.ai/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://glama.ai/.well-known/oauth-protected-resource"
      },
      "latency_ms": 56.8,
      "status": "error"
    },
    "official_registry_probe": {
      "details": {
        "direct_match": false,
        "official_identifiers": [
          "ai.ai-akari/one-minute-akari",
          "ai.bizmuse/bizmuse",
          "ai.boolsai/directory",
          "ai.agentutility/mcp-model-router",
          "ai.analyticslegends/sap-analytics",
          "ai.auteng/mcp",
          "ai.clelp/clelp",
          "ai.getoptimal/optibot",
          "ai.alphacreek/alphacreek-mcp",
          "ai.arclan/registry"
        ],
        "official_peer_count": 10,
        "registry_source": "glama_registry"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "openid_configuration": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "probe_noise_resilience": {
      "details": {
        "headers": {
          "content-type": "text/plain; charset=utf-8",
          "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
        },
        "http_status": 200,
        "url": "https://glama.ai/robots.txt",
        "validation_disallowed": false
      },
      "latency_ms": 12.61,
      "status": "ok"
    },
    "prompt_get": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "prompts_list": {
      "details": {
        "reason": "initialize_unreachable"
      },
      "latency_ms": null,
      "status": "skipped"
    },
    "protocol_version_probe": {
      "details": {
        "latest_known_version": "2025-11-25",
        "reason": "no_protocol_version",
        "validator_protocol_version": "2025-03-26"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "provenance_divergence_probe": {
      "details": {
        "direct_official_match": false,
        "drift_fields": [],
        "metadata_document_count": 1,
        "registry_homepage": null,
        "registry_repository": null,
        "registry_title": null,
        "registry_version": null,
        "server_card_homepage": null,
        "server_card_repository": null,
        "server_card_title": null,
        "server_card_version": null
      },
      "latency_ms": null,
      "status": "ok"
    },
    "request_association_probe": {
      "details": {
        "reason": "no_request_association_capabilities_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resource_read": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resources_list": {
      "details": {
        "reason": "initialize_unreachable"
      },
      "latency_ms": null,
      "status": "skipped"
    },
    "server_card": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://glama.ai/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://glama.ai/.well-known/mcp/server-card.json"
      },
      "latency_ms": 89.45,
      "status": "error"
    },
    "session_resume_probe": {
      "details": {
        "reason": "initialize_unreachable"
      },
      "latency_ms": null,
      "status": "skipped"
    },
    "step_up_auth_probe": {
      "details": {
        "auth_required_checks": [],
        "broad_scopes": [],
        "challenge_headers": [],
        "minimal_scope_documented": false,
        "oauth_present": false,
        "scope_specificity_ratio": 0.0,
        "step_up_signals": [],
        "supported_scopes": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tool_snapshot_probe": {
      "details": {
        "reason": "no_tools"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tools_list": {
      "details": {
        "reason": "initialize_unreachable"
      },
      "latency_ms": null,
      "status": "skipped"
    },
    "transport_compliance_probe": {
      "details": {
        "reason": "initialize_unreachable"
      },
      "latency_ms": null,
      "status": "skipped"
    },
    "utility_coverage_probe": {
      "details": {
        "completions": {
          "advertised": false,
          "live_probe": "not_executed",
          "sample_target": null
        },
        "initialize_capability_keys": [],
        "pagination": {
          "metadata_signal": false,
          "next_cursor_methods": [],
          "supported": false
        },
        "tasks": {
          "advertised": false,
          "http_status": null,
          "probe_status": "skipped"
        }
      },
      "latency_ms": null,
      "status": "missing"
    }
  },
  "failures": {
    "initialize": {
      "error": "Expecting value: line 1 column 1 (char 0)",
      "url": "https://glama.ai/mcp/servers/mgrr2j1cxk"
    },
    "oauth_authorization_server": {
      "reason": "no_authorization_server"
    },
    "oauth_protected_resource": {
      "error": "Client error '404 Not Found' for url 'https://glama.ai/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://glama.ai/.well-known/oauth-protected-resource"
    },
    "openid_configuration": {
      "reason": "no_authorization_server"
    },
    "server_card": {
      "error": "Client error '404 Not Found' for url 'https://glama.ai/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://glama.ai/.well-known/mcp/server-card.json"
    }
  },
  "remote_url": "https://glama.ai/mcp/servers/mgrr2j1cxk",
  "server_card_payload": null,
  "server_identifier": "okareo-ai/okareo-mcp"
}
Known versions
  • No versions recorded.
Validation history
7 day score delta
n/a
30 day score delta
n/a
Recent healthy ratio
0%
Freshness
5.2h
TimestampStatusScoreLatencyTools
Aug 05, 2026 04:02:42 PM UTC Failing 8.5 271.2 ms 0
Aug 05, 2026 03:27:14 PM UTC Failing 8.5 425.7 ms 0
Aug 05, 2026 08:00:04 AM UTC Failing 13.3 995.8 ms 0
Aug 04, 2026 11:15:11 PM UTC Failing 13.3 1425.7 ms 0
Aug 04, 2026 02:50:31 PM UTC Failing 17.1 1228.2 ms 0
Aug 04, 2026 07:23:21 AM UTC Failing 17.0 1328.8 ms 0
Aug 03, 2026 08:50:10 PM UTC Failing 17.0 1199.6 ms 0
Aug 03, 2026 02:35:38 AM UTC Failing 17.0 986.4 ms 0
Validation timeline
ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
Aug 05, 2026 04:02:42 PM UTC Failing 8.5 unknown unknown 0 0 none
Aug 05, 2026 03:27:14 PM UTC Failing 8.5 unknown unknown 0 0 none
Aug 05, 2026 08:00:04 AM UTC Failing 13.3 unknown unknown 0 0 none
Aug 04, 2026 11:15:11 PM UTC Failing 13.3 unknown unknown 0 0 none
Aug 04, 2026 02:50:31 PM UTC Failing 17.1 unknown unknown 0 0 none
Aug 04, 2026 07:23:21 AM UTC Failing 17.0 unknown unknown 0 0 none
Aug 03, 2026 08:50:10 PM UTC Failing 17.0 unknown unknown 0 0 none
Aug 03, 2026 02:35:38 AM UTC Failing 17.0 unknown unknown 0 0 none
Aug 02, 2026 07:14:02 PM UTC Failing 16.9 unknown unknown 0 0 none
Aug 02, 2026 12:25:08 PM UTC Failing 16.9 unknown unknown 0 0 none
Recent validation runs
Recent validation runs for this MCP server
StartedStatusSummaryLatencyChecks
Aug 05, 2026 04:02:42 PM UTC Completed Failing 271.2 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, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Aug 05, 2026 03:27:14 PM UTC Completed Failing 425.7 ms
Aug 05, 2026 08:00:03 AM UTC Completed Failing 995.8 ms
Aug 04, 2026 11:15:10 PM UTC Completed Failing 1425.7 ms
Aug 04, 2026 02:50:30 PM UTC Completed Failing 1228.2 ms
Aug 04, 2026 07:23:20 AM UTC Completed Failing 1328.8 ms
Aug 03, 2026 08:50:09 PM UTC Completed Failing 1199.6 ms
Aug 03, 2026 02:35:37 AM UTC Completed Failing 986.4 ms
Aug 02, 2026 07:14:01 PM UTC Completed Failing 914.0 ms
Aug 02, 2026 12:25:07 PM UTC Completed Failing 482.9 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 05, 2026 11:01:55 AM UTC Score corrected (post-1.0.503 remediation, R1 zero-anchoring) Prior: 13.28. Corrected: 7.62.
Aug 05, 2026 04:02:42 PM UTC Latest validation: failing Score 14.2 with status failing.
Aug 05, 2026 04:02:42 PM UTC Score changed Score delta +0.0 versus the previous run.
Aug 05, 2026 03:27:14 PM UTC Score changed Score delta -4.8 versus the previous run.
Aug 05, 2026 08:00:04 AM UTC Score changed Score delta +0.0 versus the previous run.
Capabilities
Use-case taxonomy
other
Benchmark tasks
Benchmark taskStatusEvidence
Discover tools Likely to fail
  • initialize • Error
  • tools_list • Skipped
Read-only fetch flow Likely to fail
  • resource_read • Missing
  • read_only_tool_surface • Missing
OAuth-required connect Degraded
  • oauth_protected_resource • Error
  • step_up_auth_probe • Missing
Safe write flow with confirmation Passes
  • action_safety_probe • OK
Utility coverage
Probe status
Missing
Completions
not detected
Completion probe target: none
Pagination
not detected
No nextCursor evidence.
Tasks
Skipped
Advertised: no
Transport compliance drilldown
Probe status
Skipped
Transport
unknown
Session header
no
Protocol header
no
Bad protocol response
n/a
DELETE teardown
n/a
Expired session retry
n/a
Last-Event-ID visible
no

Issues: none

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.02
Summary changed
no
Tool delta
0
Prompt delta
0
Auth mode changed
no
Write surface expanded
no
Protocol regressed
no
Registry drift changed
no

Regressed checks: connector_publishability_probe, determinism_probe, initialize, oauth_protected_resource, prompts_list, resources_list, server_card, session_resume_probe, tools_list, transport_compliance_probe

Improved checks: action_safety_probe, probe_noise_resilience, provenance_divergence_probe

ComponentPreviousLatestDelta
trust_confidence_score1.61.70.1
installability_score3.523.5-0.02
Registry & provenance divergence
Probe status
OK
Direct official match
no
Drift fields
none
FieldRegistryLive server card
Titlen/an/a
Versionn/an/a
Homepagen/an/a
Active alerts
  • Latest validation is failing (critical)
    Core MCP flows did not validate successfully on the latest run.
  • Initialize flow regressed (critical)
    A client-visible initialize behavior changed for the worse.
  • tools/list regressed (critical)
    Tool discovery became less reliable on the latest run.
Aliases & registry graph
IdentifierSourceCanonicalScore
okareo-ai/okareo-mcp glama_registry yes 8.5
Alias consolidation
Canonical identifier
okareo-ai/okareo-mcp
Duplicate aliases
0
Registry sources
glama_registry
Remote URLs
Homepages
Source disagreements
FieldWhat differsObserved values
No source disagreements detected.

Fix it

Why this score?
Access & Protocol
11.5/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
6/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
15.87/24
Operational stability, consistency, and trustworthiness over time.
Discovery & Governance
18.75/28
How well the server is documented, listed, and governed in public registries.
Adoption & Market
2.85/8
Adoption clues and public evidence that the server is intended for external use.
Algorithmic score breakdown
Auth Operability
0/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
3/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
2/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
1.7/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
1.7/4
Confidence-adjusted reliability score that penalizes low evidence volume.
Abuse/Noise Resilience
2.5/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
2/4
How completely resources and resource templates describe URIs, types, and usage shape.
Discovery Metadata
4/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
3.5/4
How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.
Session Semantics
0/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
0/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
3.2/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
3/4
Confidence that recent validations are current enough and dense enough to trust operationally.
Transport Fidelity
3.5/4
Whether declared transport metadata matches the observed endpoint behavior and response formats.
Spec Recency
0/4
How close the server’s claimed MCP protocol version is to the latest known public revision.
Session Resume
2/4
Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.
Step-Up Auth
0/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
0/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
0/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
0.8/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
0/4
Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.
Action Safety
3/4
Risk-weighted view of destructive, exec, egress, and confirmation semantics across the tool surface.
Official Registry Presence
3/4
Whether the server appears directly or indirectly in the official MCP registry.
Provenance Divergence
4/4
How closely official registry metadata, the live server card, and public repo/package signals agree with each other.
Safety Transparency
2/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.5/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
1.5/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
1.5/4
Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.
Data Exfiltration Resilience
1/4
Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.
Least Privilege Scope
1.5/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
1.5/4
Assesses secret-bearing tools, token leakage risk, and whether the public surface avoids obvious secret exposure.
Supply Chain Signal
0.5/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 Make initialize deterministic and client-friendly If initialize fails or requires undocumented auth, many MCP clients cannot connect. Allow initialize to succeed consistently, or return a deterministic auth-required response with clear metadata.
Playbook
  • Allow `initialize` to succeed unauthenticated when possible.
  • If auth is required, return a deterministic auth-required response and matching metadata.
  • Retest against `https://glama.ai/mcp/servers/mgrr2j1cxk` from a clean client session.
Critical Respond to initialize flow regressed A client-visible initialize behavior changed for the worse. Compare initialize responses between the latest two runs and restore the previous stable behavior.
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 Associate roots, sampling, and elicitation with active client requests Modern MCP guidance expects roots, sampling, and elicitation traffic to be tied to an active client request instead of arriving unsolicited on idle sessions. Only send roots/list, sampling/createMessage, or elicitation/create requests while handling an active client-initiated request, never on idle sessions.
Playbook
  • Only send `roots/list`, `sampling/createMessage`, or `elicitation/create` requests while handling an active client-initiated request.
  • Avoid emitting these requests on idle or newly-initialized sessions with no pending client request.
  • Revalidate and confirm `request_association_probe` no longer returns `missing` or `warning`.
High Expose /.well-known/oauth-protected-resource Without a protected-resource document, OAuth clients cannot discover auth requirements reliably. Serve /.well-known/oauth-protected-resource and point it at your authorization server metadata.
Playbook
  • Serve `/.well-known/oauth-protected-resource` from the same host as the MCP endpoint.
  • Point it at the authorization server metadata URL.
  • Confirm clients receive consistent auth hints before tool execution.
High Keep connector refreshes backward compatible Managed connector clients freeze tool snapshots, so removed tools, new required args, and breaking output changes can break published integrations after refresh. Avoid removing tools, adding new required arguments, or changing outputSchema for tools already published to connector directories without a version bump.
Playbook
  • Avoid removing tools or adding new required arguments to existing tools without a major version bump.
  • Avoid breaking changes to `outputSchema` for tools already published to connector directories.
  • This check reads `no_historical_snapshot` on a server's first validation run -- that is expected, not itself a defect, and resolves after a second run.
High Publish OAuth authorization-server metadata Clients need authorization-server metadata to discover issuer, endpoints, and DCR support. Publish /.well-known/oauth-authorization-server from your issuer and include registration_endpoint when supported.
Playbook
  • Publish `/.well-known/oauth-authorization-server` from the issuer.
  • Add `registration_endpoint` if DCR is supported.
  • Verify issuer, authorization, token, and jwks metadata are all reachable.
High Publish a complete server card Missing or incomplete server-card metadata weakens discovery, documentation, and trust signals. Serve /.well-known/mcp/server-card.json and include tools, prompts/resources, homepage, and support links.
Playbook
  • Publish `/.well-known/mcp/server-card.json`.
  • Include homepage, repository, support, tools, prompts/resources, and auth metadata.
  • Revalidate the server after publishing the card.
High Stop asking users to paste secrets directly Public MCP servers should prefer OAuth or browser-based auth guidance over in-band secret collection.
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 Document minimal scopes and return cleaner auth challenges Modern clients expect granular scopes and step-up auth signals such as WWW-Authenticate scope hints. Return granular scopes and WWW-Authenticate challenge hints instead of forcing overly broad auth upfront.
Playbook
  • Advertise the narrowest viable scopes in OAuth metadata.
  • Return `WWW-Authenticate` challenges with scope or insufficient-scope hints when additional consent is needed.
  • Revalidate with both public discovery and auth-required flows.
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 Access & Protocol score Connectivity, auth, and transport expectations for common clients. Tighten auth discovery, session behavior, and transport metadata until remote clients can connect without guesswork.
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 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 Reduce tool-surface churn Frequent add/remove or output-shape drift makes published connectors and cached tool snapshots brittle. Keep tool names, required arguments, and output schemas stable between deploys, and publish a changelog entry when they must change.
Playbook
  • Avoid changing tool names, required arguments, or output schemas between deploys unless the change is intentional.
  • Publish a changelog entry when the tool surface changes so cached or frozen client snapshots can be reconciled.
  • This check compares against the previous run, so it needs a second validation before it can report a stable baseline.
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.
Medium Support resumable HTTP sessions cleanly Modern MCP clients increasingly expect resumable session behavior on streamable HTTP transports. Persist session state keyed by Mcp-Session-Id and honor Last-Event-ID on GET reconnects so clients can resume a dropped Streamable HTTP session.
Playbook
  • Persist session state keyed by `Mcp-Session-Id` so a client can reconnect after a dropped connection.
  • Honor `Last-Event-ID` on GET reconnects to replay missed SSE events instead of erroring.
  • Revalidate and confirm `session_resume_probe` no longer returns `warning`.
Low Expose modern utility surfaces like completions, pagination, or tasks Utility coverage improves interoperability with larger clients and long-lived agent workflows. Expose completions, pagination, and task metadata where supported so larger clients can plan and resume work safely.
Playbook
  • Advertise `completions`, pagination cursors, and `tasks` only when they are actually supported.
  • Return `nextCursor` on large list operations when pagination is available.
  • Document task support and whether it requires step-up auth.
Low Publish newer MCP capability signals Roots, sampling, elicitation, structured outputs, and related metadata improve client understanding and ranking. Advertise only the advanced capabilities (roots, sampling, elicitation) you have actually implemented end to end in the initialize capabilities object.
Playbook
  • Add the capabilities you actually support (`roots`, `sampling`, `elicitation`) to the `capabilities` object returned from `initialize`.
  • Only advertise a capability once the corresponding request/response flow is implemented end to end.
  • Revalidate and confirm `advanced_capabilities_probe` reflects the updated capability set.
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
Utility Coverage 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
Step Up Auth 0/4 -4.0
Spec Recency 0/4 -4.0
Session Semantics 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
Compatibility profiles
OpenAI Connectors
33.3
blocked
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Initialize must be reachable.; tools/list must succeed.; Transport compliance should be in good shape.; OAuth interoperability should be strong.
Connector URL: https://glama.ai/mcp/servers/mgrr2j1cxk
# No OAuth metadata detected.
# Server: okareo-ai/okareo-mcp
Claude Desktop
33.3
blocked
Initialize must succeed or cleanly request auth.; tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool.
{
  "mcpServers": {
    "okareo-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://glama.ai/mcp/servers/mgrr2j1cxk"]
    }
  }
}
Smithery
40.0
blocked
Tool discovery must succeed.; Initialize should work before execution.; Machine-readable failure semantics should be present.
smithery mcp add "https://glama.ai/mcp/servers/mgrr2j1cxk"
Generic Streamable HTTP
50.0
blocked
Initialize must succeed.; tools/list must succeed.; Session behavior should be predictable.
curl -sS https://glama.ai/mcp/servers/mgrr2j1cxk -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
Freshly Validated Write-Safe No Critical Risk
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
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://glama.ai/mcp/servers/mgrr2j1cxk
# No OAuth metadata detected.
# Server: okareo-ai/okareo-mcp
Claude Desktop
{
  "mcpServers": {
    "okareo-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://glama.ai/mcp/servers/mgrr2j1cxk"]
    }
  }
}
Smithery
smithery mcp add "https://glama.ai/mcp/servers/mgrr2j1cxk"
Generic Http
curl -sS https://glama.ai/mcp/servers/mgrr2j1cxk -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://glama.ai/mcp/servers/mgrr2j1cxk. 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 okareo-ai/okareo-mcp.
Direct machine links
JSON report • Compare this server • Verify MCP API