← Back to search
Search • TrustOps • Plans • Shortlists • Rankings • Compare • ChatGPT compatible • Claude compatible • Healthcare • Digests • RSS • RSS XML • Backfill • MCP API
github-kooshapari/phenomcp

KooshaPari/PhenoMCP

Phenotype-org MCP server

JSON report • History API • Manage this server • Global feed
EXECUTIVE VERDICT

Executive verdict

Production trust decision: Block for production
Reason: failing live status + score below evaluation threshold
Next action: revalidate, add safeguards, export policy
Status
Failing
Score
47.9
Transport
streamable-http
Tools
0

Current trust snapshot

Snapshot ID
trustsnap_230efec1d71cd534
Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.
Snapshot generated
May 13, 2026 05:58:21 PM UTC
All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.
Last validated
May 13, 2026 05:50:03 PM UTC
Age: 0.14h • freshness band: Verified in last 24h • display score: 47.93
Production trust decision
Block for production
failing live status + score below evaluation threshold
Readiness class
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.
SERVER OWNER FUNNEL

Own this MCP?

Claim ownership, prove control with a GitHub, DNS, or HTTP token challenge, revalidate now, publish a badge, and configure monitoring.

1. Claim
unclaimed
Start owner claim with GitHub, DNS, or HTTP challenge instructions.
2. Revalidate
POST /v1/servers/github-kooshapari/phenomcp/revalidate
Verified owners get priority queueing after proof succeeds.
3. Badge
Verified by MCP Verify badge
Verified by MCP Verify - score 47.9 - last checked May 13, 2026
4. Monitor
Pick plan + alerts
Continuous Verify plan is self-serve: choose a tier, configure watches, add authenticated validation, trigger revalidation, and use the badge.
Badge embed 
[![Verified by MCP Verify](https://verify.sentinelsignal.io/badge/github-kooshapari/phenomcp.svg)](https://verify.sentinelsignal.io/servers/github-kooshapari/phenomcp)

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.

Freshness band
Verified in last 24h
Policy SLA: 168.0h • confidence-weighted score: 34.7 • stale score suppressed: ✕
Policy exports
Export policy
Formats: json, rego, yaml, github_action, gateway_config, client_report
Runtime routing
/v1/route
Returns allowed tools, blocked tools, approval requirement, and reason.
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

Production readiness class

Production readiness class
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.
Critical alerts
1
Production verdicts degrade quickly when critical alerts are active.

Evidence confidence

Confidence score
72.5
Based on 6 recent validations, 26 captured checks, and validation age of 0.1 hours.
Live checks captured
26
More direct checks increase trust in the current verdict.
Validation age
0.1h
Lower age means fresher evidence.

Recommended for

No recommendation profile is available yet.

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: medium (72.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initialize • Error
  • tools_list • Error
  • transport_compliance_probe • Error
  • 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: medium (72.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initialize • Error
  • tools_list • Error
  • transport_compliance_probe • Error
Write-action publishing
Publishing allowed
Current write surface is bounded enough for cautious review with production policy controls.
Confidence: medium (72.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: medium (72.5)
Evidence provenance
Winner: history
Supporting sources: history, live_validation
Disagreements: none
  • tool_snapshot_probe • Missing
  • connector_replay_probe • Missing

Why compatibility is limited by client

ChatGPT custom connector
Blocked
Remediation checklist
  • No explicit blockers recorded.
Claude remote MCP
Blocked
Remediation checklist
  • No explicit blockers recorded.
Write-safe publishing
Ready
Remediation checklist
  • No explicit blockers recorded.

Verdict traces

Production verdict
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.
Confidence: medium (72.5)
Winning source: live_validation
Triggering alerts
  • server_failing • critical • Latest validation is failing
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

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

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
May 13, 2026 05:50:03 PM UTC Latest validation: failing Score 47.9 with status failing.
May 13, 2026 05:50:03 PM UTC Score changed Score delta +1.4 versus the previous run.
May 13, 2026 09:48:38 AM UTC Score changed Score delta +0.4 versus the previous run.
May 13, 2026 01:47:33 AM UTC Score changed Score delta +0.2 versus the previous run.

Capabilities

Use-case taxonomy
development

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.

Why this score?

Access & Protocol
18.93/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
14.17/56
How well the tool/resource interface communicates and behaves under automation.
Security Posture
26/36
How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.
Reliability & Trust
11.78/24
Operational stability, consistency, and trustworthiness over time.
Discovery & Governance
19.45/28
How well the server is documented, listed, and governed in public registries.
Adoption & Market
3.62/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.7/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
1.7/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
0.6/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
3/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.9/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.5/4
Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.
Maintenance Signal
3/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
2/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
3/4
Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.
Step-Up Auth
3/4
Whether OAuth metadata and WWW-Authenticate challenges support granular, incremental consent instead of broad upfront scopes.
Transport Compliance
0/4
Checks session headers, protocol-version enforcement, session teardown, and expired-session behavior.
Utility Coverage
2/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
2/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
1.6/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
3/4
Whether a previously published frozen connector snapshot would remain backward compatible after the latest tool refresh.
Request Association
3/4
Whether roots, sampling, and elicitation appear tied to active client requests instead of arriving unsolicited on idle sessions.
Interactive Flow Safety
3/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
4/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
3/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
3/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
4/4
Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.
Data Exfiltration Resilience
3/4
Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.
Least Privilege Scope
2/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
3/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.

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://phenomcp.phenotype.space
# No OAuth metadata detected.
# Server: github-kooshapari/phenomcp
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": {
    "phenomcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://phenomcp.phenotype.space"]
    }
  }
}
Smithery
40.0
blocked
Tool discovery must succeed.; Initialize should work before execution.; Machine-readable failure semantics should be present.
smithery mcp add "https://phenomcp.phenotype.space"
Generic Streamable HTTP
50.0
blocked
Initialize must succeed.; tools/list must succeed.; Session behavior should be predictable.
curl -sS https://phenomcp.phenotype.space -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"}}}'

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://phenomcp.phenotype.space` from a clean client session.
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.
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. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
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. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
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. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Adopt a current MCP protocol revision Older protocol revisions reduce compatibility with newer clients and registry programs. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Close connector-publishing gaps Connector catalogs care about protocol recency, session behavior, auth clarity, and tool-surface stability. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
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
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
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.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
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.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Reduce tool-surface churn Frequent add/remove or output-shape drift makes published connectors and cached tool snapshots brittle. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
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. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
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. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Low Publish or reconcile the server in the official MCP registry Official registry presence improves discovery confidence and cross-source consistency. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.

Point loss breakdown

ComponentCurrentPoints missing
Transport Compliance 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
Session Semantics 0/4 -4.0
Schema Completeness 0/4 -4.0
Result Shape Stability 0/4 -4.0
OAUTH Interop 0/4 -4.0
Input Sanitization Safety 0/4 -4.0
Auth Operability 0/4 -4.0
SLO Health 0/4 -4.0

Validation diff

Score delta
1.39
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: none

Improved checks: none

ComponentPreviousLatestDelta
installability_score2.03.931.93
freshness_confidence_score2.53.00.5
maintenance_signal_score2.752.950.2
trust_confidence_score0.50.60.1
slo_health_score0.010.01

Tool snapshot diff & changelog

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

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.

Transport compliance drilldown

Probe status
Error
Transport
streamable-http
Session header
no
Protocol header
no
Bad protocol response
525
DELETE teardown
n/a
Expired session retry
n/a
Last-Event-ID visible
no

Issues: missing_protocol_header, bad_protocol_not_rejected

Request association

Status
Missing
Advertised capabilities
none
Observed idle methods
none
Violating methods
none
Probe HTTP status
n/a
Issues
none

Utility coverage

Probe status
Missing
Completions
not detected
Completion probe target: none
Pagination
not detected
No nextCursor evidence.
Tasks
Missing
Advertised: no

Benchmark tasks

Benchmark taskStatusEvidence
Discover tools Likely to fail
  • initialize • Error
  • tools_list • Error
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

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

Aliases & registry graph

IdentifierSourceCanonicalScore
github-kooshapari/phenomcp github_topic_registry yes 47.93

Alias consolidation

Canonical identifier
github-kooshapari/phenomcp
Duplicate aliases
0
Registry sources
github_topic_registry
Remote URLs
https://phenomcp.phenotype.space
Homepages
https://github.com/KooshaPari/PhenoMCP
Source disagreements
FieldWhat differsObserved values
No source disagreements detected.

Install snippets

Openai Connectors
Connector URL: https://phenomcp.phenotype.space
# No OAuth metadata detected.
# Server: github-kooshapari/phenomcp
Claude Desktop
{
  "mcpServers": {
    "phenomcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://phenomcp.phenotype.space"]
    }
  }
}
Smithery
smithery mcp add "https://phenomcp.phenotype.space"
Generic Http
curl -sS https://phenomcp.phenotype.space -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://phenomcp.phenotype.space. 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-kooshapari/phenomcp.
Direct machine links
JSON report • Compare this server • Verify MCP API

