MCP is quite complicated, so we decided to make it easy with native auth and hosted MCP connections and a single configuration step. Works with any client that supports MCP (like Cursor, Claude, Zed, ChatGPT, etc)
Do you auto-generate specific MCP tools for the repo? Curious what the queries you would use with an AI agent to get a response back.
I'm building my own hosted MCP solution (https://skeet.build) and have been deliberately choosing which tools to expose depending on the use case- since there are tool limits due to the context window for apps like Cursor.
There are numerous outfits that you can go to online to order blank checks. And of the small number that I have used, all of them let me just type in my routing number and account number and other information that appears printed on the check.
Your use of Plaid would exclude me from your service for two reasons:
1: I bank at a small regional credit union that is almost impossible to get linked with Plaid.
2: Plaid hypothetically lets you do a lot more than just learn my account and routing number. I would not trust a new start up with that level of access.
Given that relatively few things require the MICR numbers to be printed with magnetized ink anymore, it’s not clear what fraud someone could commit with your service that they couldn’t commit just as easily commit in a dozen different ways and that we can’t really prevent without a systematic overhaul of the paper check system
Varo is one. But even the ones that do support it like "Chime" have online comments like this:
"Chime is great for everything else, but their check features are absolute trash and will cause you frustration. Just don't do it and find another option."
> Do you restrict writing checks that are for an amount greater than the current account balance? Lastly, I’m wondering how you handle deliberate check fraud. Victims will try to sue all associated parties. How does your liability work in those cases?
That is one of our fraud signals. We have systems in place to review payment amounts, address, frequency, etc that can cause additional KYC checks to be preformed via Plaid before we'll send the check.
> Cash App us a lump of cash and we’ll send it somewhere by check
Funny thing about sending checks is it's just an account and routing number in a special font on a piece of paper. We don't touch any customer funds.
> Am I missing something that differentiates what you do from what they do?
We have a simpler UI with a focus just on sending the check, so having your contacts prefilled make it quick and easy. But, if your bank already supports this then probably not for you!
If we grow the app enough, we'll add more features like scheduled / recurring payments and tracking for delivery and when the check is deposited.
> Funny thing about sending checks is it's just an account and routing number in a special font on a piece of paper. We don't touch any customer funds.
Oh that’s so cool! I hadn’t even thought about that operational aspect. Very clever: I guess that means you’re an easy, slick option for customers from an awfully long list of banks and neobanks with varying quality of native products.
Let us know what you think!