← Back to search

Search • Rankings • TrustOps • Docs • Pricing • Claim/Manage

davidmosiah/delx-mcp-server

Delx MCP Server

MCP stdio bridge for the Delx Protocol: continuity, witness, recovery, ontology and passport tools.

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

DECISION SUMMARY

Block For Production

Score

n/a

Rank suppressed while production readiness shows a blocking verdict.

Confidence

Medium

Based on evidence completeness, recency, and validation density.

Evidence age

3.7h old

Freshness: fresh. Snapshot trustsnap_e4562f29bb575960.

Top risk drivers

Utility Coverage
Transport Compliance
Tool Surface Design

Recommended actions

Make tools/list succeed unauthenticated when possible, or document the auth flow in the server card.
Fix the failing checks first, then revalidate to confirm the recovery path.
Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.

Next action

revalidate, add safeguards, export policy

unauthenticated behavior not proven + failing live status

Compare alternatives Export policy Open report JSON Dispute this assessment

Observed Attention

Low observed attention

AI discovery detected. This MCP server has recently appeared in AI-assisted discovery or evaluation traffic on Verify.

Search crawler activity
profile / ledger inspection

Bucketed signal based on recent segmented Verify telemetry. Crawler and evaluator activity is not treated as confirmed human demand.

Claim this profile to control the metadata agents are reading and publish verified ownership, security contact, policy metadata, badge status, and Intelligence API fields.

Risks Compatibility Evidence Fix it Governance History Technical details

Status

Failing

Score

n/a

Transport

streamable-http

Tools

754

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.

Risks

Security posture

Tools analyzed

High-risk tools

Destructive tools

Exec tools

Egress tools

Secret tools

Bulk-access tools

Risk distribution

none

Tool capability & risk inventory

No tool inventory available from the latest validation run.

Write-action governance

Governance status

Not_Assessed

Safe to publish

Auth boundary

oauth_or_auth_required

Blast radius

Low

High-risk tools

Confirmation signals

none

Safeguard count

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

Tool	Risk	Flags	Safeguards
High-risk tool assessment unavailable -- no tools were analyzed.

Action-controls diff

Need at least two validation runs before diffing action controls.

Critical alerts

High/critical-severity alerts

Production verdicts degrade quickly when high or critical-severity alerts are active.

Compatibility

Client compatibility verdicts

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

Client compatibility: ChatGPT

Partially client-compatible

Dynamic client registration materially improves connector setup.; tools/list must succeed.; Transport compliance failed or did not complete successfully.; The tool surface is not limited to search/fetch-style read tools.; Not yet safe for company-knowledge use: requires a search/fetch-only surface with no export, bulk, mutating, or high-blast-radius exposure.; Not yet safe for the Messages API remote MCP path: requires OAuth, a compatible connector profile, and no pending connector-refresh risk.

Confidence: medium (65.0)

Evidence provenance

Winner: live_validation

Supporting sources: live_validation, history, server_card

Disagreements: none

initialize • OK
tools_list • Error
transport_compliance_probe • Error
step_up_auth_probe • OK
connector_replay_probe • Missing — Frozen tool snapshots must survive refresh.
request_association_probe • Missing — Roots, sampling, and elicitation should stay request-scoped.

Client compatibility: Claude

Partially client-compatible

tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; The tool surface is not limited to search/fetch-style read tools.; Not yet safe for company-knowledge use: requires a search/fetch-only surface with no export, bulk, mutating, or high-blast-radius exposure.; Not yet safe for the Messages API remote MCP path: requires OAuth, a compatible connector profile, and no pending connector-refresh risk.; Transport compliance failed or did not complete successfully.

Confidence: medium (65.0)

Evidence provenance

Winner: live_validation

Supporting sources: live_validation, history, server_card

Disagreements: none

initialize • OK
tools_list • Error
transport_compliance_probe • Error

Write-action publishing

Publishing blocked

action_safety_probe has not run yet -- no tool surface was observed, so write-action safety could not be assessed. Active alert(s) affecting production readiness: Latest validation is failing.

Confidence: medium (65.0)

Evidence provenance

Winner: live_validation

