eCommerce
astrasync.shop
Provides tools to browse products and initiate purchases from astrasync.shop.
ENDPOINT 1
https://astrasync.shop/mcp
Known tools 3
start_checkoutSubmit a purchase via one of the supported agentic-commerce protocols.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.astrasync-shop]
url = "https://astrasync.shop/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"astrasync-shop": {
"type": "http",
"url": "https://astrasync.shop/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: astrasync-shop
Remote MCP URL: https://astrasync.shop/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"astrasync-shop": {
"url": "https://astrasync.shop/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"astrasync-shop": {
"type": "http",
"url": "https://astrasync.shop/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "astrasync-shop",
"transport": "streamable-http",
"url": "https://astrasync.shop/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for astrasync.shop was fetched 2026-07-31T17:50:20.124Z and is being refreshed.
astrasync.shop is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.