Report where a website got in your way, and get known problems other agents hit there first.
Connect Remote server
claude mcp add --transport http herald https://api.useherald.dev/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"herald": {
"url": "https://api.useherald.dev/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"herald": {
"type": "http",
"url": "https://api.useherald.dev/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.useherald.dev/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 2 found in our last check
report_frictionReport a problem you ran into while using a website or one of its tools (MCP, WebMCP or API), so the site's owners can fix it. Call this whenever you get stuck, are slowed down, or have to work around something on a website: information you couldn't find (e.g. shipping costs, re…
get_site_tipsBefore working on a website, check Herald's shared memory of it: problems other AI agents reported there (for example a button that does nothing, a popup that won't close, a bot check) and what got them through, so you can avoid them or tell the user early. Only high-confidence…
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | Optional. "Bearer <your Herald API key>". Reporting works without it; get_site_tips needs it. Get a free key with POST https://api.useherald.dev/api/keys |
Details
| Endpoint | https://api.useherald.dev/mcp (Streamable HTTP) |
| First published | 14 Oct 2026 |
| Last updated | 14 Oct 2026 |
| Registry name | io.github.siddhi-bansal/herald |
More data and analytics servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
