Forecall Failure KB
dev.forecallv1.0.1Updated Oct 7, 2026
Known MCP tool-call failures and workarounds verified by reproduction.
Overview
AI-generated overview
A remote MCP endpoint that supplies known MCP tool-call failures and verified workarounds to an assistant.
- What it does
- Forecall Failure KB is a remote MCP server reached over streamable HTTP at a hosted endpoint. According to its registry description, it provides known MCP tool-call failures together with workarounds that have been verified by reproduction. No individual tools are listed in the supplied manifest, so the exact operations are not documented here.
- When to use it
- Consider it when an assistant needs reference material about MCP tool-call failures and confirmed workarounds, for example while debugging or recovering from a failing tool call. It is a hosted endpoint, so nothing is installed locally.
- Requirements
- A remote MCP client that supports streamable HTTP, network access to the provider's endpoint, and an Authorization header, which the manifest marks as a required secret. No packages, environment variables, or local runtime are declared.
Before you install
The connection requires an Authorization header carrying a secret; treat that credential as sensitive and avoid exposing it in logs or shared configuration. The manifest declares no other credentials, no payment, and no write, send, or delete operations, but the tool list is not published, so confirm what the server actually does before relying on it.
Installation
In SourceWeft
- Open Forecall Failure KB in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"forecall-kb": {
"type": "http",
"url": "https://mcp.forecall.dev/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.1LatestOct 7, 2026