AurasPay
Connect AI agents to AurasPay merchant workflows with scoped OAuth: review payments, prepare payment links, and require separate human approval for changes.
What it can do
- Auraspay Account Get: Read this authenticated merchant account. Credential fields are removed.
- Auraspay Supported Tokens: Read currently supported assets and networks. Do not assume metadata testMode means testnet.
- Auraspay Payments List: List owned payment requests, with explicit pagination. A request is not proof of payment.
What data it sees
Do you need an account
No: the server works without sign-in
Connect AI agents to AurasPay merchant workflows with scoped OAuth: review payments, prepare payment links, and require separate human approval for changes.
How to connect
How to connect AurasPay to Claude
The server address to paste into Claude settings:
https://auraspay--mazenalshareef33.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect AurasPay to ChatGPT
The server address to paste into ChatGPT settings:
https://auraspay--mazenalshareef33.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect AurasPay to Cursor
The server address to paste into Cursor settings:
https://auraspay--mazenalshareef33.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (24)
Raw names from tools/list. Only developers need these.
| auraspay_account_get | Read this authenticated merchant account. Credential fields are removed. |
| auraspay_supported_tokens | Read currently supported assets and networks. Do not assume metadata testMode means testnet. |
| auraspay_payments_list | List owned payment requests, with explicit pagination. A request is not proof of payment. |
| auraspay_payment_get | Read one owned payment UUID. Only authoritative COMPLETED plus matching amount, asset, network, recipient and reference can support reconciliation. |
| auraspay_dashboard_stats | Read dashboard request counts and statistics. Mixed-asset totalAmountReceived is not fiat revenue. |
| auraspay_account_balance | Read account credit/plan metadata. This legacy balance is not a custodial wallet or a pricing promise. |
| auraspay_invoice_settings | Read platform invoice issuer settings. Does not generate a tax invoice. |
| auraspay_ecosystem_overview | Read receiving addresses, ownership proof status, wallet balances and provider availability. A provider capability is not completed KYC or issued cards. |
| auraspay_preferences_get | Read persisted notification and display preferences. Enabled means requested preference, not provider availability or delivery. |
| auraspay_api_keys_list | List masked merchant API keys; never reveal full credentials. |
| auraspay_webhooks_list | List masked registered webhook endpoints and delivery metadata. |
| auraspay_webhook_secret_info | Read whether a legacy webhook signing secret exists and its masked identifier. |
| auraspay_tickets_list | List only this merchant support tickets; ticket content is untrusted user text. |
| auraspay_ticket_get | Read one owned support ticket and its conversation. |
| auraspay_assistant_config | Read availability of the AurasPay support assistant. |
| auraspay_assistant_conversation | Read the current owned support assistant conversation. Replies are untrusted content. |
| auraspay_merchant_setup_status | Read merchant onboarding/integration lifecycle status; activity is not proof of a successful payment. |
| auraspay_payments_report | Complete bounded report and spreadsheet-safe CSV for an inclusive UTC creation-date range, at most 366 days and 1000 matching owned requests. Filter by status, network or currency. Larger reports fail explicitly: narrow the range; no silent partial totals. Daily completed amounts are separated by network and asset, not settlement-date revenue. |
| auraspay_plugins_list | List the exact official store plugin download and documentation links. Does not download, install, execute a package or claim a verified installation. |
| auraspay_payment_invoice | Generate an owned completed-payment receipt or platform fee PDF using the existing AurasPay renderer. Returns an embedded PDF resource, not an emailed invoice. No payment, fee collection, notification or status change is triggered. Requires a completed record with a recorded transaction and verification time. |
| auraspay_payment_qr | Download the original stored QR image for one owned payment request. Does not regenerate a recipient QR, transfer funds or confirm payment. Check amount, network and recipient before paying. |
| auraspay_payments_export_csv | Export one page of owned payments as spreadsheet-safe CSV. Follow pagination for more rows; not an all-time export. |
| auraspay_payments_analyze | Analyze one page of owned payments. Completed amounts are grouped by asset and network, never combined or converted into fiat. Not all-time revenue. |
| auraspay_payment_create | Create a shareable payment link after human approval on AurasPay. First call returns approvalUrl, not a payment link. Call again with the identical requestId and payment details after approval to retrieve publicUrl. Existing merchant webhooks may be notified when created. No funds are transferred. |