Hilt

Hilt PayMe MCP Connector

OAuth-gated remote MCP resource at https://api.hilt.so/mcp/pay-me for compatible AI clients: resolve a verified PayMe handle, start a wallet-approved SOL or Solana USDC payment (the client prepares terms; the payer signs in their own wallet), read activity, and create/cancel payment links. Authorization is OAuth authorization-code with PKCE S256 and dynamic client registration on the issuer https://api.hilt.so (RFC 8414 + RFC 9728 metadata published), scopes pay_me:read, pay_me:request, pay_me:prepare. Anonymous tools/list answers 401 with a resource_metadata challenge; the ten tool names come from the docs.

GitHub

Documentation

📖
Authentication
https://raw.githubusercontent.com/api-evangelist/hilt-so/refs/heads/main/authentication/hilt-so-authentication.yml
📖
Documentation
https://docs.hilt.so/developers/pay-me-mcp

Other Resources

🔗
MCPServer
https://raw.githubusercontent.com/api-evangelist/hilt-so/refs/heads/main/mcp/hilt-so-pay-me-mcp.yml
🔗
MCPServer
https://api.hilt.so/mcp/pay-me
🔗
OAuthScopes
https://raw.githubusercontent.com/api-evangelist/hilt-so/refs/heads/main/scopes/hilt-so-scopes.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/payme-mcp"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑ 
aid: hilt-so:payme-mcp
name: Hilt PayMe MCP Connector
description: 'OAuth-gated remote MCP resource at https://api.hilt.so/mcp/pay-me for compatible AI clients:
  resolve a verified PayMe handle, start a wallet-approved SOL or Solana USDC payment (the client prepares
  terms; the payer signs in their own wallet), read activity, and create/cancel payment links. Authorization
  is OAuth authorization-code with PKCE S256 and dynamic client registration on the issuer https://api.hilt.so
  (RFC 8414 + RFC 9728 metadata published), scopes pay_me:read, pay_me:request, pay_me:prepare. Anonymous
  tools/list answers 401 with a resource_metadata challenge; the ten tool names come from the docs.'
image: https://www.hilt.so/Logo.png
humanURL: https://docs.hilt.so/developers/pay-me-mcp
baseURL: https://api.hilt.so/mcp/pay-me
tags:
- MCP
- Authentication
- Solana
- USDC
- Payments
- PayMe
tags_raw:
- MCP
- OAuth
- Solana
- USDC
- Payments
- PayMe
properties:
- type: MCPServer
  url: mcp/hilt-so-pay-me-mcp.yml
- type: MCPServer
  url: https://api.hilt.so/mcp/pay-me
  name: Live MCP endpoint (OAuth-gated, probed 401)
- type: OAuthScopes
  url: scopes/hilt-so-scopes.yml
- type: Authentication
  url: authentication/hilt-so-authentication.yml
- type: Documentation
  url: https://docs.hilt.so/developers/pay-me-mcp