A side-by-side look at the PageProofer and Butterbase Oss MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose PageProofer for knowledge & memory work over a hosted endpoint; choose Butterbase Oss for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
P
Choose PageProofer when
You need dedicated capabilities in the Knowledge & Memory domain.
No tool names declared yet. Check the project README from the listing page.
Butterbase Oss 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.
PageProofer is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. Butterbase Oss belongs to Knowledge & Memory and uses a local stdio subprocess. Pick PageProofer for knowledge & memory work and Butterbase Oss for knowledge & memory.
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.
PageProofer has no declared pricing — check the project's own site. Butterbase Oss has no declared pricing — check the project's own site. 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 pageproofer and mcp-285 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, PageProofer has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Butterbase Oss has 51/100 (Good) with 1 views, 0 installs and 3,112 GitHub stars.