Web3alert for agents

io.web3alertPublished by web3alert.ioOfficial publisherv0.1.0Updated Nov 21, 2026

Decoded on-chain events for AI agents: find triggers, subscribe a webhook, read delivery logs.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Remote Web3alert MCP server that lets an assistant work with decoded on-chain event triggers, webhook subscriptions and delivery logs.

What you can do
  • Find decoded on-chain event triggers available for alerting
  • Subscribe a webhook to a chosen trigger
  • Read delivery logs for subscribed alerts
When to use it
Useful when an assistant should set up or inspect blockchain event alerts, such as subscribing a webhook to an on-chain trigger or checking whether past alert deliveries succeeded.
Requirements
Remote streamable HTTP endpoint at web3alert.io; no local package. Requires a bearer personal access token from the Web3alert Account page, sent in the Authorization header.
Before you install
The server needs a personal access token in the Authorization header, so treat it as a secret. Subscribing a webhook changes alerting configuration and sends event data to the webhook target you choose.

Installation

In SourceWeft

  1. Open Web3alert for agents in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/io.web3alert%2Fagent/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.

{
  "mcpServers": {
    "web3alert-for-agents": {
      "type": "http",
      "url": "https://web3alert.io/mcp/agent",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

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. v0.1.0LatestNov 21, 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.