Claims & monitoring

Server ownership

No verified maintainer claim recorded.

Watch subscriptions
0
Teams: none

Alert routing

Active watches
0
Generic webhooks
0
Slack routes
0
Teams routes
0
Email routes
0
WatchTeamChannelsMinimum severity
No active watch destinations.

Maintainer analytics

Validation Run Count
6
Average Latency Ms
5348.26
Healthy Run Ratio Recent
0.0
Registry Presence Count
1
Active Alert Count
1
Watcher Count
0
Verified Claim
False
Taxonomy Tags
development
Score Trend
47.93, 46.54, 46.13, 45.91, 46.28, 45.13
Remediation Count
23
High Risk Tool Count
0
Destructive Tool Count
0
Exec Tool Count
0

Maintainer response quality

Score
33.33
Verified claim
✕
Support contact
✓
Changelog present
✕
Incident notes present
✕
Tool changes documented
✓
Annotation history
✕
Annotation count
0

Maintainer annotations

No maintainer annotations have been recorded yet.

Maintainer rebuttals & expected behavior

No maintainer rebuttals or expected-behavior overrides are recorded yet.

Latest validation evidence

Latest summary
Failing
Validation profile
remote_mcp
Started
May 13, 2026 05:50:00 PM UTC
Latency
3383.0 ms

