Magicsword MCP vs PageLens AI
A side-by-side look at the Magicsword MCP and PageLens AI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
Magicsword MCPSecurity · Local subprocess (stdio)Manage MagicSword endpoints, alerts, policies, and private intelligence through MCP.53GoodAuth: api key requiredVerdict: choose Magicsword MCP for security work as a local process; choose PageLens AI for security over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
MChoose Magicsword MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
MAGICSWORD_API_KEY, MAGICSWORD_BASE_URL. - You want tools like
whoami, list_endpoints, show_endpoint.
Choose PageLens AI when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
whoami, list_domains, list_scans.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M Magicsword MCP | |
|---|---|---|
| Category | Security | Security |
| Quality signal | 53/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | OAuth 2.0 |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | MAGICSWORD_API_KEYMAGICSWORD_BASE_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 21 | 4 |
| Full listing | View Magicsword MCP | View PageLens AI |
Tools & capabilities
Magicsword MCP tools 21
whoamiReturns organization, key id, and scopes. Always call first when troubleshooting.list_endpointsLists endpoints with optional platform / status / hostname-glob filtering.show_endpointFetches one endpoint with OS, policy, compliance, upgrade, heartbeat, and AMSI details.list_agent_releasesLists available agent versions and per-platform latest releases.find_alertsSearches alerts by severity / ack state / since / hostname / MITRE technique.list_eventsLists audit/block telemetry events, including last-day event review workflows.triage_alertFetches one alert directly with triggering events, metadata, and file context; optionally acknowledges or dismisses it.list_policiesLists policies with current version + mode.show_policyShows one policy by id.manage_policy_rulesLists rules or adds explicit / event-derived rules to a policy by id or name. Avoid explicit flat hash rules for Windows WDAC.apply_policy_to_endpointsResolves endpoints and previews a policy assignment; `confirm=true` applies it after approval.flip_to_enforcingTwo-step preview/confirm flip with a server-issued one-time confirm token. Safety-critical.- +9 more on the listing page
PageLens AI tools 4
whoamiConfirm which PageLens account this MCP session is operating on, plus granted OAuth scopes.list_domainsList the domains you've verified ownership of, along with badge tier and the scan currently anchored to the public badge.list_scansList your most recent PageLens scans. Filter by status, domain, or date. Returns a slim summary per scan (id, URL, score, grade, severity counts, and `launchVerdict`). Scans may include `launchContext` with `builderPlatform` and `launchMoment` so agents can frame fixes for the owner's workflow with…get_scanRead the full summary for a single scan: score, grade, owner-first `launchVerdict`, severity counts, launch context, executive summary, top-5 highest-priority findings, and per-persona reviews. For QA Audit scans, `get_scan` also returns a `qaAudit` block containing the product-flow synthesis, jour…
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.
Magicsword MCP
{
"mcpServers": {
"magicsword-mcp": {
"command": "npx",
"args": [
"-y",
"@magicsword-io/magicsword-mcp"
],
"env": {
"MAGICSWORD_API_KEY": "YOUR_MAGICSWORD_API_KEY_HERE",
"MAGICSWORD_BASE_URL": "YOUR_MAGICSWORD_BASE_URL_HERE"
}
}
}
}
PageLens AI
{
"mcpServers": {
"pagelens-ai": {
"url": "https://www.pagelensai.com/api/mcp"
}
}
}
Frequently asked questions
Magicsword MCP is categorized under Security and uses a local stdio subprocess. PageLens AI belongs to Security and uses a remote HTTP/SSE transport. Pick Magicsword MCP for security work and PageLens AI for security.
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.
Magicsword MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. PageLens AI has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 magicsword-mcp and pagelens-ai as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Magicsword MCP has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. PageLens AI has 49/100 (Fair) with 3 views, 0 installs and 1 GitHub stars.