AurasPay Merchant MCP

com.auraspayPublished by auraspay.comOfficial publisherv0.1.3Updated Nov 5, 2026

Review AurasPay merchant payments and prepare payment links with scoped OAuth and human approval.

VerifiedStreamable HTTPWeb executableFinanceData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Hosted, OAuth-protected MCP server that lets an assistant read an AurasPay merchant account's payments, reports and settings and prepare merchant actions for…

What you can do
  • Read merchant profile, balance counters, supported tokens, preferences and setup status
  • List, read and verify owned payment requests, plus retrieve stored QR images and invoice or fee PDFs
  • Export a payment page as CSV, analyze payment activity and build bounded reports or dashboard statistics
  • Prepare payment links, profile changes, qualification and referral actions for separate approval in AurasPay
  • Manage receiving wallets: create an ownership challenge, verify a signature and disconnect an address
  • Handle support tickets and assistant conversations, and review or revoke API keys and webhooks
When to use it
Useful when a merchant wants an AI assistant to review AurasPay payment activity, produce reports or exports, or draft payment links and support replies, while keeping approvals and secret handling inside the AurasPay dashboard.
Requirements
A remote Streamable HTTP endpoint with OAuth (PKCE and Dynamic Client Registration) completed in the client browser. A merchant AurasPay account and consent to the requested scopes; tool availability depends on the scopes granted. No environment variables or headers are declared.
Before you install
The server can prepare changes such as payment links, profile updates, ticket replies, webhook creation and key or webhook revocation; these require separate human review in AurasPay, and revoking a key or webhook stops integrations and notifications. It handles wallet ownership signatures and API-key creation, though secrets are shown only inside AurasPay. A payment link is a request, not proof of funds; only COMPLETED status supports reconciliation, and test mode is metadata only. AurasPay…

Installation

In SourceWeft

  1. Open AurasPay Merchant MCP 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/com.auraspay%2Fmerchant-payments/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": {
    "auraspay-merchant": {
      "type": "http",
      "url": "https://mcp.auraspay.com/api/mcp"
    }
  }
}

README

AurasPay Merchant MCP

[MCP Badge]

AurasPay Merchant MCP connects compatible AI applications to an AurasPay merchant account through a hosted, OAuth-protected Model Context Protocol server.

It can read scoped merchant and payment information, export or analyze bounded payment data, and prepare supported merchant actions. Creating a payment link or changing merchant data requires a separate authenticated review in AurasPay.

Connect

Remote MCP URL:

text
https://mcp.auraspay.com/api/mcp

Use this official endpoint directly. Smithery's connection management services closed on October 31, 2026; replace any previous Smithery proxy URL or CLI setup with the direct URL above and complete OAuth in your client.

Codex

sh
codex mcp add auraspay --url https://mcp.auraspay.com/api/mcpcodex mcp login auraspay

Restart the Codex desktop app or IDE extension after adding the server. Use /mcp to confirm the connection.

Claude Code

sh
claude mcp add --transport http --scope user auraspay https://mcp.auraspay.com/api/mcp

Open /mcp inside Claude Code and complete authentication in the browser.

Gemini CLI

Install the AurasPay extension directly from the official public repository:

sh
gemini extensions install https://github.com/AurasPayOfficial/auraspay-mcp-docs

Restart Gemini CLI, run /mcp auth auraspay, and complete OAuth in the browser.

Visual Studio Code

Install AurasPay in VS Code

You can also install it from a terminal:

sh
code --add-mcp '{"name":"auraspay","type":"http","url":"https://mcp.auraspay.com/api/mcp"}'

For a workspace installation, copy .vscode/mcp.json into your project. Run MCP: List Servers, start auraspay, trust the server, and complete OAuth in the browser.

GitHub Copilot CLI

sh
copilot mcp add --transport http auraspay https://mcp.auraspay.com/api/mcpcopilot mcp list

Complete OAuth when prompted. To configure it manually for your user account, merge examples/github-copilot-mcp-config.json into ~/.copilot/mcp-config.json. The root .mcp.json is also ready for project-level Copilot CLI use after folder trust is confirmed.

Devin

For Devin Local, which is the default agent in new Devin Desktop tabs:

sh
devin mcp add --scope user auraspay https://mcp.auraspay.com/api/mcpdevin mcp login auraspaydevin mcp get auraspay

Complete OAuth in the browser when prompted. A copy-ready configuration for ~/.config/devin/mcp_config.json is available at examples/devin-mcp_config.json.

Legacy Cascade uses the Windsurf configuration described below. Team administrators can also add AurasPay through Settings > MCP Marketplace > Add Your Own, select HTTP and OAuth, enter the remote MCP URL, save it, and run Test listing tools.

Cursor

Add AurasPay to Cursor

For a manual installation, merge this entry into ~/.cursor/mcp.json for all projects, or into .cursor/mcp.json inside one project:

json
{  "mcpServers": {    "auraspay": {      "url": "https://mcp.auraspay.com/api/mcp"    }  }}

Open Cursor > Customize > MCPs, connect auraspay, and complete OAuth in the browser. Cursor Agent CLI users can run cursor-agent mcp login auraspay after saving the configuration.

Windsurf / legacy Devin Desktop Cascade

Merge this entry into ~/.codeium/windsurf/mcp_config.json:

json
{  "mcpServers": {    "auraspay": {      "serverUrl": "https://mcp.auraspay.com/api/mcp"    }  }}