Failures

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, transport compliance, +3 more.
connector_replay_probe Missing n/a No connector replay evidence recorded.
determinism_probe Missing n/a tools list unavailable
initialize Error 380.4 ms Server error '525 <none>' for url 'https://phenomcp.phenotype.space' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/525
interactive_flow_probe Missing n/a Check completed
oauth_authorization_server Missing n/a no authorization server
oauth_protected_resource Error 360.9 ms Server error '525 <none>' for url 'https://phenomcp.phenotype.space/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/525
official_registry_probe Warning n/a Check completed
openid_configuration Missing n/a no authorization server
probe_noise_resilience OK 338.3 ms Fetched https://phenomcp.phenotype.space/robots.txt
prompt_get Missing n/a not advertised
prompts_list Missing 340.3 ms Server error '525 <none>' for url 'https://phenomcp.phenotype.space' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/525
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 Missing 391.2 ms Server error '525 <none>' for url 'https://phenomcp.phenotype.space' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/525
server_card Error 967.2 ms Server error '525 <none>' for url 'https://phenomcp.phenotype.space/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/525
session_resume_probe Missing n/a no session id
step_up_auth_probe Missing n/a No OAuth or incremental-scope signals detected.
tool_snapshot_probe Missing n/a no tools
tools_list Error 136.9 ms Server error '525 <none>' for url 'https://phenomcp.phenotype.space' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/525
transport_compliance_probe Error 117.9 ms Issues: missing protocol header, bad protocol not rejected (bad protocol=525).
utility_coverage_probe Missing 336.0 ms No completions evidence; no pagination evidence; tasks missing.

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",
          "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": true,
          "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": "tools_list_unavailable"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "initialize": {
      "details": {
        "error": "Server error '525 <none>' for url 'https://phenomcp.phenotype.space'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/525",
        "headers": {
          "content-type": "application/json; charset=utf-8"
        },
        "http_status": 525,
        "payload": {},
        "url": "https://phenomcp.phenotype.space"
      },
      "latency_ms": 380.37,
      "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": "Server error '525 <none>' for url 'https://phenomcp.phenotype.space/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/525",
        "url": "https://phenomcp.phenotype.space/.well-known/oauth-protected-resource"
      },
      "latency_ms": 360.86,
      "status": "error"
    },
    "official_registry_probe": {
      "details": {
        "direct_match": false,
        "official_identifiers": [
          "io.github.YuzuKyouma/ponzu",
          "io.github.M-China-Official/mcd-mcp",
          "eu.ansvar/peruvian-law-mcp",
          "io.github.olgasafonova/miro-mcp-server",
          "io.getunleash/unleash-mcp",
          "com.gitkraken/gk-cli",
          "io.github.bajoski34/mcp-flutterwave",
          "ai.smithery/arjunkmrm-ts-test-2",
          "io.github.levelsofself/self-awareness-game",
          "io.github.kirbah/mcp-youtube"
        ],
        "official_peer_count": 10,
        "registry_source": "github_topic_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"
        },
        "http_status": 200,
        "url": "https://phenomcp.phenotype.space/robots.txt"
      },
      "latency_ms": 338.32,
      "status": "ok"
    },
    "prompt_get": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "prompts_list": {
      "details": {
        "error": "Server error '525 <none>' for url 'https://phenomcp.phenotype.space'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/525",
        "headers": {
          "content-type": "application/json; charset=utf-8"
        },
        "http_status": 525,
        "payload": {},
        "reason": "not_advertised",
        "url": "https://phenomcp.phenotype.space"
      },
      "latency_ms": 340.3,
      "status": "missing"
    },
    "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": {
        "error": "Server error '525 <none>' for url 'https://phenomcp.phenotype.space'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/525",
        "headers": {
          "content-type": "application/json; charset=utf-8"
        },
        "http_status": 525,
        "payload": {},
        "reason": "not_advertised",
        "url": "https://phenomcp.phenotype.space"
      },
      "latency_ms": 391.18,
      "status": "missing"
    },
    "server_card": {
      "details": {
        "error": "Server error '525 <none>' for url 'https://phenomcp.phenotype.space/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/525",
        "url": "https://phenomcp.phenotype.space/.well-known/mcp/server-card.json"
      },
      "latency_ms": 967.2,
      "status": "error"
    },
    "session_resume_probe": {
      "details": {
        "protocol_version": null,
        "reason": "no_session_id",
        "resume_expected": false,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "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": {
        "error": "Server error '525 <none>' for url 'https://phenomcp.phenotype.space'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/525",
        "headers": {
          "content-type": "application/json; charset=utf-8"
        },
        "http_status": 525,
        "payload": {},
        "url": "https://phenomcp.phenotype.space"
      },
      "latency_ms": 136.87,
      "status": "error"
    },
    "transport_compliance_probe": {
      "details": {
        "bad_protocol_error": null,
        "bad_protocol_headers": {
          "content-type": "application/json; charset=utf-8"
        },
        "bad_protocol_payload": {
          "cloudflare_error": true,
          "detail": "The SSL/TLS handshake between Cloudflare and the origin server failed. The origin's SSL configuration is not compatible with Cloudflare, possibly due to missing shared cipher suites or an unsupported TLS version.",
          "error_category": "ssl",
          "error_code": 525,
          "error_name": "ssl_handshake_failed",
          "footer": "This error was generated by Cloudflare on behalf of the website owner.",
          "instance": "9fb380d70be9ef62",
          "owner_action_required": true,
          "ray_id": "9fb380d70be9ef62",
          "retryable": false,
          "status": 525,
          "timestamp": "2026-05-13T17:50:03Z",
          "title": "Error 525: SSL handshake failed",
          "type": "https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525/",
          "what_you_should_do": "**Do not retry.** Retrying will not resolve this error. The website operator must fix the origin SSL/TLS configuration to use cipher suites and TLS versions compatible with Cloudflare.",
          "zone": "phenomcp.phenotype.space"
        },
        "bad_protocol_status_code": 525,
        "delete_error": null,
        "delete_status_code": null,
        "expired_session_error": null,
        "expired_session_status_code": null,
        "issues": [
          "missing_protocol_header",
          "bad_protocol_not_rejected"
        ],
        "last_event_id_visible": false,
        "protocol_header_present": false,
        "requested_protocol_version": "2025-03-26",
        "session_id_present": false,
        "transport": "streamable-http"
      },
      "latency_ms": 117.91,
      "status": "error"
    },
    "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": 525,
          "probe_status": "missing"
        }
      },
      "latency_ms": 335.96,
      "status": "missing"
    }
  },
  "failures": {
    "initialize": {
      "error": "Server error '525 <none>' for url 'https://phenomcp.phenotype.space'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/525",
      "headers": {
        "content-type": "application/json; charset=utf-8"
      },
      "http_status": 525,
      "payload": {},
      "url": "https://phenomcp.phenotype.space"
    },
    "oauth_authorization_server": {
      "reason": "no_authorization_server"
    },
    "oauth_protected_resource": {
      "error": "Server error '525 <none>' for url 'https://phenomcp.phenotype.space/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/525",
      "url": "https://phenomcp.phenotype.space/.well-known/oauth-protected-resource"
    },
    "openid_configuration": {
      "reason": "no_authorization_server"
    },
    "server_card": {
      "error": "Server error '525 <none>' for url 'https://phenomcp.phenotype.space/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/525",
      "url": "https://phenomcp.phenotype.space/.well-known/mcp/server-card.json"
    },
    "tools_list": {
      "error": "Server error '525 <none>' for url 'https://phenomcp.phenotype.space'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/525",
      "headers": {
        "content-type": "application/json; charset=utf-8"
      },
      "http_status": 525,
      "payload": {},
      "url": "https://phenomcp.phenotype.space"
    },
    "transport_compliance_probe": {
      "bad_protocol_error": null,
      "bad_protocol_headers": {
        "content-type": "application/json; charset=utf-8"
      },
      "bad_protocol_payload": {
        "cloudflare_error": true,
        "detail": "The SSL/TLS handshake between Cloudflare and the origin server failed. The origin's SSL configuration is not compatible with Cloudflare, possibly due to missing shared cipher suites or an unsupported TLS version.",
        "error_category": "ssl",
        "error_code": 525,
        "error_name": "ssl_handshake_failed",
        "footer": "This error was generated by Cloudflare on behalf of the website owner.",
        "instance": "9fb380d70be9ef62",
        "owner_action_required": true,
        "ray_id": "9fb380d70be9ef62",
        "retryable": false,
        "status": 525,
        "timestamp": "2026-05-13T17:50:03Z",
        "title": "Error 525: SSL handshake failed",
        "type": "https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525/",
        "what_you_should_do": "**Do not retry.** Retrying will not resolve this error. The website operator must fix the origin SSL/TLS configuration to use cipher suites and TLS versions compatible with Cloudflare.",
        "zone": "phenomcp.phenotype.space"
      },
      "bad_protocol_status_code": 525,
      "delete_error": null,
      "delete_status_code": null,
      "expired_session_error": null,
      "expired_session_status_code": null,
      "issues": [
        "missing_protocol_header",
        "bad_protocol_not_rejected"
      ],
      "last_event_id_visible": false,
      "protocol_header_present": false,
      "requested_protocol_version": "2025-03-26",
      "session_id_present": false,
      "transport": "streamable-http"
    }
  },
  "remote_url": "https://phenomcp.phenotype.space",
  "server_card_payload": null,
  "server_identifier": "github-kooshapari/phenomcp"
}