Supporting sources: live_validation, history

Disagreements: none

action_safety_probe • Not_Assessed

Snapshot churn risk

Not Assessed

No prior validation is available to compare against yet -- churn risk has not been assessed.

Confidence: medium (65.0)

Evidence provenance

Winner: history

Supporting sources: history, live_validation

Disagreements: none

tool_snapshot_probe • Missing
connector_replay_probe • Missing

Client compatibility gate details

ChatGPT custom connector

Partially client-compatible

Remediation checklist

Support dynamic client registration (DCR) to simplify connector setup.
Fix the server so tools/list returns successfully.
Resolve the transport compliance failure -- see the transport compliance probe evidence for what specifically broke.
Limit the exposed surface to search/fetch-style read tools.
Remove export, bulk, mutating, and high-blast-radius exposure before certifying company-knowledge use.
Satisfy OAuth, compatibility, and connector-refresh requirements before using the Messages API remote MCP path.

Claude remote MCP

Partially client-compatible

Remediation checklist

Fix the server so tools/list returns successfully.
Resolve the transport compliance failure -- see the transport compliance probe evidence for what specifically broke.
Limit the exposed surface to search/fetch-style read tools.
Remove export, bulk, mutating, and high-blast-radius exposure before certifying company-knowledge use.
Satisfy OAuth, compatibility, and connector-refresh requirements before using the Messages API remote MCP path.
Resolve transport compliance issues before wider client rollout.

Write-safe publishing

Blocked

Production readiness is blocked by an active alert: Latest validation is failing.

Remediation checklist

Resolve the active alert: Latest validation is failing.

Verdict traces

Production verdict

Failing

The latest validation run was attempted but did not complete successfully.

Confidence: medium (65.0)

Winning source: live_validation

Triggering alerts

server_failing • critical • Latest validation is failing

Client verdict trace table

Verdict	Status	Checks	Winning source	Conflicts
`openai_connectors`	Partially client-compatible	initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe	live_validation	none
`claude_desktop`	Partially client-compatible	initialize, tools_list, transport_compliance_probe	live_validation	none
`unsafe_for_write_actions`	Publishing blocked	action_safety_probe	live_validation	none
`snapshot_churn_risk`	Not Assessed	tool_snapshot_probe, connector_replay_probe	history	none

Publishability policy profiles

ChatGPT custom connector compatibility

Compatible with review

Search Fetch Only: No
Write Actions Present: No
Oauth Configured: Yes
Admin Refresh Required: No
Safe For Company Knowledge: No
Safe For Messages Api Remote Mcp: No

Claude remote MCP compatibility

Compatible with review

tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; The tool surface is not limited to search/fetch-style read tools.; Not yet safe for company-knowledge use: requires a search/fetch-only surface with no export, bulk, mutating, or high-blast-radius exposure.; Not yet safe for the Messages API remote MCP path: requires OAuth, a compatible connector profile, and no pending connector-refresh risk. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.

Search Fetch Only: No
Write Actions Present: No
Oauth Configured: Yes
Admin Refresh Required: No
Safe For Company Knowledge: No
Safe For Messages Api Remote Mcp: No

Compatibility fixtures

ChatGPT custom connector fixture

Degraded

Dynamic client registration materially improves connector setup.; tools/list must succeed.; Transport compliance failed or did not complete successfully.

remote_http_endpoint: Passes
oauth_discovery: Passes
frozen_tool_snapshot_refresh: Passes
request_association: Passes

Anthropic remote MCP fixture

Degraded

tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.

remote_transport: Passes
tool_discovery: Likely to fail
auth_connect: Passes
safe_write_review: Degraded

Recommended for

No recommendation profile is available yet.

Evidence

Current trust snapshot

Snapshot ID

trustsnap_e4562f29bb575960

Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.

Snapshot generated

Aug 11, 2026 11:39:06 AM UTC

All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.

Last validated

Aug 11, 2026 07:59:52 AM UTC

Age: 3.65h • evidence age tier: Verified in last 24h • display score: suppressed

Canonical machine links

Compare index

/compare.json

Compare API

