Tin vs Valid
A side-by-side look at the Tin and Valid MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Tin for marketing work over a hosted endpoint; choose Valid for marketing. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Tin when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | V Valid | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 45/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 264 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Tin | View Valid |
Tools & capabilities
Tin tools
No tool names declared yet. Check the project README from the listing page.
Valid tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Tin
{
"mcpServers": {
"tin": {
"url": "https://app.tin.computer/mcp"
}
}
}
Valid
No confirmed install command for Valid yet — follow the setup steps linked from its listing page rather than a guessed package name.