ENDPOINT 1
https://usevig.com/mcp
MCP server metadata
- Name
- usevig
- Version
- 0.1.0
The active product uses CREATE2 checkouts. Start with create_merchant on Base Sepolia. Then call create_checkout. The payer sends an ordinary token transfer. usevig watches the chain. The merchant signs collection and pays collection gas.
Known tools 10
get_planYour tier, status (pending/active/past_due/expired), expiry, and whether you can create mainnet checkouts.
Potential side effectsupdate_accountChange account settings in place — you never need a new account to accept different chains or tokens.
Inferred read-onlyget_checkoutRead a checkout: status, which finality level it has reached, observed transfers, and any shortfall if the payer underpaid.
Inferred read-onlyget_collect_quoteBuild an UNSIGNED transaction that sweeps your received funds to your payout address.
Inferred read-onlyget_uncollected_balanceHow much has been paid to you but not yet swept to your payout address, per chain and token.
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.usevig]
url = "https://usevig.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"usevig": {
"type": "http",
"url": "https://usevig.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: usevig
Remote MCP URL: https://usevig.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": {
"usevig": {
"url": "https://usevig.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"usevig": {
"type": "http",
"url": "https://usevig.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "usevig",
"transport": "streamable-http",
"url": "https://usevig.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.