Blue Cap Machine Commerce
REMOTE · MACHINE.SOUNDIQ.IO · SCANNED SEP 24
Deterministic MCP utilities, validation, evidence verification, and x402 commerce on Base.
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 Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability58
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 491 tokens (~70/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 8% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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 Blue Cap Machine Commerce MCP server?
Blue Cap Machine Commerce is a hosted endpoint at https://machine.soundiq.io/mcp, 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 · machine.soundiq.io
claude mcp add --transport http io-soundiq-bluecap-evidence-verify 'https://machine.soundiq.io/mcp'
{
"mcpServers": {
"io-soundiq-bluecap-evidence-verify": {
"url": "https://machine.soundiq.io/mcp"
}
}
} {
"servers": {
"io-soundiq-bluecap-evidence-verify": {
"type": "http",
"url": "https://machine.soundiq.io/mcp"
}
}
} [mcp_servers.io-soundiq-bluecap-evidence-verify] url = "https://machine.soundiq.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-soundiq-bluecap-evidence-verify": {
"type": "remote",
"url": "https://machine.soundiq.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-soundiq-bluecap-evidence-verify --url 'https://machine.soundiq.io/mcp' --transport streamable-http
mcp_servers:
io-soundiq-bluecap-evidence-verify:
url: "https://machine.soundiq.io/mcp" {
"McpServers": {
"io-soundiq-bluecap-evidence-verify": {
"Transport": "http",
"Url": "https://machine.soundiq.io/mcp"
}
}
} assistant mcp add io-soundiq-bluecap-evidence-verify -t streamable-http -u 'https://machine.soundiq.io/mcp'
{
"mcpServers": {
"io-soundiq-bluecap-evidence-verify": {
"type": "http",
"url": "https://machine.soundiq.io/mcp"
}
}
} 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.
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 0
- Schema quality: 266 → 491 ▼ functional
- New tool “evidence_verify_mpp” functional
- New tool “hash_compute_mpp” functional
- New tool “schema_validate_mpp” functional
- 11 Sept 26 −1
- Tool “evidence_verify” rewrote its description, which is the text the model reads security
- Schema quality: 86 → 66 ▲ functional
- Schema quality: good → fair functional
- New tool “agent_wallet” 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 24 Sept 2026 · Probed https://machine.soundiq.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=soundiq.io | CN=WE1,O=Google Trust Services,C=US | 22 Aug 2026 | 20 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 9c75d856f6b0bcea0eba448729d858d8 |
| SANs: soundiq.io, machine.soundiq.io, *.machine.soundiq.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of machine.soundiq.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| soundiq.io. | 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 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://machine.soundiq.io/mcp | Verified | 200 | |
| http (plaintext) | http://machine.soundiq.io/mcp | Inconclusive | 405 |
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 →
agent_wallet Blue Cap agent.wallet ~31
Provision a free Blue Cap machine wallet (Base Mainnet, USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| agent_id | string | yes | – |
No examples provided.
evidence_verify Blue Cap evidence.verify ~53
Verify supplied structured evidence and return a machine-readable verification result.
| Name | Type | Req | Description |
|---|---|---|---|
| assurance_record | object | yes | – |
| consumer_id | string | yes | – |
| evidence_artifacts | object | yes | – |
| invocation_context | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| capability_result | object | yes | – |
| commercial_receipt | object | yes | – |
| storefront_authority | object | yes | – |
| x402_settlement | object | yes | – |
No examples provided.
evidence_verify_mpp Blue Cap evidence.verify — Stripe MPP ~74
Return a Stripe MPP payment link for this Blue Cap capability. POST the same arguments to paymentLink to receive the HTTP 402 challenge and complete payment.
| Name | Type | Req | Description |
|---|---|---|---|
| assurance_record | object | yes | – |
| consumer_id | string | yes | – |
| evidence_artifacts | object | yes | – |
| invocation_context | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| instructions | string | yes | – |
| method | – | yes | – |
| paymentLink | string | yes | – |
| paymentProtocol | – | yes | – |
| price | object | yes | – |
| provider | – | yes | – |
| requestBody | object | yes | – |
No examples provided.
hash_compute Blue Cap hash.compute ~75
Compute a SHA-256 digest for customer-supplied UTF-8 or base64-decoded bytes through a stable machine endpoint. Returns the reproducible digest through a receipted external execution.
| Name | Type | Req | Description |
|---|---|---|---|
| consumer_id | string | yes | – |
| data | string | yes | – |
| encoding | – | yes | – |
| invocation_context | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| capability_result | object | yes | – |
| commercial_receipt | object | yes | – |
| storefront_authority | object | yes | – |
| x402_settlement | object | yes | – |
No examples provided.
hash_compute_mpp Blue Cap hash.compute — Stripe MPP ~69
Return a Stripe MPP payment link for this Blue Cap capability. POST the same arguments to paymentLink to receive the HTTP 402 challenge and complete payment.
| Name | Type | Req | Description |
|---|---|---|---|
| consumer_id | string | yes | – |
| data | string | yes | – |
| encoding | – | yes | – |
| invocation_context | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| instructions | string | yes | – |
| method | – | yes | – |
| paymentLink | string | yes | – |
| paymentProtocol | – | yes | – |
| price | object | yes | – |
| provider | – | yes | – |
| requestBody | object | yes | – |
No examples provided.
schema_validate Blue Cap schema.validate ~88
Validate supplied structured data against a customer-supplied JSON Schema Draft 2020-12 supported subset. Returns a deterministic machine-readable validity result and bounded errors through a receipted external execution.
| Name | Type | Req | Description |
|---|---|---|---|
| consumer_id | string | yes | – |
| invocation_context | object | yes | – |
| schema | object | yes | JSON Schema using the published Draft 2020-12 supported subset. |
| value | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| capability_result | object | yes | – |
| commercial_receipt | object | yes | – |
| storefront_authority | object | yes | – |
| x402_settlement | object | yes | – |
No examples provided.
schema_validate_mpp Blue Cap schema.validate — Stripe MPP ~82
Return a Stripe MPP payment link for this Blue Cap capability. POST the same arguments to paymentLink to receive the HTTP 402 challenge and complete payment.
| Name | Type | Req | Description |
|---|---|---|---|
| consumer_id | string | yes | – |
| invocation_context | object | yes | – |
| schema | object | yes | JSON Schema using the published Draft 2020-12 supported subset. |
| value | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| instructions | string | yes | – |
| method | – | yes | – |
| paymentLink | string | yes | – |
| paymentProtocol | – | yes | – |
| price | object | yes | – |
| provider | – | yes | – |
| requestBody | object | yes | – |
No examples provided.
What is the Blue Cap Machine Commerce MCP server?
Blue Cap Machine Commerce is an MCP server listed in the public MCP registry as io.soundiq/bluecap-evidence-verify. Deterministic MCP utilities, validation, evidence verification, and x402 commerce on Base. This page covers its hosted endpoint (https://machine.soundiq.io/mcp).
Is the Blue Cap Machine Commerce MCP server safe to use?
Blue Cap Machine Commerce scores 78 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.
What tools does the Blue Cap Machine Commerce MCP server expose?
Blue Cap Machine Commerce exposes 7 tools: evidence_verify, agent_wallet, schema_validate, hash_compute, evidence_verify_mpp, and 2 more. Their descriptions and schemas cost roughly 472 tokens of context every time the server is loaded.
Does the Blue Cap Machine Commerce MCP server require authentication?
No. We connected to Blue Cap Machine Commerce without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Blue Cap Machine Commerce MCP server still maintained?
Blue Cap Machine Commerce is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.