Hilt PayMe

so.hiltPublished by hilt.soOfficial publisherv1.1.1Updated Oct 24, 2026

Wallet-approved SOL and Solana USDC payments to verified X handles, with zero custody.

The publisher's own server: Hilt Pay Agent Commerce

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

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.

What you can do
Send SOL or Solana USDC payments to verified X handles, with each payment approved in the user's wallet rather than held by the service. The server is described as non-custodial, so funds stay under the user's wallet control. No individual tools are listed in the supplied material, so exact operations beyond payment sending are not documented.
When to use it
Useful when an assistant needs to pay a person identified by a verified X handle in SOL or Solana USDC, and the user wants to approve each transfer from their own wallet.
Requirements
A remote endpoint at api.hilt.so over streamable HTTP. OAuth authentication is required. A Solana wallet able to approve transactions, and funds in SOL or USDC, are needed to complete payments. No environment variables or headers are declared.
Before you install
This server moves real money: payments in SOL or USDC are irreversible once confirmed on-chain. Every transfer should be reviewed and approved in the wallet, and the recipient's verified X handle checked before sending. OAuth grants access to the account; review the scopes requested. The service is described as non-custodial, but the supplied material does not detail how approvals or verification work.

Installation

In SourceWeft

  1. Open Hilt PayMe in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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%2Fpay-me/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "hilt-payme": {
      "type": "http",
      "url": "https://api.hilt.so/mcp/pay-me"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.1LatestSep 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 listed15 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