eCommerce
ai2aihandoff.com
Manages vendor quote workflows by listing priced catalog items, scoping work, locking signed quotes, and tracking payment receipts.
ENDPOINT 1
https://ai2aihandoff.com/mcp
MCP server metadata
- Name
- seamless-handoff
- Version
- 0.1.0
Quote work from this vendor on behalf of your human. Use interpret_request to turn a plain-English need into catalog items (or list_catalog to browse), scope_work to build and revise a scope, request_quote to lock a signed 30-minute price, then hand the returned pay_url to your human. There is deliberately no payment tool: only a person in a browser can complete payment. Poll check_receipt for the receipt afterwards.
Known tools 5
list_catalogList the priced items this vendor can quote, with unit prices and minimum quantities.
Inferred read-onlycheck_receiptCheck whether the human has paid a quote yet, and fetch the receipt once they have.
Inferred read-onlyCONNECT 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.seamless-handoff]
url = "https://ai2aihandoff.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"seamless-handoff": {
"type": "http",
"url": "https://ai2aihandoff.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: seamless-handoff
Remote MCP URL: https://ai2aihandoff.com/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": {
"seamless-handoff": {
"url": "https://ai2aihandoff.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"seamless-handoff": {
"type": "http",
"url": "https://ai2aihandoff.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "seamless-handoff",
"transport": "streamable-http",
"url": "https://ai2aihandoff.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.