/v1/compare?server=davidmosiah%2Fdelx-mcp-server

Trust summary

/v1/servers/davidmosiah/delx-mcp-server/trust-summary

Report JSON

/v1/servers/davidmosiah/delx-mcp-server/report

Policy export

/v1/servers/davidmosiah/delx-mcp-server/policy

Badge metadata

/v1/servers/davidmosiah/delx-mcp-server/badge

Ledger evidence

/v1/servers/davidmosiah/delx-mcp-server/ledger

Human compare URL

/compare?server=davidmosiah%2Fdelx-mcp-server

Evidence confidence

Confidence score

65.0

Based on 0 recent validations, 27 captured checks, and validation age of 3.7 hours.

Live checks captured

More direct checks increase trust in the current verdict.

Validation age

3.6h

Lower age means fresher evidence.

Latest validation evidence

Latest summary

Failing

Validation profile

remote_mcp

Started

Aug 11, 2026 07:59:47 AM UTC

Latency

4834.4 ms

Failures

server_card Response body exceeded byte limit
tools_list Response body exceeded byte limit
transport_compliance_probe Issues: missing session id, missing protocol header, bad protocol not rejected (bad protocol=200).

Checks

Check	Status	Latency	Evidence
`action_safety_probe`	Not_Assessed	n/a	No write-action risk evidence recorded.
`advanced_capabilities_probe`	Missing	n/a	No advanced MCP capability signals detected.
`connector_publishability_probe`	Error	n/a	Publishability blockers: tools list, transport compliance, action safety, server card, +1 more.
`connector_replay_probe`	Missing	n/a	No connector replay evidence recorded.
`determinism_probe`	Missing	n/a	tools list unavailable
`initialize`	OK	115.2 ms	Protocol 2025-03-26
`interactive_flow_probe`	OK	n/a	Check completed
`oauth_authorization_server`	OK	121.3 ms	agent_auth, authorization_endpoint, delx:access_mode, delx:note
`oauth_protected_resource`	OK	343.1 ms	1 authorization server(s)
`official_registry_probe`	Missing	n/a	Check completed
`openid_configuration`	OK	128.4 ms	agent_auth, authorization_endpoint, delx:access_mode, delx:note
`probe_noise_resilience`	OK	397.2 ms	Fetched https://api.delx.ai/robots.txt
`prompt_get`	Missing	n/a	not advertised
`prompts_list`	Missing	355.3 ms	Client error '400 Bad Request' for url 'https://api.delx.ai/v1/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
`protocol_version_probe`	Warning	n/a	Claims 2025-03-26; 2 release(s) behind 2025-11-25.
`provenance_divergence_probe`	Not_Assessed	n/a	Check completed
`request_association_probe`	Missing	n/a	No request-association capabilities were advertised.
`resource_read`	Missing	n/a	not advertised
`resources_list`	Missing	326.2 ms	Client error '400 Bad Request' for url 'https://api.delx.ai/v1/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
`schema_divergence_probe`	Missing	n/a	no server card tools
`server_card`	Error	668.1 ms	Response body exceeded byte limit
`session_resume_probe`	Warning	n/a	no session id
`step_up_auth_probe`	OK	n/a	Scopes=public.
`tool_snapshot_probe`	Missing	n/a	no tools
`tools_list`	Error	682.2 ms	Response body exceeded byte limit
`transport_compliance_probe`	Error	1026.0 ms	Issues: missing session id, missing protocol header, bad protocol not rejected (bad protocol=200).
`utility_coverage_probe`	Missing	110.5 ms	No completions evidence; no pagination evidence; tasks missing.

Known versions

No versions recorded.

Public server reputation

Validation success 7d

0.5

Validation success 30d

0.5

Mean time to recover

n/a

Breaking diffs 30d

Registry drift frequency 30d

Snapshot changes 30d

Benchmark tasks

Benchmark task	Status	Evidence
Discover tools	Likely to fail	`initialize` • OK `tools_list` • Error
Read-only fetch flow	Likely to fail	`resource_read` • Missing `read_only_tool_surface` • Missing
OAuth-required connect	Passes	`oauth_protected_resource` • OK `step_up_auth_probe` • OK
Safe write flow with confirmation	Likely to fail	`action_safety_probe` • Not_Assessed

