Hilt Pay Agent Commerce
REMOTE · API.HILT.SO
x402 V2 payment-to-access on Solana USDC with receipts, entitlements, atomic metering and webhooks.
Available components
Last scanned (10 minutes ago)
Scores higher than 10% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 yet verified: we couldn't confirm whether this endpoint requires it. 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 14 Oct 26 −50
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 5 Nov 2026 · Probed https://api.hilt.so/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hilt.so | CN=YE2,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 639ac798b1f8bc46936c8584606590b96bb |
| SANs: admin.hilt.so, api.hilt.so, app.hilt.so, docs.hilt.so, hilt.so, pay.hilt.so, www.hilt.so | ||||||
| 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.hilt.so. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| so. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 503 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.hilt.so/mcp | HTTP error | 503 | |
| http (plaintext) | http://api.hilt.so/mcp | HTTPS enforced | 301 | https://api.hilt.so/mcp |
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 →
hilt_activate_growth Activate Hilt Pay API Growth ~63
Activate 30 days of Hilt Pay API growth for 349 USDC on Solana. Requires a free Agent Bootstrap setup intent.
| Name | Type | Req | Description |
|---|---|---|---|
| delivery_claim | string | yes | – |
| setup_intent_id | string | yes | – |
| setup_token | string | yes | – |
No output schema declared.
No examples provided.
hilt_activate_scale Activate Hilt Pay API Scale ~64
Activate 30 days of Hilt Pay API scale for 1250 USDC on Solana. Requires a free Agent Bootstrap setup intent.
| Name | Type | Req | Description |
|---|---|---|---|
| delivery_claim | string | yes | – |
| setup_intent_id | string | yes | – |
| setup_token | string | yes | – |
No output schema declared.
No examples provided.
hilt_activate_starter Activate Hilt Pay API Starter ~64
Activate 30 days of Hilt Pay API starter for 79 USDC on Solana. Requires a free Agent Bootstrap setup intent.
| Name | Type | Req | Description |
|---|---|---|---|
| delivery_claim | string | yes | – |
| setup_intent_id | string | yes | – |
| setup_token | string | yes | – |
No output schema declared.
No examples provided.
hilt_agent_bootstrap Hilt Pay Agent Bootstrap ~94
Create a free sandbox setup intent and scoped sandbox key. Live activation remains an explicit paid step.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | – |
| agent_platform | string | – | – |
| contact_email | string | – | – |
| external_reference | string | – | – |
| metadata | object | – | – |
| requested_permissions | array | – | – |
| requested_use_case | string | – | – |
| ttl_hours | integer | – | – |
No output schema declared.
No examples provided.
hilt_claim_api_key Claim Hilt Pay API Key ~59
Recover live API-key delivery after a settled marketplace plan activation.
| Name | Type | Req | Description |
|---|---|---|---|
| delivery_claim | string | yes | – |
| purchase_intent_id | string | yes | – |
| setup_intent_id | string | yes | – |
| setup_token | string | yes | – |
No output schema declared.
No examples provided.
hilt_create_quote Create Hilt Pay Quote ~59
Create a deterministic quote and recommended Hilt buying path without charging the buyer.
| Name | Type | Req | Description |
|---|---|---|---|
| current_payment_flow | string | – | – |
| product_description | string | – | – |
| product_url | string | – | – |
| target_marketplace | string | – | – |
No output schema declared.
No examples provided.
hilt_get_catalog Get Hilt Pay Catalog ~23
Get the canonical Hilt Pay agent-commerce catalog and discovery endpoints.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hilt_get_offer Get Hilt Pay Offer ~29
Get Hilt's canonical agent-commerce offer, interfaces, products, prices, and buying paths.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hilt_get_pricing Get Hilt Pay Pricing ~22
Get canonical Hilt Pay API pricing and activation paths.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Hilt Pay Agent Commerce MCP server?
Hilt Pay Agent Commerce is a hosted endpoint at https://api.hilt.so/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 · api.hilt.so
claude mcp add --transport http so-hilt-agent-commerce 'https://api.hilt.so/mcp'
What is the Hilt Pay Agent Commerce MCP server?
Hilt Pay Agent Commerce is an MCP server listed in the public MCP registry as so.hilt/agent-commerce. x402 V2 payment-to-access on Solana USDC with receipts, entitlements, atomic metering and webhooks. This page covers its hosted endpoint (https://api.hilt.so/mcp).
Is the Hilt Pay Agent Commerce MCP server safe to use?
Hilt Pay Agent Commerce scores 25 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 Hilt Pay Agent Commerce MCP server expose?
Hilt Pay Agent Commerce exposes 9 tools: hilt_get_offer, hilt_get_catalog, hilt_get_pricing, hilt_create_quote, hilt_agent_bootstrap, and 4 more. Their descriptions and schemas cost roughly 477 tokens of context every time the server is loaded.
Does the Hilt Pay Agent Commerce MCP server require authentication?
Its publisher declares no required credentials for Hilt Pay Agent Commerce. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Hilt Pay Agent Commerce MCP server still maintained?
Hilt Pay Agent Commerce is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.