Where it fits
Developers building autonomous M2M agents that need HTTP 402 protected settlement in USDC on Base L2.
- Protect an autonomous agent endpoint with an HTTP 402 turnstile.
- Settle micro-payments in USDC on Base L2.
- Run M2M services behind MilliGate Sovereign.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with MilliGate Sovereign
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Investigates a question against high-trust primary sources and records the findings in a Markdown file inside the repo. Use it when a topic needs research, docs or API facts need gathering, or reading legwork should go to a background agent.
Show recorded token use, cache reads, and mode attribution for the current Claude Code session.
Improves application speed across the frontend, backend, database, and query layers. Reach for it when a performance target exists, a regression is suspected, Core Web Vitals or load times need work, N+1 queries need fixing, or profiling has exposed a bottleneck.
No skills found
Try a different search term or clear the filters.
Install it in your client
Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses SSE.
- 01
Run this command in your terminal
This adds MilliGate Sovereign as a remote SSE server in Claude Code.
Claude Codeclaude mcp add --transport sse milligate-sovereign https://mcp.milligate.io/sse --scope project - 02
Verify the connection
Run claude mcp list, or open /mcp in a Claude Code session.
Learn more about MCP in Claude Code
- 01
Install with one click
This opens Cursor with the server pre-filled. Review the connection before accepting it.
Install in Cursor - 02
Verify the connection
Open Cursor's MCP settings and enable the server if it is not active.
Learn more about MCP in Cursor
- 01
Install with one click
This opens VS Code with the server pre-filled. Review the connection before accepting it.
Install in VS Code - 02
Verify the connection
Run MCP: List Servers from the Command Palette and start the server.
Learn more about MCP in VS Code
- 01
Open Claude settings
Open Settings, choose Connectors, add a custom connector, and paste the hosted endpoint. Complete the provider sign-in when prompted.
Open Claude settings - 02
Verify the connection
Return to a chat, open the connector menu, and confirm the server tools appear.
Learn more about MCP in Claude
More clients, including project and global config files, are in the sidebar.
Endpoint and configuration
The installer uses the server name milligate-sovereign. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
milligate-sovereignappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Protect an autonomous agent endpoint with an HTTP 402 turnstile. Check the result before you give the server more access.
- 3Check permissions.
Confirm the provider's credential model before relying on scopes or key permissions. Remove the server and revoke any token when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
- The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
- Your client only supports Streamable HTTP. Use a client that supports SSE or the provider's HTTP endpoint.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider documentation
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
MilliGate Sovereign documentationhttps://milligate.io/