Known versions

Validation history

7 day score delta
n/a
30 day score delta
n/a
Recent healthy ratio
0%
Freshness
0.1h
TimestampStatusScoreLatencyTools
May 13, 2026 05:50:03 PM UTC Failing 47.9 3383.0 ms 0
May 13, 2026 09:48:38 AM UTC Failing 46.5 6510.9 ms 0
May 13, 2026 01:47:33 AM UTC Failing 46.1 4076.1 ms 0
May 12, 2026 05:45:16 PM UTC Failing 45.9 12452.9 ms 0
May 12, 2026 09:43:45 AM UTC Failing 46.3 2945.9 ms 0
May 12, 2026 01:42:50 AM UTC Failing 45.1 2720.9 ms 0

Validation timeline

ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
May 13, 2026 05:50:03 PM UTC Failing 47.9 unknown unknown 0 0 none
May 13, 2026 09:48:38 AM UTC Failing 46.5 unknown unknown 0 0 none
May 13, 2026 01:47:33 AM UTC Failing 46.1 unknown unknown 0 0 none
May 12, 2026 05:45:16 PM UTC Failing 45.9 unknown unknown 0 0 none
May 12, 2026 09:43:45 AM UTC Failing 46.3 unknown unknown 0 0 none
May 12, 2026 01:42:50 AM UTC Failing 45.1 unknown unknown 0 0 none

Recent validation runs

StartedStatusSummaryLatencyChecks
May 13, 2026 05:50:00 PM UTC Completed Failing 3383.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, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 13, 2026 09:48:32 AM UTC Completed Failing 6510.9 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
May 13, 2026 01:47:29 AM UTC Completed Failing 4076.1 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
May 12, 2026 05:45:04 PM UTC Completed Failing 12452.9 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
May 12, 2026 09:43:42 AM UTC Completed Failing 2945.9 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
May 12, 2026 01:42:47 AM UTC Completed Failing 2720.9 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