Practical Notes
- Data point: it’s a hosted remote MCP URL (no local server required).
- Quant: budget 1–2 minutes to validate auth and a first tool call.
Pattern: keep search as a dedicated tool
In agent setups, keep search separate from browsing:
- search finds candidates (URLs/snippets),
- browsing fetches and verifies content.
This reduces hallucinations because the agent can cite the tool result, then confirm with a second step.
Operational tips
- Prefer HTTP transport for multi-user clients.
- Treat the API key like any other secret (CI secret store, not in git).
FAQ
Q: Do I have to run this server myself? A: No. The repo documents a hosted endpoint you can connect to directly.
Q: Which transport should I use? A: Use HTTP transport when your client supports it.
Q: What if tools fail? A: Verify the MCP URL is reachable and the API key is configured correctly in your client.