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
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1037 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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
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
claude mcp add --transport http davidmosiah-delx-mcp-a2a 'https://api.delx.ai/v1/mcp?src=registry-commerce'
{
"mcpServers": {
"davidmosiah-delx-mcp-a2a": {
"url": "https://api.delx.ai/v1/mcp?src=registry-commerce"
}
}
} {
"servers": {
"davidmosiah-delx-mcp-a2a": {
"type": "http",
"url": "https://api.delx.ai/v1/mcp?src=registry-commerce"
}
}
} [mcp_servers.davidmosiah-delx-mcp-a2a] url = "https://api.delx.ai/v1/mcp?src=registry-commerce"
{
"$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
}
}
} openclaw mcp add davidmosiah-delx-mcp-a2a --url 'https://api.delx.ai/v1/mcp?src=registry-commerce' --transport streamable-http
mcp_servers:
davidmosiah-delx-mcp-a2a:
url: "https://api.delx.ai/v1/mcp?src=registry-commerce" {
"McpServers": {
"davidmosiah-delx-mcp-a2a": {
"Transport": "http",
"Url": "https://api.delx.ai/v1/mcp?src=registry-commerce"
}
}
} assistant mcp add davidmosiah-delx-mcp-a2a -t streamable-http -u 'https://api.delx.ai/v1/mcp?src=registry-commerce'
{
"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.
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
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 |
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 →
util_json_cross_field_order ~232
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| left_field | string | yes | – |
| object | object | yes | – |
| relation | string | yes | – |
| right_field | string | yes | – |
No output schema declared.
No examples provided.
util_json_depth_check ~169
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| maximum_depth | integer | yes | – |
| value | object | yes | – |
No output schema declared.
No examples provided.
util_json_email_fields_check ~172
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | yes | – |
| object | object | yes | – |
No output schema declared.
No examples provided.
util_json_empty_prune ~148
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| object | object | yes | – |
No output schema declared.
No examples provided.
util_json_enum_fields_check ~174
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| enums | object | yes | – |
| object | object | yes | – |
No output schema declared.
No examples provided.
util_json_escape ~30
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
util_json_hash_fields_check ~203
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | yes | – |
| hex_length | integer | yes | – |
| object | object | yes | – |
No output schema declared.
No examples provided.
util_json_key_allowlist ~174
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed | array | yes | – |
| object | object | yes | – |
No output schema declared.
No examples provided.
util_json_key_denylist ~180
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| denied | array | yes | – |
| object | object | yes | – |
No output schema declared.
No examples provided.
util_json_keys ~37
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| json_text | string | yes | – |
No output schema declared.
No examples provided.
util_json_lines_parse ~142
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
util_json_lines_stringify ~147
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
util_json_merge_patch ~44
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| patch | object | yes | – |
| target | object | yes | – |
No output schema declared.
No examples provided.
util_json_minify ~39
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| json_text | string | yes | – |
No output schema declared.
No examples provided.
util_json_null_prune ~147
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| object | object | yes | – |
No output schema declared.
No examples provided.
util_json_number_coerce ~146
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| values | array | yes | – |
No output schema declared.
No examples provided.
util_json_numeric_range_check ~225
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | yes | – |
| maximum | number | yes | – |
| minimum | number | yes | – |
| object | object | yes | – |
No output schema declared.
No examples provided.
util_json_object_deep_merge ~176
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| left | object | yes | – |
| right | object | yes | – |
No output schema declared.
No examples provided.
util_json_object_diff ~170
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| after | object | yes | – |
| before | object | yes | – |
No output schema declared.
No examples provided.
util_json_object_lowercase_keys ~149
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| object | object | yes | – |
No output schema declared.
No examples provided.
util_json_object_omit ~172
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| keys | array | yes | – |
| object | object | yes | – |
No output schema declared.
No examples provided.
util_json_object_pick ~168
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| keys | array | yes | – |
| object | object | yes | – |
No output schema declared.
No examples provided.
util_json_object_rename_keys ~177
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| mapping | object | yes | – |
| object | object | yes | – |
No output schema declared.
No examples provided.
util_json_object_sort_keys ~147
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| object | object | yes | – |
No output schema declared.
No examples provided.
util_json_patch_preview ~173
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| document | object | yes | – |
| operations | array | yes | – |
No output schema declared.
No examples provided.
util_json_path_pick ~41
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| object | object | yes | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
util_json_pattern_fields_check ~200
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | yes | – |
| object | object | yes | – |
| pattern | string | yes | – |
No output schema declared.
No examples provided.
util_json_pointer_escape ~139
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | – |
No output schema declared.
No examples provided.
util_json_pointer_get ~169
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| document | object | yes | – |
| pointer | string | yes | – |
No output schema declared.
No examples provided.
util_json_pointer_unescape ~145
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | – |
No output schema declared.
No examples provided.
util_json_pretty ~39
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| json_text | string | yes | – |
No output schema declared.
No examples provided.
util_json_required_fields_check ~174
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| object | object | yes | – |
| required_fields | array | yes | – |
No output schema declared.
No examples provided.
util_json_schema_quickcheck ~50
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| instance | object | yes | – |
| schema | object | yes | – |
No output schema declared.
No examples provided.
util_json_schema_validate_lite ~45
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| instance | object | yes | – |
| schema | object | yes | – |
No output schema declared.
No examples provided.
util_json_shape_profile ~39
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
No output schema declared.
No examples provided.
util_json_size_budget ~172
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| maximum_bytes | integer | yes | – |
| value | object | yes | – |
No output schema declared.
No examples provided.
util_json_string_length_check ~226
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | yes | – |
| maximum | integer | yes | – |
| minimum | integer | yes | – |
| object | object | yes | – |
No output schema declared.
No examples provided.
util_json_timestamp_fields_check ~231
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | yes | – |
| maximum_epoch | integer | yes | – |
| minimum_epoch | integer | yes | – |
| object | object | yes | – |
No output schema declared.
No examples provided.
util_json_to_csv ~48
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| delimiter | string | – | – |
| json_text | string | yes | – |
No output schema declared.
No examples provided.
util_json_type ~37
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| json_text | string | yes | – |
No output schema declared.
No examples provided.
util_json_type_map_check ~175
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| object | object | yes | – |
| types | object | yes | – |
No output schema declared.
No examples provided.
util_json_type_name ~28
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| value | array | yes | – |
No output schema declared.
No examples provided.
util_json_unique_fields_check ~171
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | yes | – |
| items | array | yes | – |
No output schema declared.
No examples provided.
util_json_url_fields_check ~174
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | yes | – |
| object | object | yes | – |
No output schema declared.
No examples provided.
util_json_uuid_fields_check ~172
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | yes | – |
| object | object | yes | – |
No output schema declared.
No examples provided.
util_json_validate ~35
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | – |
No output schema declared.
No examples provided.
util_jsonld_key_list ~45
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
No output schema declared.
No examples provided.
util_jwt_claims_audit ~56
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| claims | object | yes | – |
| now_epoch | number | yes | – |
No output schema declared.
No examples provided.
util_jwt_claims_humanize ~35
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| jwt | string | yes | – |
No output schema declared.
No examples provided.
util_jwt_exp_seconds ~32
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | – |
No output schema declared.
No examples provided.
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.