Next free-source huntWe check for new free data every weekday.
FinancialMCP serverFirst audited Nov 13, 2026

OurPay Wallet

Crypto wallet for AI agents: balances, payments, swaps and trading with owner controls.The vendor's description, from its MCP Registry listing.

Sign-in required: limited auditAudited Nov 13, 2026

Sign-in stopped the tool checks. We checked the connection, encryption and how sign-in works. Public audit: we connect as an AI client would, list the tools and check what they say. We do not run them. How we audit

Does it work?
YesIt connects.
Sign-up?
RequiredYou need an account or key from the provider.
Can it change things?
UnknownIts tools are behind sign-in.
Endpointhttps://mcp.ourpay.dev/wallet/mcp

Source code Website Streamable HTTP

What we checked, the evidence, and the tools it offers.

What we checked

Security

  • Passed: Connections are encrypted (HTTPS).

Sign-in

  • Note: Sign-in is required to use this server.

    The server answered HTTP 401 to an unauthenticated client. The public audit stops here: tool checks need an account.

    • WWW-Authenticate: Bearer resource_metadata="https://mcp.ourpay.dev/.well-known/oauth-protected-resource/wallet/mcp", scope="agent_wallets:read agent_wallets:spend"
  • Passed: The sign-in method is discoverable, as the MCP spec describes.

    • authorization server: https://api.ourpay.dev/v1/agent-wallets/oauth

Connection

  • Passed: The server responds.

Audit history

  1. Nov 13Sign-in

What we sent

Every request in this audit, with the answer and how long it took. We never send credentials and never call a tool.

RequestAnswerTime
initializeHTTP 401426 ms
auth-metadataHTTP 200376 ms

Run this server, or disagree with the result?

Fix the issue and it shows in the next weekly audit, or email us to ask for a re-audit or to dispute a finding. Read how we audit for what each check means.