Weio site check vs Magic MCP
A side-by-side look at the Weio site check and Magic MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
W
Weio site checkDeveloper Tools · Local subprocess (stdio)Website facts for agents: HTTPS/certificate checks, public site info, small local-business search.40FairAuth: not declaredVerdict: choose Weio site check for developer tools work as a local process; choose Magic MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
WChoose Weio site check when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Choose Magic MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TWENTY_FIRST_API_KEY, API_KEY_21ST.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W Weio site check | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 40/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Paid service |
| Required env vars | None listed |
Tools & capabilities
Weio site check tools
No tool names declared yet. Check the project README from the listing page.
Magic MCP 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.
Weio site check
{
"mcpServers": {
"weio-site-check": {
"command": "npx",
"args": [
"-y",
"@stripe/link-cli"
]
}
}
}
Magic MCP
{
"mcpServers": {
"21st-dev-magic-mcp": {
"command": "npx",
"args": [
"-y",
"@21st-dev/cli@latest"
],
"env": {
"TWENTY_FIRST_API_KEY": "YOUR_TWENTY_FIRST_API_KEY_HERE",
"API_KEY_21ST": "YOUR_API_KEY_21ST_HERE"
}
}
}
}
Frequently asked questions
Weio site check is categorized under Developer Tools and uses a local stdio subprocess. Magic MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Weio site check for developer tools work and Magic MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Weio site check has no declared pricing — check the project's own site. Magic MCP is listed as a paid service. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add weio-site-check and 21st-dev-magic-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Weio site check has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Magic MCP has 53/100 (Good) with 16 views, 1 installs and 5,997 GitHub stars.
