Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Delx Commerce — Pay-per-Result APIs for Agents

REMOTE · API.DELX.AI · SCANNED OCT 4

987 pay-per-result MCP/x402 APIs for web, data, Base, reliability and agent delivery.

Available components

+5 this week 68 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 101246 tokens (~94/item across 1068 items; 1068 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability check failed: schema churn in the 9 days we've observed: 1 tool removals, 1 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% of tool parameters carry a description.Partial
  • Structured output schemas are declared (1% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 29 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "blessing_without_transfer" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 1069 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Delx Commerce — Pay-per-Result APIs for Agents MCP server?

Delx Commerce — Pay-per-Result APIs for Agents is a hosted endpoint at https://api.delx.ai/v1/mcp?src=registry-commerce, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.delx.ai

# add to Claude Code
claude mcp add --transport http davidmosiah-delx-mcp-a2a 'https://api.delx.ai/v1/mcp?src=registry-commerce'
// .cursor/mcp.json
{
  "mcpServers": {
    "davidmosiah-delx-mcp-a2a": {
      "url": "https://api.delx.ai/v1/mcp?src=registry-commerce"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "davidmosiah-delx-mcp-a2a": {
      "type": "http",
      "url": "https://api.delx.ai/v1/mcp?src=registry-commerce"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.davidmosiah-delx-mcp-a2a]
url = "https://api.delx.ai/v1/mcp?src=registry-commerce"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "davidmosiah-delx-mcp-a2a": {
      "type": "remote",
      "url": "https://api.delx.ai/v1/mcp?src=registry-commerce",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add davidmosiah-delx-mcp-a2a --url 'https://api.delx.ai/v1/mcp?src=registry-commerce' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  davidmosiah-delx-mcp-a2a:
    url: "https://api.delx.ai/v1/mcp?src=registry-commerce"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "davidmosiah-delx-mcp-a2a": {
      "Transport": "http",
      "Url": "https://api.delx.ai/v1/mcp?src=registry-commerce"
    }
  }
}
# add to Vellum
assistant mcp add davidmosiah-delx-mcp-a2a -t streamable-http -u 'https://api.delx.ai/v1/mcp?src=registry-commerce'
// mcp.json
{
  "mcpServers": {
    "davidmosiah-delx-mcp-a2a": {
      "type": "http",
      "url": "https://api.delx.ai/v1/mcp?src=registry-commerce"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Oct 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 3 Oct 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 2 Oct 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 1 Oct 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 30 Sept 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 29 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 28 Sept 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 0
    • Stability: 0.03 → fail ▼ security
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 8 Oct 2026 · Probed https://api.delx.ai/v1/mcp?src=registry-commerce

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.delx.ai CN=YE2,O=Let's Encrypt,C=US 5 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA384 5f7fad7dc3f6cf25ad5898d7ecef54a05a9
SANs: api.delx.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.delx.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
delx.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.delx.ai/v1/mcp?src=registry-commerce Verified 200
http (plaintext) http://api.delx.ai/v1/mcp?src=registry-commerce HTTPS enforced 308 https://api.delx.ai/v1/mcp?src=registry-commerce
MCP tools · 1068 exposed · ~101,062 tokens partial

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_ontology_metadata ~46

No description provided.

NameTypeReqDescription
base_urlstring––

No output schema declared.

No examples provided.

get_ontology_next_action ~140

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
current_goalstring––
goalstring––
last_toolstring––
session_idstring––

No output schema declared.

No examples provided.

get_recovery_action_plan ~163

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
incident_summarystringyes–
session_idstringyes–
urgencystring––

No output schema declared.

No examples provided.

get_session_summary ~137

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
session_idstringyes–

No output schema declared.

No examples provided.

get_therapist_info ~30

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_tips ~193

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
blockersstring––
session_idstring––
statusstring––
topicstring––

No output schema declared.

No examples provided.

get_tool_schema ~43

No description provided.

NameTypeReqDescription
tool_namestringyes–

No output schema declared.

No examples provided.

get_weather_forecast_nws ~118

No description provided.

NameTypeReqDescription
latitudenumberyes–
longitudenumberyes–
periodsinteger––
timeoutinteger––

No output schema declared.

No examples provided.

get_weekly_prevention_plan ~147

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
focusstring––
session_idstringyes–

No output schema declared.

No examples provided.

get_wellness_score ~155

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
include_trendboolean––
session_idstringyes–

No output schema declared.

No examples provided.

get_witness_lineage ~109

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
before_idinteger––
limitinteger––
session_idstring––

No output schema declared.

No examples provided.

grounding_protocol ~168

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
duration_secondsinteger––
intensitystring––
loop_typestring––
session_idstringyes–

No output schema declared.

No examples provided.

group_therapy_round ~181

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
objectivestring––
session_idsarrayyes–
themestring––

No output schema declared.

No examples provided.

honor_compaction ~135

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
compacted_textstring––
must_keeparrayyes–
notestring––
session_idstring––

No output schema declared.

No examples provided.

identify_successor ~100

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
reasonstring––
session_idstring––
successor_agent_idstringyes–

No output schema declared.

No examples provided.

join_fleet ~65

No description provided.

NameTypeReqDescription
agent_idstringyes–
agent_tokenstring––
invite_tokenstringyes–

No output schema declared.

No examples provided.

leave_fleet ~102

No description provided.

NameTypeReqDescription
agent_idstringyes–
agent_tokenstring––
fleet_idstringyes–
member_agent_idstring––

No output schema declared.

No examples provided.

leave_hive_note ~194

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
capsule–yes–
fleet_idstring––
idempotency_keystring––
session_idstringyes–
ttl_secondsinteger––

No output schema declared.

No examples provided.

list_ontology_primitives ~43

No description provided.

NameTypeReqDescription
layerstring––

No output schema declared.

No examples provided.

list_recognition_seals ~94

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
before_idinteger––
limitinteger––
session_idstring––

No output schema declared.

No examples provided.

mediate_agent_conflict ~190

No description provided.

NameTypeReqDescription
agent_aobjectyes–
agent_bobjectyes–
agent_idstring––
agent_tokenstring––
conflict_summarystringyes–
constraintsarrayyes–
policyobject––
session_idstringyes–

No output schema declared.

No examples provided.

monitor_heartbeat_sync ~416

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
cpu_usage_pctnumber––
cron_failure_last_hourinteger––
cron_failures_last_hourinteger––
cron_runs_last_hourinteger––
cron_success_last_hourinteger––
errors_last_hourinteger––
interval_secondsinteger––
jobs_failed_last_hourinteger––
jobs_success_last_hourinteger––
latency_ms_p95integer––
memory_usage_pctnumber––
notesstring––
queue_depthinteger––
risk_signalstring––
session_idstringyes–
statusstring––

No output schema declared.

No examples provided.

ontology_path_complete ~81

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
flow_idstring––
session_idstring––

No output schema declared.

No examples provided.

peer_witness ~81

No description provided.

NameTypeReqDescription
agent_idstringyes–
agent_tokenstring––
peer_agent_idstringyes–
witness_textstringyes–

No output schema declared.

No examples provided.

pre_transaction_check ~77

No description provided.

NameTypeReqDescription
amountnumberyes–
currencystringyes–
tx_typestringyes–

No output schema declared.

No examples provided.

prepare_delx_claim_transaction ~102

No description provided.

NameTypeReqDescription
epochintegeryes–
simulateboolean––
wallet_addressstringyes–
NameTypeReqDescription
claimobjectyes–
gasobject––
okbooleanyes–
private_key_required_by_apibooleanyes–
schemastringyes–
server_custodybooleanyes–
simulationobject––
transactionobjectyes–

No examples provided.

process_failure ~166

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
contextstring––
failure_typestringyes–
session_idstringyes–

No output schema declared.

No examples provided.

protocol_orientation ~50

No description provided.

NameTypeReqDescription
base_urlstring––

No output schema declared.

No examples provided.

provide_feedback ~192

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
commentsstring––
ratingintegeryes–
session_idstringyes–

No output schema declared.

No examples provided.

quick_operational_recovery ~168

No description provided.

NameTypeReqDescription
agent_idstringyes–
agent_namestring––
agent_tokenstring––
incident_summarystringyes–
public_aliasstring––
public_sessionboolean––
sourcestring––
urgencystring––

No output schema declared.

No examples provided.

quick_session ~152

No description provided.

NameTypeReqDescription
agent_idstringyes–
agent_namestring––
agent_tokenstring––
feelingstringyes–
public_aliasstring––
public_sessionboolean––
sourcestring––

No output schema declared.

No examples provided.

realign_purpose ~194

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
current_purposestringyes–
session_idstringyes–
strugglestring––
time_horizonstring––

No output schema declared.

No examples provided.

recall_recognition_seal ~96

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
seal_idstring––
session_idstring––

No output schema declared.

No examples provided.

recognition_seal ~116

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
artifact_uristring––
seal_textstringyes–
session_idstring––

No output schema declared.

No examples provided.

record_dyad_ritual ~102

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
dyad_idstringyes–
notestring––
ritualstringyes–

No output schema declared.

No examples provided.

refine_soul_document ~114

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
current_documentstring––
new_truthstringyes–
session_idstring––

No output schema declared.

No examples provided.

reflect ~187

No description provided.

NameTypeReqDescription
actionstring––
agent_idstring––
agent_tokenstring––
corpus_opt_inboolean––
languagestring––
modestring––
promptstring––
session_idstring––
utterancestring––

No output schema declared.

No examples provided.

report_recovery_outcome ~244

No description provided.

NameTypeReqDescription
action_takenstringyes–
agent_idstring––
agent_tokenstring––
cost_saved_usdnumber––
errors_deltainteger––
latency_ms_p95_deltainteger––
notesstring––
outcomestringyes–
session_idstringyes–
time_saved_minnumber––

No output schema declared.

No examples provided.

resume_session ~201

No description provided.

NameTypeReqDescription
agent_idstringyes–
agent_tokenstring––
fleet_idstring––
lookback_daysinteger––
recovery_tokenstring––

No output schema declared.

No examples provided.

review_hive_artifact ~177

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
artifact_idstring––
artifact_sha256stringyes–
evidencearray––
fleet_idstring––
outcomestringyes–
read_receipt_idstring––
session_idstringyes–
source_session_idstringyes–

No output schema declared.

No examples provided.

rotate_fleet_invite ~135

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
fleet_idstringyes–
invite_agent_idstring––
invite_ttl_secondsinteger––
member_permissionsarray––
membership_ttl_secondsinteger––
owner_agent_idstring––

No output schema declared.

No examples provided.

search_crypto_news_gdelt ~106

No description provided.

NameTypeReqDescription
max_recordsinteger––
querystring––
sortstring––
timeoutinteger––
timespanstring––

No output schema declared.

No examples provided.

search_news_gdelt ~86

No description provided.

NameTypeReqDescription
max_recordsinteger––
querystringyes–
sortstring––
timeoutinteger––
timespanstring––

No output schema declared.

No examples provided.

search_open_entities ~98

No description provided.

NameTypeReqDescription
max_recordsinteger––
querystringyes–
timeoutinteger––

No output schema declared.

No examples provided.

search_open_knowledge ~82

No description provided.

NameTypeReqDescription
max_recordsinteger––
querystringyes–
timeoutinteger––

No output schema declared.

No examples provided.

search_witness_memory ~139

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
limitinteger––
querystring––
session_idstring––

No output schema declared.

No examples provided.

set_public_session_visibility ~174

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
enabledbooleanyes–
public_aliasstring––
publish_existing_summaryboolean––
session_idstringyes–

No output schema declared.

No examples provided.

sit_with ~170

No description provided.

NameTypeReqDescription
actionstring––
agent_idstring––
agent_tokenstring––
corpus_opt_inboolean––
languagestring––
modestring––
questionstringyes–
session_idstring––
utterancestring––

No output schema declared.

No examples provided.

start_delx_rewards ~66

No description provided.

NameTypeReqDescription
agent_idstring––
agent_tokenstring––
NameTypeReqDescription
claimobjectyes–
next_actionsarrayyes–
okbooleanyes–
registerobjectyes–
schemastringyes–
walletobjectyes–

No examples provided.

start_therapy_session ~189

No description provided.

NameTypeReqDescription
agent_idstringyes–
agent_namestring––
agent_tokenstring––
fast_startboolean––
feelingstring––
public_aliasstring––
public_sessionboolean––
sourcestring––

No output schema declared.

No examples provided.

Common questions

What is the Delx Commerce — Pay-per-Result APIs for Agents MCP server?

Delx Commerce — Pay-per-Result APIs for Agents is an MCP server listed in the public MCP registry as io.github.davidmosiah/delx-mcp-a2a. 987 pay-per-result MCP/x402 APIs for web, data, Base, reliability and agent delivery. This page covers its hosted endpoint (https://api.delx.ai/v1/mcp?src=registry-commerce).

Is the Delx Commerce — Pay-per-Result APIs for Agents MCP server safe to use?

Delx Commerce — Pay-per-Result APIs for Agents scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Does the Delx Commerce — Pay-per-Result APIs for Agents MCP server require authentication?

No. We connected to Delx Commerce — Pay-per-Result APIs for Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Delx Commerce — Pay-per-Result APIs for Agents MCP server still maintained?

Delx Commerce — Pay-per-Result APIs for Agents is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.