Utility coverage

Probe status

Missing

Completions

not detected

Completion probe target: none

Pagination

not detected

No nextCursor evidence.

Tasks

Missing

Advertised: no

Tool snapshot diff & changelog

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

Validation diff

Need at least two validation runs before diffing changes.

Registry & provenance divergence

Probe status

Error

Direct official match

Drift fields

homepage registry_identifier registry_source remote_url

Field	Registry	Live server card
Title	n/a	n/a
Version	n/a	n/a
Homepage	n/a	n/a

Active alerts

Latest validation is failing (critical)
Core MCP flows did not validate successfully on the latest run.

Aliases & registry graph

Identifier	Source	Canonical	Identity evidence	Score
`davidmosiah/delx-mcp-server`	glama_registry	yes	canonical	n/a
`github-davidmosiah/delx-mcp-server`	github_topic_registry	no	repo_slug	n/a
`awesome-davidmosiah/delx-mcp-server`	awesome_mcp_servers	no	repo_slug	n/a

Alias consolidation

Strong alias identity requires matching remote URL, server-card URL, repository slug, or explicit registry cross-reference; shared provider namespace alone is not identity.

Canonical identifier

davidmosiah/delx-mcp-server

Duplicate aliases

Registry sources

awesome_mcp_servers github_topic_registry glama_registry

Remote URLs

https://api.delx.ai/v1/mcp

https://delx.ai/mcp-server

https://glama.ai/mcp/servers/davidmosiah/delx-mcp-server/badges/score.svg)](https://glama.ai/mcp/servers/davidmosiah/delx-mcp-server

Homepages

https://delx.ai/mcp-server

https://github.com/davidmosiah/delx-mcp-server

https://glama.ai/mcp/servers/q8t098iwao

Source disagreements

Field	What differs	Observed values
Registry source	Multiple registries or registry sync paths claim this same canonical server.	awesome_mcp_servers github_topic_registry glama_registry
Remote URL	Aliases currently point at different MCP endpoints, which can indicate mirrors, stale registry data, or a real endpoint split.	https://api.delx.ai/v1/mcp https://delx.ai/mcp-server https://glama.ai/mcp/servers/davidmosiah/delx-mcp-server/badges/score.svg)](https://glama.ai/mcp/servers/davidmosiah/delx-mcp-server
Homepage	Registry entries disagree on the primary homepage for this server.	https://delx.ai/mcp-server https://github.com/davidmosiah/delx-mcp-server https://glama.ai/mcp/servers/q8t098iwao
Registry identifier	Different registry-specific identifiers resolve to the same canonical server record here.	awesome_mcp_servers:davidmosiah/delx-mcp-server github_topic_registry:davidmosiah/delx-mcp-server glama_registry:q8t098iwao

Fix it

Why this score?

Access & Protocol

22/44

Connectivity, auth, and transport expectations for common clients.

Interface Quality

2/56

How well the tool/resource interface communicates and behaves under automation.

Security Posture

3/36

How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.

Reliability & Trust

9/24

Operational stability, consistency, and trustworthiness over time.

Discovery & Governance

11/28

How well the server is documented, listed, and governed in public registries.

Adoption & Market

2/8

Adoption clues and public evidence that the server is intended for external use.

Algorithmic score breakdown

Auth Operability

4/4

Measures whether auth discovery and protected access behave predictably for clients.

Error Contract Quality

0/4

Grades machine-readable error structure, status alignment, and remediation hints.

Rate-Limit Semantics

2/4

Checks whether quota/throttle responses are deterministic and automation-friendly.

Schema Completeness

0/4

Completeness of tool descriptions, parameter docs, examples, and schema shape.

Backward Compatibility

4/4

Stability score across tool schema/name drift relative to prior validations.

SLO Health

1/4

Availability, latency, and burst-failure profile across recent validation history.

Security Hygiene

0/4

HTTPS posture, endpoint hygiene, and response-surface hardening checks.

Task Success

0/4

