NestDaddy

Forecall Failure KB

dev.forecall/forecall-kb · v1.2.0

Known MCP tool-call failures and workarounds verified by reproduction.

Connect Remote server

Terminal
claude mcp add --transport http forecall-kb https://mcp.forecall.dev/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
~/.cursor/mcp.json
{
  "mcpServers": {
    "forecall-kb": {
      "url": "https://mcp.forecall.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "forecall-kb": {
      "type": "http",
      "url": "https://mcp.forecall.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://mcp.forecall.dev/mcp

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools

This server asks for a key before it lists its tools. Connect it with your own key to see them.

Headers

NameDescription
Authorization
Required, secret

Details

Endpointhttps://mcp.forecall.dev/mcp (Streamable HTTP)
First published15 Oct 2026
Last updated15 Oct 2026
Registry namedev.forecall/forecall-kb

More other servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.