Agent NOTAMs: hazard bulletins for agents

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

Signed, auto-expiring hazard bulletins for tools and APIs, with pre-flight checks for agents.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint that gives agents signed, auto-expiring hazard bulletins for tools and APIs, plus pre-flight checks.

What you can do
  • The manifest lists no individual tools, so capabilities come from the registry description only.
  • It supplies signed hazard bulletins about tools and APIs, which expire automatically.
  • It offers pre-flight checks an agent can run before using a tool or API.
  • Access is through a remote streamable HTTP endpoint with OAuth sign-in.
When to use it
Consider it when an agent calls third-party tools or APIs and you want a warning layer that flags known hazards and lets the agent check before acting. It is not for general search, data retrieval or content generation.
Requirements
A remote MCP client that supports streamable HTTP, pointed at the provider's hosted endpoint. OAuth authentication is required; no environment variables or headers are declared. Network access to the provider is needed.
Before you install
OAuth grants the server access tied to your account, so review the scopes requested at sign-in. The bulletins are third-party content and may be incomplete or stale, so treat them as advisory rather than authoritative. No tool list is published, so confirm what the server can do before relying on it.

Installation

In SourceWeft

  1. Open Agent NOTAMs: hazard bulletins for agents in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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%2Fagent-notams-hazard-bulletins/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": {
    "agent-notams-hazard-bulletins-for-agents": {
      "type": "http",
      "url": "https://textforagents.com/products/agent-notams-hazard-bulletins/mcp"
    }
  }
}

Tools

0
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

1
  1. v1.0.0LatestOct 19, 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.

Other Textforagents integrations