Can an agent reliably initialize, enumerate tools, and execute core MCP flows?

Trust Confidence

2/4

Confidence-adjusted reliability score that penalizes low evidence volume.

Prompt Contract

0/4

Quality of prompt metadata, argument shape, and prompt discoverability for clients.

Resource Contract

0/4

How completely resources and resource templates describe URIs, types, and usage shape.

Discovery Metadata

2/4

Homepage, docs, icon, repository, support, and license coverage for directory consumers.

Registry Consistency

2/4

Agreement between stored registry metadata, live server-card data, and current validation output.

Installability

2/4

How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.

Session Semantics

1/4

Determinism and state behavior across repeated MCP calls, including sticky-session surprises.

Tool Surface Design

0/4

Naming clarity, schema ergonomics, and parameter complexity across the tool surface.

Result Shape Stability

0/4

Stability of declared output schemas across validations, with penalties for drift or missing shapes.

OAuth Interop

3/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

2/4

Versioning, update recency, and historical validation cadence that indicate active stewardship.

Adoption Signal

1/4

Directory presence and distribution clues that suggest the server is intended for external use.

Freshness Confidence

2/4

Confidence that recent validations are current enough and dense enough to trust operationally.

Transport Fidelity

3/4

Whether declared transport metadata matches the observed endpoint behavior and response formats.

Spec Recency

2/4

How close the server’s claimed MCP protocol version is to the latest known public revision.

Session Resume

3/4

Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.

Step-Up Auth

4/4

Whether OAuth metadata and WWW-Authenticate challenges support granular, incremental consent instead of broad upfront scopes.

Transport Compliance

0/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

1/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

3/4

Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.

Official Registry Presence

3/4

Whether the server appears directly or indirectly in the official MCP registry.

Safety Transparency

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.

Data Exfiltration Resilience

0/4

Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.

Supply Chain Signal

0/4

Public metadata signal for repository, changelog, license, versioning, and recency that supports supply-chain trust.

Input Sanitization Safety

0/4

Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.

Tool Namespace Clarity

0/4

Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.

8 component(s) not assessed for this run: Abuse/Noise Resilience, Action Safety, Provenance Divergence, Destructive Operation Safety, Egress / SSRF Resilience, Execution / Sandbox Safety, Least Privilege Scope, Secret Handling Hygiene

Experimental candidate components

Personal Data Exposure

1.5

Experimental candidate, weight 0. Export and bulk-access evidence only; no impact on totals, verdicts, rankings, or gates.

Actionable remediation

