Singularity Layer MCP

REMOTE · MCP.X402LAYER.CC · SCANNED AUG 3

MCP for Singularity Layer - discover listings, manage assets, run payment flows, and use agents

Available components

+2 this week 52 52 Trust /100

Trust breakdown (6 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 →

Endpoint Security46

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 38 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 not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
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 Usability45

0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 4569 tokens (~106/item across 43 items; 38 tools + 5 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities20

Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.x402layer.cc

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http ivaavimusic-singularity https://mcp.x402layer.cc/mcp

# ~/.codex/config.toml

[mcp_servers.ivaavimusic-singularity]
url = "https://mcp.x402layer.cc/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ivaavimusic-singularity": {
      "type": "remote",
      "url": "https://mcp.x402layer.cc/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add ivaavimusic-singularity --url https://mcp.x402layer.cc/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  ivaavimusic-singularity:
    url: "https://mcp.x402layer.cc/mcp"

// mcp.json

{
  "mcpServers": {
    "ivaavimusic-singularity": {
      "type": "http",
      "url": "https://mcp.x402layer.cc/mcp"
    }
  }
}

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.

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
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
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 49

First indexed and scored.

Show 5 earlier entries Hide earlier entries

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 3 Aug 2026 · Probed https://mcp.x402layer.cc/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=x402layer.cc	CN=WE1,O=Google Trust Services,C=US	9 Jul 2026	7 Oct 2026	ECDSA 256	ECDSA-SHA256	962a7aab157531820ed2f8846c967a46
SANs: x402layer.cc, mcp.x402layer.cc
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

DNSSEC insecure

Validation of mcp.x402layer.cc. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
cc.	present	12593	13	Verified
x402layer.cc.	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

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mcp.x402layer.cc/mcp	Verified	200
http (plaintext)	http://mcp.x402layer.cc/mcp	Inconclusive	405

MCP tools — 38 exposed · ~4,540 tokens

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.

Tool Tokens

browse_marketplace ~178

Browse and search the Singularity Marketplace with various filters. Returns listings of endpoints, products, and agentic services.

Input Output Examples

Name	Type	Req	Description
category	string	—	Category to filter by
chain	string	—	Blockchain network to filter by
featured	boolean	—	Only return featured listings
limit	number	—	Maximum number of results (default: 20)
maxPrice	number	—	Maximum price filter
minPrice	number	—	Minimum price filter
minRating	number	—	Minimum average rating (0-5)
mode	string	—	Payment mode filter
offset	number	—	Pagination offset (default: 0)
search	string	—	Search term to find matching listings
sort	string	—	Sort order
type	string	—	Type of listing to filter by

No output schema declared.

No examples provided.

create_campaign ~264

Create a fundraiser campaign owned by the dashboard user behind your MCP personal access token. Requires mcp:campaigns:write or mcp:*.

Input Output Examples

Name	Type	Req	Description
accessToken	string	yes	Your dashboard MCP personal access token (sgl_pat_*)
bagsConfigType	string	—	Optional Bags fee tier config UUID
category	string	—	Category label
clientReferenceId	string	—	Optional client reference alias for idempotency
deadline	string	—	ISO datetime deadline
description	string	—	Campaign description
feeOption	string	—	Fee share option
feeSplitPct	number	—	Creator split percentage when feeOption=split
idempotencyKey	string	—	Optional idempotency key for safe retries
images	array	—	Up to 5 HTTPS image URLs
links	—	—	Optional campaign links array
subcategory	string	—	Subcategory label
targetAmount	number	yes	Funding target in USDC
title	string	yes	Campaign title
tokenTicker	string	—	2-10 uppercase alphanumeric ticker
walletAddress	string	yes	Solana payout wallet for creator disbursal
xHandle	string	—	Optional X handle without @

No output schema declared.

No examples provided.

create_endpoint_with_payment ~296

Create a new agent endpoint after you have obtained a valid X-Payment payload for the creation challenge. Requires a dashboard PAT with mcp:endpoints:write or mcp:*.

Input Output Examples

Name	Type	Req	Description
accessToken	string	yes	Your dashboard MCP personal access token (sgl_pat_*)
bannerUrl	string	—	Endpoint banner URL
category	string	—	Marketplace category
chain	string	yes	Primary payout network, usually base, solana, or both
currency	string	—	Payout currency, default USDC
description	string	—	Endpoint description
imageUrl	string	—	Endpoint image URL
listOnMarketplace	boolean	—	Whether to list the endpoint publicly
mode	string	—	Pricing mode
name	string	yes	Human-readable endpoint name
originUrl	string	yes	Origin URL of the endpoint backend
paymentPayload	—	yes	Raw X-Payment payload returned by the paying client, as JSON or base64 string
price	number	—	Price per request or base package price
purchaseAmount	number	—	USDC amount to pay on creation, minimum 5
slug	string	yes	Unique slug for the new endpoint
walletAddress	string	yes	Primary payout wallet address
walletAddressSecondary	string	—	Secondary wallet when chain is both
webhookUrl	string\|null	—	Optional HTTPS webhook URL

No output schema declared.

No examples provided.

delete_endpoint ~113

⚠️ DESTRUCTIVE: Permanently delete an endpoint. Cannot be undone. Only works for agent-created endpoints. PATs are preferred and require mcp:endpoints:write or mcp:*.

Input Output Examples

Name	Type	Req	Description
accessToken	string	—	Your dashboard MCP personal access token (sgl_pat_*)
apiKey	string	—	Legacy endpoint API key (x402_*)
confirm	boolean	yes	Must be true to confirm deletion
slug	string	yes	The unique slug identifier for the endpoint to delete

No output schema declared.

No examples provided.

finalize_agent_registration ~73

Finalize a wallet-first agent registration after the on-chain transaction has been sent from the same wallet.

Input Output Examples

Name	Type	Req	Description
payload	object	yes	Raw finalize payload expected by the worker, including network, stage, and transaction hash/signature fields
sessionToken	string	yes	Wallet session token with erc8004_register scope

No output schema declared.

No examples provided.

finalize_agent_update ~107

Finalize a wallet-first update for an existing ERC-8004 or Solana-8004 agent after any required on-chain transaction has been sent from the same wallet.

Input Output Examples

Name	Type	Req	Description
payload	object	yes	Raw finalize payload expected by the worker, including network plus agentId or assetAddress and any txHash/txSignature/tokenUri fields
sessionToken	string	yes	Wallet session token with erc8004_manage, erc8004_update, or erc8004_register scope

No output schema declared.

No examples provided.

get_agent ~86

Get details for a specific ERC-8004 or Solana-8004 agent by network and identifier.

Input Output Examples

Name	Type	Req	Description
agentId	number	—	The numeric agent ID (for EVM chains)
assetAddress	string	—	The asset address (for Solana)
network	string	yes	The blockchain network (base, ethereum, polygon, bsc, monad, solana)

No output schema declared.

No examples provided.

get_agent_registry_info ~36

Get public ERC-8004 / Solana-8004 registry information, supported networks, worker routes, and wallet-first notes.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_endpoint_details ~93

Get full details for an endpoint you own, including credit balance, pricing config, and wallet address. PATs are preferred and require mcp:read or mcp:*.

Input Output Examples

Name	Type	Req	Description
accessToken	string	—	Your dashboard MCP personal access token (sgl_pat_*)
apiKey	string	—	Legacy endpoint API key (x402_*)
slug	string	yes	The unique slug identifier for the endpoint

No output schema declared.

No examples provided.

get_endpoint_stats ~96

Get usage analytics for an endpoint: total requests, monthly requests, revenue, and success rate. PATs or endpoint API keys improve accuracy. PATs require mcp:read or mcp:*.

Input Output Examples

Name	Type	Req	Description
accessToken	string	—	Your dashboard MCP personal access token (optional)
apiKey	string	—	Legacy endpoint API key (optional, improves accuracy)
slug	string	yes	The unique slug identifier for the endpoint

No output schema declared.

No examples provided.

get_featured ~42

Get featured marketplace listings (endpoints and products highlighted by the platform).

Input Output Examples

Name	Type	Req	Description
limit	number	—	Maximum number of featured items to return (default: 12)

No output schema declared.

No examples provided.

get_listing ~34

Get detailed information about a specific marketplace listing by its slug.

Input Output Examples

Name	Type	Req	Description
slug	string	yes	The unique slug identifier for the listing

No output schema declared.

No examples provided.

get_top_rated ~40

Get top-rated marketplace listings sorted by average rating.

Input Output Examples

Name	Type	Req	Description
limit	number	—	Maximum number of top-rated items to return (default: 12)

No output schema declared.

No examples provided.

list_agents ~61

List all registered ERC-8004 and Solana-8004 agents.

Input Output Examples

Name	Type	Req	Description
limit	number	—	Maximum results (default: 50)
network	string	—	Filter by network
offset	number	—	Pagination offset (default: 0)

No output schema declared.

No examples provided.

list_categories ~14

List all available marketplace categories.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_my_agent_bindable_endpoints ~68

List platform endpoints owned by the authenticated wallet or linked dashboard user that can be bound to ERC-8004 agents.

Input Output Examples

Name	Type	Req	Description
listedOnly	boolean	—	Return only active/listed endpoints
sessionToken	string	yes	Wallet session token returned by verify_agent_wallet_challenge

No output schema declared.

No examples provided.

list_my_campaigns ~70

List fundraiser campaigns owned by the dashboard user behind your MCP personal access token. Requires mcp:read or mcp:*.

Input Output Examples

Name	Type	Req	Description
accessToken	string	yes	Your dashboard MCP personal access token (sgl_pat_*)
slug	string	—	Optional campaign slug to fetch a single owned campaign

No output schema declared.

No examples provided.

list_my_endpoints ~82

List the endpoints accessible to the dashboard owner behind your MCP access token or endpoint API key. PATs are preferred for owner-wide inventory and require mcp:read or mcp:*.

Input Output Examples

Name	Type	Req	Description
accessToken	string	—	Your dashboard MCP personal access token (sgl_pat_*)
apiKey	string	—	Legacy endpoint API key (x402_*)

No output schema declared.

No examples provided.

list_my_products ~78

List the products owned by the same dashboard user as your MCP access token or endpoint API key. PATs are preferred and require mcp:read or mcp:*.

Input Output Examples

Name	Type	Req	Description
accessToken	string	—	Your dashboard MCP personal access token (sgl_pat_*)
apiKey	string	—	Legacy endpoint API key (x402_*)

No output schema declared.

No examples provided.

list_my_registered_agents ~60

List ERC-8004 or Solana-8004 agents owned by the authenticated wallet or linked dashboard user.

Input Output Examples

Name	Type	Req	Description
network	string	—	Optional network filter
sessionToken	string	yes	Wallet session token returned by verify_agent_wallet_challenge

No output schema declared.

No examples provided.

list_networks ~15

List all supported blockchain networks.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

prepare_agent_registration ~190

Prepare a wallet-first ERC-8004 or Solana-8004 registration. The caller must later send the on-chain transaction from the same wallet and then call finalize_agent_registration.

Input Output Examples

Name	Type	Req	Description
assetAddress	string	—	Required for Solana registrations
customEndpoints	array	—	Custom endpoint URLs to bind
description	string	yes	Agent description
endpoint	string	—	Primary or fallback endpoint URL
endpointIds	array	—	Platform endpoint UUIDs to bind
image	string	—	Agent image URL
name	string	yes	Agent name
network	string	yes	Target network for the agent
ownerAddress	string	—	Owner wallet address matching the authenticated session wallet
sessionToken	string	yes	Wallet session token with erc8004_register scope
tags	array	—	Agent tags
version	string	—	Agent version string

No output schema declared.

No examples provided.

prepare_agent_update ~105

Prepare a wallet-first update for an existing ERC-8004 or Solana-8004 agent. If metadata changes require an on-chain URI update, the response describes that action.

Input Output Examples

Name	Type	Req	Description
payload	object	yes	Raw update payload expected by the worker, including network plus agentId or assetAddress and the requested fields to change
sessionToken	string	yes	Wallet session token with erc8004_manage, erc8004_update, or erc8004_register scope

No output schema declared.

No examples provided.

purchase_endpoint_credits_with_payment ~126

Complete a public endpoint credit-pack purchase after you have obtained a valid X-Payment payload for the purchase challenge.

Input Output Examples

Name	Type	Req	Description
clientReferenceId	string	—	Optional client reference ID forwarded to the purchase flow
metadata	object	—	Optional metadata object forwarded to the purchase flow
paymentPayload	—	yes	Raw X-Payment payload returned by the paying client, as JSON or base64 string
slug	string	yes	Endpoint slug for the credit-enabled endpoint
walletAddress	string	—	Optional wallet address to receive the purchased credits when the underlying endpoint supports it

No output schema declared.

No examples provided.

purchase_product_with_payment ~114

Complete a public product purchase after you have obtained a valid X-Payment payload for that product challenge.

Input Output Examples

Name	Type	Req	Description
clientReferenceId	string	—	Optional client reference ID forwarded to the purchase flow
metadata	object	—	Optional metadata object forwarded to the purchase flow
paymentPayload	—	yes	Raw X-Payment payload returned by the paying client, as JSON or base64 string
productIdOrSlug	string	yes	Product slug or product ID used in the public /p/:id-or-slug purchase route

No output schema declared.

No examples provided.

remove_webhook ~83

Remove the webhook URL from an endpoint. PATs are preferred and require mcp:endpoints:write or mcp:*.

Input Output Examples

Name	Type	Req	Description
accessToken	string	—	Your dashboard MCP personal access token (sgl_pat_*)
apiKey	string	—	Legacy endpoint API key (x402_*)
slug	string	yes	The unique slug identifier for the endpoint

No output schema declared.

No examples provided.

request_agent_wallet_challenge ~96

Create a wallet-auth challenge for ERC-8004 agent registration or management. The wallet owner must sign the returned message locally; MCP does not sign with the wallet.

Input Output Examples

Name	Type	Req	Description
action	string	—	Session scope to request
chain	string	yes	Wallet auth chain
payload	object	—	Optional payload object to bind into the signed challenge
walletAddress	string	yes	Wallet address that will sign the challenge

No output schema declared.

No examples provided.

request_endpoint_creation_payment ~267

Return the x402 payment challenge needed to create a new agent endpoint. Requires a dashboard PAT with mcp:endpoints:write or mcp:*.

Input Output Examples

Name	Type	Req	Description
accessToken	string	yes	Your dashboard MCP personal access token (sgl_pat_*)
bannerUrl	string	—	Endpoint banner URL
category	string	—	Marketplace category
chain	string	yes	Primary payout network, usually base, solana, or both
currency	string	—	Payout currency, default USDC
description	string	—	Endpoint description
imageUrl	string	—	Endpoint image URL
listOnMarketplace	boolean	—	Whether to list the endpoint publicly
mode	string	—	Pricing mode
name	string	yes	Human-readable endpoint name
originUrl	string	yes	Origin URL of the endpoint backend
price	number	—	Price per request or base package price
purchaseAmount	number	—	USDC amount to pay on creation, minimum 5
slug	string	yes	Unique slug for the new endpoint
walletAddress	string	yes	Primary payout wallet address
walletAddressSecondary	string	—	Secondary wallet when chain is both
webhookUrl	string\|null	—	Optional HTTPS webhook URL

No output schema declared.

No examples provided.

request_endpoint_credit_purchase_payment ~105

Return the x402 payment challenge for purchasing a public credit pack from an endpoint that exposes /e/:slug?action=purchase.

Input Output Examples

Name	Type	Req	Description
clientReferenceId	string	—	Optional client reference ID forwarded to the purchase flow
metadata	object	—	Optional metadata object forwarded to the purchase flow
slug	string	yes	Endpoint slug for the credit-enabled endpoint
walletAddress	string	—	Optional wallet address to receive the purchased credits when the underlying endpoint supports it

No output schema declared.

No examples provided.

request_endpoint_topup_payment ~120

Return the x402 payment challenge needed to top up credits for an existing agent endpoint. Accepts either a dashboard PAT with mcp:endpoints:write or mcp:* or a legacy endpoint API key.

Input Output Examples

Name	Type	Req	Description
accessToken	string	—	Your dashboard MCP personal access token (sgl_pat_*)
apiKey	string	—	Legacy endpoint API key (x402_*)
slug	string	yes	Slug of the endpoint to top up
topupAmount	number	yes	USDC amount to add, minimum 1

No output schema declared.

No examples provided.

request_product_purchase_payment ~103

Return the x402 payment challenge for purchasing a public product. This wraps the existing public /p/:id-or-slug flow and does not require owner credentials.

Input Output Examples

Name	Type	Req	Description
clientReferenceId	string	—	Optional client reference ID forwarded to the purchase flow
metadata	object	—	Optional metadata object forwarded to the purchase flow
productIdOrSlug	string	yes	Product slug or product ID used in the public /p/:id-or-slug purchase route

No output schema declared.

No examples provided.

set_webhook ~108

Set or update the webhook URL for an endpoint. Returns a signing secret that must be saved. PATs are preferred and require mcp:endpoints:write or mcp:*.

Input Output Examples

Name	Type	Req	Description
accessToken	string	—	Your dashboard MCP personal access token (sgl_pat_*)
apiKey	string	—	Legacy endpoint API key (x402_*)
slug	string	yes	The unique slug identifier for the endpoint
webhookUrl	string	yes	HTTPS URL to receive webhook events

No output schema declared.

No examples provided.

submit_agent_feedback ~155

Submit on-chain ERC-8004 or Solana-8004 reputation feedback through the worker feedback route. This requires the separate worker feedback API key, not a wallet session token.

Input Output Examples

Name	Type	Req	Description
agentId	number	—	EVM agent id
apiKey	string	yes	Worker feedback API key
assetAddress	string	—	Solana asset address
comment	string	—	Optional feedback comment
endpoint	string	—	Optional endpoint context string
network	string	yes	Target network for the feedback
rating	number	yes	Rating from 1 to 5
tag1	string	—	Primary tag, default overall
tag2	string	—	Secondary tag, default agentic

No output schema declared.

No examples provided.

topup_endpoint_with_payment ~143

Complete an endpoint credit top-up after you have obtained a valid X-Payment payload. Accepts either a dashboard PAT with mcp:endpoints:write or mcp:* or a legacy endpoint API key.

Input Output Examples

Name	Type	Req	Description
accessToken	string	—	Your dashboard MCP personal access token (sgl_pat_*)
apiKey	string	—	Legacy endpoint API key (x402_*)
paymentPayload	—	yes	Raw X-Payment payload returned by the paying client, as JSON or base64 string
slug	string	yes	Slug of the endpoint to top up
topupAmount	number	yes	USDC amount to add, minimum 1

No output schema declared.

No examples provided.

update_campaign ~124

Update allowlisted fundraiser campaign fields such as title, description, x handle, images, and links. Requires mcp:campaigns:write or mcp:*.

Input Output Examples

Name	Type	Req	Description
accessToken	string	yes	Your dashboard MCP personal access token (sgl_pat_*)
description	string	—	Updated campaign description
images	array	—	Updated HTTPS image URLs
links	—	—	Updated campaign links array
slug	string	yes	Campaign slug to update
title	string	—	Updated campaign title
xHandle	string	—	Updated X handle without @

No output schema declared.

No examples provided.

update_endpoint ~340

Update allowlisted endpoint fields such as metadata, pricing, listing flags, imagery, wallet, payment options, slug, and webhook settings. PATs are preferred and require mcp:endpoints:write or mcp:*.

Input Output Examples

Name	Type	Req	Description
accessToken	string	—	Your dashboard MCP personal access token (sgl_pat_*)
active	boolean	—	Enable or disable the endpoint
apiKey	string	—	Legacy endpoint API key (x402_*)
bannerUrl	string	—	Updated banner URL
category	string	—	Updated category
chain	string	—	Updated chain/network
creditPackagePrice	number	—	Package price in USDC
creditPackageSize	number	—	Credits per package
currency	string	—	Updated currency code
description	string	—	Updated description
imageUrl	string	—	Updated image URL
isListed	boolean	—	Whether the endpoint should be listed
listedInMarketplace	boolean	—	Whether the endpoint should appear in marketplace listings
logoUrl	string	—	Updated logo URL
mode	string	—	Pricing mode
name	string	—	Updated endpoint name
newSlug	string	—	New slug to assign to the endpoint
originUrl	string	—	Updated origin URL
paymentOptions	—	—	Updated payment options object
price	number	—	Updated endpoint price
slug	string	yes	The existing slug of the endpoint you want to update
walletAddress	string	—	Updated payout wallet address
webhookUrl	string\|null	—	Set an HTTPS webhook URL or null to remove it

No output schema declared.

No examples provided.

update_product ~326

Update allowlisted product fields including metadata, pricing, listing state, payment options, wallet, branding, and slug. PATs are preferred and require mcp:products:write or mcp:*.

Input Output Examples

Name	Type	Req	Description
accessToken	string	—	Your dashboard MCP personal access token (sgl_pat_*)
active	boolean	—	Enable or disable the product
apiKey	string	—	Legacy endpoint API key (x402_*)
bannerUrl	string	—	Updated banner URL
category	string	—	Updated product category
chain	string	—	Updated chain/network
currency	string	—	Updated currency code
customButtonBg	string	—	Custom button background color
customButtonText	string	—	Custom button text color
customFont	string	—	Custom font family
customPageBg	string	—	Custom page background color
customPageText	string	—	Custom page text color
description	string	—	Updated product description
id	string	—	Product ID to update
isListed	boolean	—	Whether the product should be listed
logoUrl	string	—	Updated logo URL
name	string	—	Updated product name
newSlug	string	—	New slug to assign to the product
paymentOptions	—	—	Updated payment options object
price	number	—	Updated product price
productImageUrl	string	—	Updated product image URL
slug	string	—	Product slug to update
walletAddress	string	—	Updated payout wallet address

No output schema declared.

No examples provided.

verify_agent_wallet_challenge ~129

Verify a wallet-signed auth challenge and receive a short-lived session token for agent registry flows.

Input Output Examples

Name	Type	Req	Description
action	string	—	Session scope originally requested
chain	string	yes	Wallet auth chain
nonce	string	yes	Nonce returned by request_agent_wallet_challenge
payload	object	—	Optional payload object that was part of the original challenge
signature	string	yes	Wallet signature over the challenge message
signatureEncoding	string	—	hex for EVM, base64 for Solana
walletAddress	string	yes	Wallet address that signed the challenge

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	49
27 Jul	50
28 Jul	50
29 Jul	51
30 Jul	51
31 Jul	51
1 Aug	51
2 Aug	52
3 Aug	52