In Windsurf or legacy Cascade, open the MCPs menu (or Settings > Cascade > MCP Servers), select auraspay, and complete OAuth in the browser. A copy-ready configuration is available at examples/windsurf-mcp_config.json.

Cline

sh
cline mcp add --transport http --yes auraspay https://mcp.auraspay.com/api/mcp

Complete OAuth in the browser when Cline prompts you to authorize AurasPay. The unauthenticated MCP endpoint intentionally returns 401 Unauthorized together with OAuth discovery metadata; that response means the protected server is reachable and authentication must be completed, not that the service is down.

For automated availability checks that do not complete OAuth, use:

text
https://mcp.auraspay.com/health

It returns HTTP 200 with {"live":true} while the MCP gateway is available. See llms-install.md for the complete Cline validation flow.

Other clients

Choose Streamable HTTP, paste the remote MCP URL, and select OAuth when prompted. The client must support remote Streamable HTTP MCP, OAuth with PKCE, and Dynamic Client Registration.

Tools

ToolDescription
auraspay_account_getRead the authenticated merchant profile.
auraspay_account_balanceRead legacy dashboard counters; this is not a wallet balance.
auraspay_supported_tokensList the assets and networks currently allowed for the account.
auraspay_payments_listList owned payment requests with pagination.
auraspay_payment_getRead one owned payment request.
auraspay_payment_qrRetrieve the original stored QR image without regenerating it.
auraspay_payment_invoiceRetrieve a completed-payment receipt or platform-fee PDF when available.
auraspay_invoice_settingsRead invoice issuer settings without creating default records.
auraspay_payments_export_csvExport a selected payment page as spreadsheet-safe CSV.
auraspay_payments_analyzeAnalyze a selected page of payment activity.
auraspay_payments_reportBuild a complete bounded report using creation-date and payment filters.
auraspay_dashboard_statsRead owned payment counts and completed totals.
auraspay_payment_createPrepare a payment link request for separate authenticated merchant approval.
auraspay_payment_verifyVerify an owned pending payment after its transaction signature is reviewed.
auraspay_profile_updateReview profile changes before approving them in AurasPay.
auraspay_merchant_qualifyReview store and country details before recording merchant qualification.
auraspay_preferences_getRead persisted notification, language, currency, theme and animation choices.
auraspay_preferences_updatePersist selected preferences after native review.
auraspay_referrals_openReview before opening or initializing the owned referral program.
auraspay_ecosystem_overviewReview linked wallets, cached balances and service readiness.
auraspay_wallet_ownership_challengeCreate a short-lived wallet ownership message to sign.
auraspay_wallet_ownership_verifyVerify the signature and save the exact receiving address.
auraspay_wallet_disconnectRemove one verified receiving address from AurasPay.
auraspay_tickets_listList owned support tickets with pagination.
auraspay_ticket_getRead one owned ticket and up to its first 200 messages.
auraspay_assistant_conversationRead the latest open support conversation and its first 50 messages.
auraspay_assistant_configRead assistant configuration availability; this is not a provider health check.
auraspay_ticket_set_statusClose or reopen one owned ticket after native review.
auraspay_ticket_createReview and send a new support ticket in AurasPay.
auraspay_ticket_replyReview and send a reply to an owned support ticket.
auraspay_assistant_messageReview and send one message to the support assistant or provider.
auraspay_plugins_listList official store-plugin downloads and documentation.
auraspay_api_keys_listRead masked API-key metadata, never full keys or hashes.
auraspay_webhooks_listRead webhook endpoint and delivery metadata, never secrets or destination URLs.
auraspay_webhook_secret_infoCheck whether a legacy signing secret exists without exposing it.
auraspay_merchant_setup_statusRead recorded setup events; these are not proof of a live installation.
auraspay_api_key_revokeRevoke one key after native review; integrations using it will stop.
auraspay_webhook_revokeRevoke one endpoint after native review; notifications to it will stop.
auraspay_api_key_createApprove one-time API-key creation and display the secret only inside AurasPay, never in AI output.
auraspay_webhook_createReview a public HTTPS destination before creating a webhook.
auraspay_webhook_testReview and send one signed test event without automatically retrying an uncertain delivery.

Tool availability is permission-aware. The authenticated tools/list response is authoritative for the current release and the scopes granted by the merchant. A tool listed above appears only when its required scope was requested during consent, granted by the merchant and enabled by AurasPay.

Safety model

  • OAuth permissions are scoped and controlled by the merchant.
  • Supported changes require a separate human review in AurasPay.
  • A payment link is a payment request, not a transfer or proof that funds were received.
  • Only authoritative COMPLETED status with matching payment details supports reconciliation.
  • AurasPay never asks an MCP client for a wallet recovery phrase or private key.
  • Test mode is metadata; it does not select a sandbox or testnet.

Documentation and support

Scope of this repository

This public repository contains distribution metadata, client configuration and documentation for the hosted AurasPay Merchant MCP service. It does not contain production server source, credentials or merchant data.

Regulatory boundary

AurasPay provides non-custodial software and technical infrastructure. AurasPay is not a bank, issuer, custodian or investment adviser. Availability can depend on jurisdiction and independent providers. Review the current legal pages above for details.

Source: README.md at commit c7fa31f

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

3
  1. v0.1.3LatestNov 5, 2026
  2. v0.1.2Sep 17, 2026
  3. v0.1.1Sep 16, 2026

Score

85% 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
  • License10 pts