Hilt Pay Agent Commerce
so.hiltPublished by hilt.soOfficial publisherv1.1.0Updated Oct 24, 2026
x402 V2 payment-to-access on Solana USDC with receipts, entitlements, atomic metering and webhooks.
Overview
A remote MCP endpoint that lets an assistant handle x402 V2 payment-to-access flows on Solana USDC, including receipts, entitlements, metering and webhooks.
- What you can do
- Hilt Pay Agent Commerce is a remote MCP server reached at a hosted endpoint. According to its registry description, it covers x402 V2 payment-to-access on Solana USDC, with receipts, entitlements, atomic metering and webhooks. No individual tools are listed in the supplied material, so the exact operations an assistant can call are not documented here.
- When to use it
- Consider it when an assistant needs to take part in paid access flows settled in Solana USDC, for example granting access after payment, issuing receipts, tracking metered usage, or reacting to webhook events. It is not useful if you only need read-only Solana data or general blockchain queries.
- Requirements
- A remote streamable HTTP endpoint at The manifest declares no authentication, no environment variables and no headers, and no packages. A Solana USDC context and whatever access the service expects are implied by the description but not specified.
Installation
In SourceWeft
- Open Hilt Pay Agent Commerce in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/so.hilt%2Fagent-commerce/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"hilt-pay-agent-commerce": {
"type": "http",
"url": "https://api.hilt.so/mcp"
}
}
}Tools
0Version history
1- v1.1.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
Other Hilt integrations
Hilt PayMe
so.hiltOfficial publisher
A remote MCP server that lets an assistant send wallet-approved SOL and Solana USDC payments to verified X handles, without the server holding funds.

ChainHilt Wallet
ai.chainhilt
Local crypto wallet MCP server that lets an assistant check balances, authorize ChainHilt API requests, and sign or send verified on-chain actions.