Connection Tokens
Every MCP request to Vinkius Cloud is authenticated by a connection token — a named, HMAC-SHA256 credential that binds a client to a specific server. Tokens are the access control layer that sits between your AI clients and your infrastructure.
Most MCP platforms either rely on static API keys stored in environment variables or have no authentication at all. Vinkius Cloud provides per-server, named, instantly revocable tokens with usage tracking and plan-based quotas — the level of credential management you expect from production infrastructure.
Token list
The Connection Tokens tab displays all active tokens for the current server:
Token fields
| Field | Description |
|---|---|
| Client | Human-readable name you assign at creation (e.g., cursor-main, ci-pipeline, mobile-app) |
| Token | Masked hint showing only the last 4 characters — the full value is never stored or displayed again |
| Last Used | Relative timestamp of the most recent authenticated request via this token |
| Actions | Revoke button for immediate invalidation |
Generating a token
Click Generate to create a new token. Provide a descriptive name that identifies the client or use case:
Show-once disclosure
The full token value is displayed exactly once at creation. It is returned directly from the API response and never persisted in the database. After you close the modal or navigate away, the token cannot be recovered — you must generate a new one.
After creation, the modal displays:
- The full token — Copy it immediately. This is the only time it will be visible.
- The MCP URL — The complete
https://edge.vinkius.com/{token}/mcpendpoint, ready to paste into any AI client. - Quick Connect — Client-specific instructions with one-click copy for Cursor, Claude Desktop, and Antigravity.
Quick Connect
Immediately after generating a token, the Quick Connect panel opens with client-specific instructions:
Supported clients
| Tab | Client | Integration |
|---|---|---|
| Cursor / VSCode | Cursor, VS Code with Copilot, Windsurf | Paste the SSE URL directly into MCP settings |
| Claude Desktop | Claude Desktop | Add to mcpServers object in the JSON config file |
| Antigravity | Antigravity (Vinkius AI) | Paste the SSE URL into the MCP server field |
Plan-based quotas
Token creation is governed by your subscription plan:
| Plan | Max Tokens per Server |
|---|---|
| Free | 1 |
| Developer | 3 |
| Team | 10 |
| Business | 25 |
When you reach your plan limit, the Generate button is disabled and an upgrade notice appears. The quota counter (2 / 10 TOKENS) is always visible in the token list footer and header.
Token revocation
Click Revoke on any token to permanently invalidate it. Revocation is:
- Immediate — The token is deleted from the database and a
mcp:invalidateevent is published via Redis pub/sub in the same request - Propagated — Active SSE connections authenticated with the revoked token are terminated within milliseconds through the Kill Switch mechanism
- Irreversible — Once revoked, the token hash is removed. There is no "undo" or "suspend" — only delete and regenerate
- Audited — The revocation event appears in the Audit Logs
Token rotation
To rotate a token without downtime, generate a new token first, update your client configuration, then revoke the old token. Because tokens are per-server and independently named, you can run multiple active tokens during the transition window.
Security model
HMAC-SHA256 authentication
Every token is hashed with HMAC-SHA256 before storage. The database never contains plaintext credentials — only the hash is persisted. On each request, the incoming token is hashed and compared against stored hashes.
Token-based routing
The MCP URL format is https://edge.vinkius.com/{token}/mcp. The token in the URL path is both the routing key (identifying which server to proxy to) and the authentication credential. There is no separate server ID or API key — one value handles both concerns.
No credential leakage
- Show-once — Plaintext token returned only in the creation response
- Hint only — After creation, only the last 4 characters are visible
- No export — Token values cannot be retrieved, exported, or listed in plaintext
- Redis pub/sub — Revocation events propagate through the real-time messaging layer, not through polling
Marketplace isolation
When a server is listed on the Marketplace, buyers receive their own provisioned tokens through a separate system. Seller tokens and buyer tokens are completely isolated — one cannot access the other's credentials or see each other's token list.
Next steps
Frequently Asked Questions
How does HMAC-SHA256 token authentication work?
Every connection token is hashed with HMAC-SHA256 before storage. The database never contains plaintext credentials. On each MCP request, the incoming token is hashed and compared against stored hashes. This means even a database breach cannot expose token credentials.
Can I recover a lost connection token?
No. Tokens use show-once disclosure — the full value is displayed exactly once at creation and never persisted in the database. If you lose a token, generate a new one and update your AI client configuration. The old token can be safely revoked.
How many tokens can I create per server?
Token quotas depend on your plan: Free (1 token), Developer (3 tokens), Team (10 tokens), Business (25 tokens). The quota counter is always visible in the token list footer. When you reach your limit, the Generate button is disabled with an upgrade notice.
What AI clients support Quick Connect?
Quick Connect provides client-specific configuration for Cursor, VS Code with Copilot, Claude Desktop, Windsurf, ChatGPT, Cline, Continue, Zed, and Antigravity. Each tab shows the exact steps and configuration format for that client. The SSE URL is included in the copy-paste ready config.
Is token revocation instant?
Yes. Revocation is immediate and propagated via Redis pub/sub. The token hash is deleted from the database, active SSE connections using the revoked token are terminated within milliseconds, and the event is recorded in the Audit Log. There is no grace period.
Can seller and buyer tokens access each other?
No. When a server is listed on the Marketplace, buyer tokens and seller tokens are completely isolated. One cannot access the other's credentials or see each other's token list. This ensures marketplace privacy and prevents cross-tenant access.