
Venmo
io.github.markswendsen-codePublished by GitHub account markswendsen-codev0.1.0Updated Oct 24, 2026
MCP server for Venmo - check balance, send/request money, view history
Overview
Deprecated Venmo connector that used browser automation with user credentials to check balance, send or request money, and view history; withdrawn by its…
- What you can do
- Check Venmo balance and view transaction history
- Send money and request payments through the Venmo account
- Automate Venmo, PayPal and Cash App access using stored user credentials
- Note: the publisher states the package has been pulled and should not be run
- When to use it
- Not recommended for any use. The publisher deprecated it and asks users to stop running it, rotate their password and review recent account activity.
- Requirements
- A local Node.js runtime for the npm package, plus Venmo account credentials supplied to the connector; the manifest declares no environment variables or headers.
Installation
In SourceWeft
- Open Venmo in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
⚠️ DEPRECATED — DO NOT USE
Status: This connector has been pulled by Strider Labs as of June 5, 2026.
Why
This package automated Venmo / PayPal / Cash App access using browser automation with user credentials. We have concluded this is unsafe for users:
- Terms of Service. Automated/unauthorized access violates the user agreements of these services.
- Account suspension risk. These platforms can — and do — permanently suspend accounts they suspect of automation, and may freeze funds and linked bank accounts. Appeals are difficult or impossible.
- Credential exposure. Storing financial-service credentials in MCP client configs creates an unacceptable security surface.
- Regulatory category. Money-transmitter services operate under fraud-prevention regimes (BSA/AML) that are fundamentally hostile to bot traffic — different from commerce platforms.
Strider Labs policy
We do not ship credential-handover MCP connectors for regulated financial services. Strider Labs builds connectors for commerce platforms (food delivery, travel, reservations) that work with — not against — the operator's terms.
If you used this package
- Stop running it.
- Rotate your account password.
- Review recent Venmo/PayPal/Cash App activity for anything you didn't authorize.
- If your account was flagged, contact the platform's support — we cannot intervene.
What's next
We are evaluating safer architectures (OAuth-only, no credential handover, sanctioned partner APIs) for financial connectors. We will not re-publish browser-automation versions.
— Strider Labs, June 5, 2026
Source: README.md at commit c035cdb
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
40% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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
Declare a license in the repository or the registry entry.