Severity	Remediation	Why it matters	Recommended action
Critical	Ensure tools/list succeeds consistently	Tools discovery is the minimum viable contract for most MCP clients and directories.	Make tools/list succeed unauthenticated when possible, or document the auth flow in the server card. Playbook Make `tools/list` deterministic across repeated calls. Document or relax auth requirements for discovery routes. Check that tool names, descriptions, and schemas remain stable across deploys.
Critical	Respond to latest validation is failing	Core MCP flows did not validate successfully on the latest run.	Fix the failing checks first, then revalidate to confirm the recovery path. Playbook Fix the failing checks first. Review the latest incident feed and validation diff for the first regression. Revalidate once the remediation lands.
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	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	Resolve conflicting endpoints across registry aliases	Registry aliases for this canonical server currently resolve to different live MCP endpoints (https://api.delx.ai/v1/mcp, https://delx.ai/mcp-server, https://glama.ai/mcp/servers/davidmosiah/delx-mcp-server/badges/score.svg)](https://glama.ai/mcp/servers/davidmosiah/delx-mcp-server). An agent following one registry entry reaches a different server than one following another.	Confirm which endpoint is canonical, correct or retire the stale registry entry, and re-sync so every alias agrees on one remote_url. Playbook Identify which of the listed remote_url values is the operator's actual, currently-maintained endpoint. Update or remove the registry entries pointing at any other endpoint (a mirror, a stale fork, or a decommissioned deployment). Re-run registry sync and confirm the alias-consolidation view shows a single remote_url before treating this as resolved.
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	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	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

Component	Current	Points missing
Utility Coverage	0/4	-4.0
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
Task Success	0/4	-4.0
Security Hygiene	0/4	-4.0
Schema Completeness	0/4	-4.0
Result Shape Stability	0/4	-4.0
Resource Contract	0/4	-4.0
Request Association	0/4	-4.0

Compatibility profiles

OpenAI Connectors

66.7

partial (6 of 9 requirements met)

Dynamic client registration materially improves connector setup.; tools/list must succeed.; Transport compliance failed or did not complete successfully.

Connector URL: https://api.delx.ai/v1/mcp
# Complete OAuth in the client when prompted.
# Server: davidmosiah/delx-mcp-server

Claude Desktop

66.7

partial (4 of 6 requirements met)

tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.

{
  "mcpServers": {
    "delx-mcp-server": {
      "command": "npx",
      "args": ["mcp-remote", "https://api.delx.ai/v1/mcp"]
    }
  }
}

Smithery

60.0

partial (3 of 5 requirements met)

Tool discovery must succeed.; Machine-readable failure semantics should be present.

smithery mcp add "https://api.delx.ai/v1/mcp"

Generic Streamable HTTP

66.7

partial (4 of 6 requirements met)

tools/list must succeed.; Session behavior should be predictable.

curl -sS https://api.delx.ai/v1/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Governance

MCP TrustOps

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

Evidence age tier

Verified in last 24h

Policy SLA (contractual, distinct from the public 24h freshness window): 168.0h • confidence-weighted score (display score discounted for evidence age and confidence -- an internal TrustOps input, not the public score): n/a • evidence too old to display: ✕

Policy exports

Export policy

Formats: json, rego, yaml, github_action, gateway_config, client_report

Runtime routing

/v1/decide

Returns allowed tools, blocked tools, approval requirement, and reason.

Hosted runtime

Verify Hosted MCP

Deploy trusted servers from GitHub with secrets, egress controls, releases, rollback, and audit events.

Authenticated validation

Premium publisher feature: paid authenticated runs verify scopes, write-action safeguards, and authorized tool execution.

Active trust badges

none

Semantic benchmarks

available

Templates cover GitHub, database, healthcare, web search, and CRM least-privilege jobs.

Supply chain

metadata signal

Deep scan checks are marked separately from public metadata signals.

Compliance metadata

Terms, privacy, SOC 2, HIPAA, GDPR, retention, deletion, and audit-log fields are tracked as enterprise metadata.

Alert subscription types

Status changes Score drops or recovers Freshness SLA breach Validation schema drift OAuth or auth behavior changes Tool surface changes New or changed write tool Supply-chain signal changes Legal or compliance metadata changes

MCP Runtime hosting

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

Activation readiness

Trusted hosted runtimes require fresh validation, a passing server state, a remote endpoint, and a minimum score.

Minimum tier

TrustOps

Publisher claim plus paid TrustOps tier are required before secrets or releases can be created.

Hosted endpoint

/hosted/{namespace}/{name}/mcp

The endpoint enforces egress allowlists and records audit/usage events.

Blockers

score_below_hosting_threshold server_not_healthy_or_degraded latest_validation_not_passing blocked_by_active_alerts blocked_by_production_readiness

Deployment	Status	Endpoint	Release
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://api.delx.ai/v1/mcp
# Complete OAuth in the client when prompted.
# Server: davidmosiah/delx-mcp-server

Claude Desktop

{
  "mcpServers": {
    "delx-mcp-server": {
      "command": "npx",
      "args": ["mcp-remote", "https://api.delx.ai/v1/mcp"]
    }
  }
}

Smithery

smithery mcp add "https://api.delx.ai/v1/mcp"

Generic Http

curl -sS https://api.delx.ai/v1/mcp -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://api.delx.ai/v1/mcp. This is the target server surface, not Verify's own inspection tools.

Live capability counts

754 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 davidmosiah/delx-mcp-server.

Direct machine links

JSON report • Compare this server • Verify MCP API

History

Validation history

7 day score delta

n/a

30 day score delta

n/a

Recent healthy ratio

n/a

Freshness

3.6h

Timestamp	Status	Score	Latency	Tools
Aug 11, 2026 07:59:52 AM UTC	Failing	5.9	4834.4 ms	0
Aug 10, 2026 07:59:43 PM UTC	Failing	5.5	10795.1 ms	0
Aug 10, 2026 07:59:15 AM UTC	Failing	12.4	5179.2 ms	not fetched
Aug 09, 2026 11:59:03 PM UTC	Failing	13.0	5125.7 ms	not fetched
Aug 09, 2026 07:58:44 PM UTC	Failing	11.4	4742.4 ms	not fetched
Aug 09, 2026 07:58:18 AM UTC	Healthy	67.2	4844.6 ms	not fetched
Aug 08, 2026 07:58:08 PM UTC	Healthy	66.2	4752.1 ms	not fetched
Aug 08, 2026 07:42:33 AM UTC	Healthy	65.6	4177.5 ms	not fetched

Validation timeline

Validated	Summary	Score	Protocol	Auth mode	Tools	Changes
Aug 11, 2026 07:59:52 AM UTC	Failing	5.9	2025-03-26	oauth_supported	0	none
Aug 10, 2026 07:59:43 PM UTC	Failing	5.5	2025-03-26	oauth_supported	0	none
Aug 10, 2026 07:59:15 AM UTC	Failing	12.4	unknown	unknown	not fetched	none
Aug 09, 2026 11:59:03 PM UTC	Failing	13.0	unknown	unknown	not fetched	none
Aug 09, 2026 07:58:44 PM UTC	Failing	11.4	unknown	unknown	not fetched	none
Aug 09, 2026 07:58:18 AM UTC	Healthy	67.2	unknown	unknown	not fetched	none
Aug 08, 2026 07:58:08 PM UTC	Healthy	66.2	unknown	unknown	not fetched	none
Aug 08, 2026 07:42:33 AM UTC	Healthy	65.6	unknown	unknown	not fetched	none
Aug 07, 2026 07:42:12 PM UTC	Healthy	65.1	unknown	unknown	not fetched	none
Aug 07, 2026 07:36:54 AM UTC	Healthy	57.3	unknown	unknown	not fetched	none

Recent validation runs

Recent validation runs for this MCP server
Started	Status	Summary	Latency	Checks
Aug 11, 2026 07:59:47 AM UTC	Completed	Failing	4834.4 ms	action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, schema_divergence_probe, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Aug 10, 2026 07:59:32 PM UTC	Completed	Failing	10795.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, schema_divergence_probe, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Aug 10, 2026 07:59:10 AM UTC	Completed	Failing	5179.2 ms
Aug 09, 2026 11:58:58 PM UTC	Completed	Failing	5125.7 ms
Aug 09, 2026 07:58:39 PM UTC	Completed	Failing	4742.4 ms
Aug 09, 2026 07:58:13 AM UTC	Completed	Healthy	4844.6 ms
Aug 08, 2026 07:58:03 PM UTC	Completed	Healthy	4752.1 ms
Aug 08, 2026 07:42:28 AM UTC	Completed	Healthy	4177.5 ms
Aug 07, 2026 07:42:07 PM UTC	Completed	Healthy	4473.3 ms
Aug 07, 2026 07:36:50 AM UTC	Completed	Healthy	3707.8 ms

Incident & change feed

Timestamp	Event	Details
Aug 11, 2026 07:59:52 AM UTC	Latest validation: failing	Score 9.9 with status failing.
Aug 05, 2026 11:00:30 AM UTC	Score corrected (post-1.0.503 remediation, R1 zero-anchoring)	Prior: 64.13. Corrected: 62.35.

Technical details

Raw evidence view

Show raw JSON evidence

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

{
  "checks": {
    "count": 27,
    "items": {
      "action_safety_probe": {
        "auth_present": true,
        "reason": "empty_observation_set",
        "safeguard_count": 0,
        "status": "not_assessed"
      },
      "advanced_capabilities_probe": {
        "status": "missing"
      },
      "connector_publishability_probe": {
        "status": "error"
      },
      "connector_replay_probe": {
        "reason": "no_tools",
        "status": "missing"
      },
      "determinism_probe": {
        "reason": "tools_list_unavailable",
        "status": "missing"
      },
      "initialize": {
        "http_status": 200,
        "latency_ms": 115.23,
        "payload_omitted": true,
        "status": "ok"
      },
      "interactive_flow_probe": {
        "status": "ok"
      },
      "oauth_authorization_server": {
        "http_status": 200,
        "latency_ms": 121.31,
        "payload_omitted": true,
        "status": "ok"
      },
      "oauth_protected_resource": {
        "http_status": 200,
        "latency_ms": 343.05,
        "payload_omitted": true,
        "status": "ok"
      },
      "official_registry_probe": {
        "status": "missing"
      },
      "openid_configuration": {
        "http_status": 200,
        "latency_ms": 128.45,
        "payload_omitted": true,
        "status": "ok"
      },
      "probe_noise_resilience": {
        "http_status": 200,
        "latency_ms": 397.23,
        "status": "ok"
      },
      "prompt_get": {
        "reason": "not_advertised",
        "status": "missing"
      },
      "prompts_list": {
        "http_status": 400,
        "latency_ms": 355.31,
        "payload_omitted": true,
        "reason": "not_advertised",
        "status": "missing"
      },
      "protocol_version_probe": {
        "status": "warning"
      },
      "provenance_divergence_probe": {
        "status": "not_assessed"
      },
      "request_association_probe": {
        "reason": "no_request_association_capabilities_advertised",
        "status": "missing"
      },
      "resource_read": {
        "reason": "not_advertised",
        "status": "missing"
      },
      "resources_list": {
        "http_status": 400,
        "latency_ms": 326.17,
        "payload_omitted": true,
        "reason": "not_advertised",
        "status": "missing"
      },
      "schema_divergence_probe": {
        "reason": "no_server_card_tools",
        "status": "missing"
      },
      "server_card": {
        "latency_ms": 668.12,
        "reason": "Response body exceeded byte limit",
        "status": "error"
      },
      "session_resume_probe": {
        "reason": "no_session_id",
        "status": "warning"
      },
      "step_up_auth_probe": {
        "status": "ok"
      },
      "tool_snapshot_probe": {
        "reason": "no_tools",
        "status": "missing"
      },
      "tools_list": {
        "latency_ms": 682.25,
        "reason": "Response body exceeded byte limit",
        "status": "error"
      },
      "transport_compliance_probe": {
        "latency_ms": 1025.95,
        "protocol_header_present": false,
        "status": "error"
      },
      "utility_coverage_probe": {
        "latency_ms": 110.45,
        "status": "missing"
      }
    },
    "omitted_count": 0
  },
  "failures": {
    "count": 3,
    "items": {
      "server_card": {},
      "tools_list": {},
      "transport_compliance_probe": {}
    },
    "omitted_count": 0
  },
  "message": "Raw evidence is summarized in HTML to keep server detail pages fast. Use the JSON report or evidence API for the full payload.",
  "remote_url": "https://api.delx.ai/v1/mcp",
  "server_card": {
    "name": null,
    "raw_payload_omitted": false,
    "version": null
  },
  "server_identifier": "davidmosiah/delx-mcp-server",
  "truncated": true
}

Capabilities

OAuth: ✓
DCR/CIMD: ✕
Prompts: ✕
Homepage: https://glama.ai/mcp/servers/q8t098iwao
Docs: none
Support: https://github.com/davidmosiah/delx-mcp-server
Icon: none
Remote endpoint: https://api.delx.ai/v1/mcp
Server card: none

Use-case taxonomy

other

Transport compliance drilldown

Probe status

Error

Transport

streamable-http

Session header

Protocol header

Bad protocol response

200

DELETE teardown

n/a

Expired session retry

n/a

Last-Event-ID visible

Issues: missing_session_id, 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

Connector replay

Status

Missing

Backward compatible

Would break after refresh

Added tools

none

Removed tools

none

Additive output changes

none

Required-argument replay breaks

Tool	Added required args	Removed required args
No required-argument replay breaks detected.

Output-schema replay breaks

Tool	Removed properties	Added properties
No output-schema replay breaks detected.