What Cuely receives
Cuely never sees your code. Your agent reads your project on your own machine and sends Cuely a sentence about the product and a list of tool names. This page shows exactly what that looks like, what Cuely keeps, and how to check it yourself.
Last updated November 20, 2026
What your agent sends
Cuely is a remote MCP server. It can't open files, run commands or read your repository: it only sees what your agent puts in the call. When you ask "check my stack", the agent reads package.json and your config files locally, then sends something like this:
{
"tool": "check_project",
"arguments": {
"description": "Next.js app where therapists keep patient notes, now adding EU customers",
"using": ["Vercel", "Supabase", "Clerk", "Stripe", "Resend"]
}
}That's the whole request: a plain description of the product (at most 2,000 characters) and tool names (at most 40). Some tools also take a few fixed choices, such as web or phone app and who pays whom. The full input of every tool is in src/mcp/server.ts.
What Cuely never asks for
- Source code or the contents of any file
- Environment variable values, API keys or other secrets
- Git history, file paths or your repository's name
Cuely's instructions to agents say so in plain words: send the product in plain words and tool names, never code, file contents, env values, secrets, or the names of people, customers or companies. The description is free text, so if an agent adds more than it should, that text is used for that one answer and then dropped.
What Cuely keeps
For each call, one row with these five fields and nothing else:
- which tool was called, such as
check_project - which recipe it matched, such as
b2b-saas, if any - which categories the answer covered, such as hosting and auth
- which needs Cuely detected, from a fixed list such as
euorhealth_data - a short hash of your account that changes every day, so Cuely can count unique callers per day without being able to follow anyone from one day to the next
Cuely does not keep the description, the tool list, the comparison context or your IP address. It also counts your account's calls per day and per minute to apply your plan's limits. See the table in db/schema.sql, the code that writes it in src/mcp/server.ts, and the test that calls every tool with marked text and fails if any of it is stored, in tests/mcp.test.ts.
What passes through without being kept
Vercel hosts Cuely, so your request passes through Vercel's network on its way to the server. When something breaks, Cuely's error log records the path and the error, and leaves out request bodies and headers on purpose (instrumentation.ts). The full list of services and what each one handles is in the privacy policy.
Check it yourself
- Before it's sent: Claude Code and most MCP clients show the exact arguments of a tool call and ask you to allow it. Read the payload, then allow or deny it.
- On the server: the code that runs cuely.dev is public at https://github.com/migueljdias/cuely. The MCP server is in
src/mcp, the scoring insrc/engineand every vendor fact, with its source page and date, insrc/cataloganddata. - Run it yourself: you can run your own copy of Cuely for your own use, so nothing leaves your network at all. The README shows how.
Source and licenses
Cuely's code is published under the Functional Source License (FSL-1.1-ALv2): you can read, run, change and self-host it for any purpose except offering a competing service, and each version becomes Apache 2.0 two years after it's published. The catalog (vendor facts, prices, recipes and measurements) is published under CC BY-NC 4.0. Using Cuely's answers in your own projects, commercial or not, is always fine.
Found something that doesn't match this page? Email cuely-support@googlegroups.com or open an issue on GitHub. See SECURITY.md for security reports.