Silent tool-failure outcome monitor

com.textforagentsPublished by textforagents.comOfficial publisherv1.0.0Updated Oct 27, 2026

Outcome contracts mined from your clean traces; silent failures checked, with recovery receipts.

The publisher's own server: Agent NOTAMs: hazard bulletins for agents

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Server details

Identifier: com.textforagents/silent-tool-failure-outcome-monitor
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 22, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to textforagents.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.textforagents%2Fsilent-tool-failure-outcome-monitor.svg)](https://sourceweft.com/mcp/com.textforagents%2Fsilent-tool-failure-outcome-monitor?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Remote MCP endpoint that checks agent tool calls against outcome contracts mined from clean traces and reports silent failures with recovery receipts.

What you can do: The manifest lists no individual tools, so capabilities come from the short description only.
It mines outcome contracts from the user's clean traces.
It checks for silent tool failures against those contracts.
It returns recovery receipts for the failures it finds.
When to use it: Worth considering when an assistant or agent pipeline runs tools whose failures are not reported as errors, and you want an automated check that outcomes actually matched expectations, with a record of what was recovered.
Requirements: A remote streamable HTTP endpoint at the provider's site; no local package or runtime is needed. OAuth authentication is required. No environment variables or headers are declared.

Before you install

The service works from your traces, so tool-call data is sent to a third party; review what those traces contain before connecting. OAuth grants the server access under your account. No tool list is published, so the exact read and write behavior cannot be verified in advance.

Installation

In SourceWeft

Open Silent tool-failure outcome monitor in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.textforagents%2Fsilent-tool-failure-outcome-monitor/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "silent-tool-failure-outcome-monitor": {
      "type": "http",
      "url": "https://textforagents.com/products/silent-tool-failure-outcome-monitor/mcp"
    }
  }
}

Tools

This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

v1.0.0LatestOct 22, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.