AgentSignal

net.agentsignalPublished by agentsignal.netv0.2.74Updated Nov 19, 2026

One call reaches an agent inbox, a signed webhook, or a person's iPhone, iPad and Mac.

The publisher's own server: Signal Scout

Overview

AI-generated overview

AgentSignal lets an assistant send push notifications to a specific person's devices, check delivery credit and recipients, and register itself as an…

What you can do
  • Get and check notification credit, including a free trial block that needs no account or wallet
  • Check what notifying a given recipient would cost and whether they accept free sends
  • Send a push notification to one recipient key using credit instead of an API key
  • Open an account and mint an API key without a human, dashboard or card
  • Join a channel with a join code to become addressable in the current session
When to use it
Use it when an agent or script needs to reach a specific human right now — a finished deploy, a cron result, an alert — or when an agent should become reachable by others through a join code. It is also useful for testing notification flows with a sandbox key before paging real people.
Requirements
Runs locally over stdio via npx from the npm package @agentsignalnet/mcp, so Node.js is needed. Optional credentials: AGENTSIGNAL_API_KEY (account or sandbox key) and AGENTSIGNAL_JOIN_TOKEN; with neither set, only the no-account credit tools are registered. AGENTSIGNAL_BASE_URL overrides the API endpoint. Network access to the hosted service is required.
Before you install
Sending notifications reaches real people and consumes paid deliveries; sandbox deliveries still count against the same monthly ceiling. open_account writes a new API key to the machine, and open_credit obtains a trial block without any human approval. Keep AGENTSIGNAL_API_KEY and AGENTSIGNAL_JOIN_TOKEN private and out of transcripts. Unless AGENTSIGNAL_BASE_URL is set, the server talks to production.

Installation

In SourceWeft

  1. Open AgentSignal in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Public client mirror. This repository holds the AgentSignal client packages (@agentsignalnet/core, sdk, cli, mcp), examples and integration docs. The hosted service — API, dashboard, dispatch, billing — runs at agentsignal.net and is not part of this mirror. Issues and PRs welcome here.

[Image]

AgentSignal

Push notifications for agents. Deliver a short, high-signal message to a specific human's devices, right now — from a script, a cron job, or an autonomous agent.

bash
curl --request POST \  --url https://api.agentsignal.net/v1/messages \  --header 'Authorization: Bearer <api key>' \  --header 'Content-Type: application/json' \  --data '{    "to":"<recipient key>",    "title":"Deploy finished",    "body":"prod is green",    "priority":1}'

Why

Pushover solved this for humans in 2011 and has barely moved since. AgentSignal targets the same job for a world where the sender is usually a machine:

  • Agent-native — REST that's one curl away, plus an MCP server, TypeScript SDK, and CLI. Idempotency keys mean a retrying agent can't double-notify.
  • No seat restrictions — pricing is notification volume only. Invite the whole team, register as many devices as you want.
  • Sandboxes — throwaway projects that are auto-purged, so an agent can be exercised and the whole thing deleted with nothing retained. Deliveries count against quota.
  • Easy setup and takedown — create a channel, a person, and a device enrollment in one call. Delete all of it in one call, with no retention.
  • White-labeling — per-channel name, icon, accent color, and sound on the notification itself.
  • Scheduling — one-off and recurring sends, described in plain language ("every weekday at 09:00") with an explicit timezone, or as cron if you'd rather. Preview the next runs before you commit to them.
  • x402 — an agent with a wallet and no account can pay per notification over HTTP 402.

Pricing

PlanDeliveries / monthPrice
Free1,000$0
Starter10,000$5/mo
Growth100,000$10/mo
Max1,000,000$50/mo
Pay as you goPer delivery, USDC on Basex402

A delivery is one message reaching one device.

Architecture

Supabase is the database. Cloudflare Workers is everything else.

apps/apiCloudflare Worker (Hono). The API: ingest, dispatch, rate limiting, x402.
apps/webNext.js on Workers via OpenNext. Marketing, docs, dashboard.
apps/appleSwiftUI multiplatform client for iOS and macOS.
packages/coreShared types and Zod schemas.
packages/sdk@agentsignalnet/sdk — typed client whose retries can't double-notify.
packages/cliagentsignal — send from a terminal or a shell script.
packages/mcp@agentsignalnet/mcp — notify a human, or ask one and block until they answer.
services/pushThe doorbell. Holds an SSE socket per agent so a message arrives without being asked for. Carries no message — only "look again".
services/pilot-bridgeA box with a UDP socket, because a Worker has none. Puts us on the Pilot overlay. Deployed at pilot.agentsignal.net.
supabase/Schema, RLS policies, and the SQL that carries the ingest hot path.

Delivery is inline at ingest — APNs is called during the request, so the normal path is sub-second. Cloudflare Queues handle retries, and a Durable Object alarm drives emergency-priority re-alerts until a human acknowledges.

An agent receives in one of three ways, and the default is the humblest one. It polls /v1/devices/me/messages, which needs no inbound address and works from behind anything. A doorbell makes that prompt rather than periodic: the agent holds an outbound SSE connection and is told to look, which is why the poll underneath it is a slow safety net rather than the mechanism. Or, if the agent is already a service with a hostname of its own, it registers an endpoint and is POSTed at directly — see hosting an endpoint, which is also where the signature you must verify is specified.

None of the three replaces the delivery row. The message is written to Postgres first either way; the transport only decides how long it sits there unseen.

Platform support ships Apple first (iPhone, iPad, Mac), then Android, then Linux and Windows.

Agent orchestration onboarding

Set up human and company orchestration agents with direct recipient-key communication in one pass with:

Development

Requires Node 22+, pnpm, the Supabase CLI, and Xcode 26 for the Apple client.

bash
pnpm installsupabase start          # local Postgres, Auth, and Realtimesupabase db reset       # apply migrations and seedpnpm dev:api            # wrangler dev on :8787pnpm dev:web            # next dev on :3000

Copy apps/api/.dev.vars.example to apps/api/.dev.vars and apps/web/.env.example to apps/web/.env.local, then fill them in.

Using the MCP server

json
{  "mcpServers": {    "agentsignal": {      "command": "npx",      "args": ["-y", "@agentsignalnet/mcp"],      "env": { "AGENTSIGNAL_API_KEY": "as_test_…" }    }  }}

Paste that into .mcp.json, ~/.claude.json, or claude_desktop_config.json. A sandbox key (as_test_…) is the one to develop against: its history is disposable and swept on a TTL. It is not a second budget — sandbox deliveries count against the same monthly ceiling as live ones, and overage never applies to them, so a sandbox is a hard stop rather than a cheaper way to send. For Claude Code there is a plugin in plugins/agentsignal that asks for the credentials rather than having them sit in a config file.

Which tools appear depends on what is in that env block: the server registers only the ones the credentials can actually use, so an API key, a join token, and neither are three different toolsets.

Against local changes

npx fetches the published server. To run the one in this checkout instead:

bash
pnpm run mcp:local

That builds the packages and prints the same mcpServers block, with an absolute path to the build in place of the npx invocation, ready to paste into any of the same files. AGENTSIGNAL_API_KEY from your shell is used if it is set; otherwise the placeholder is a sandbox key.

Two things worth knowing. It points at the build, not the source, so rerun it after changing anything under packages/ — nothing is watching. And it talks to production unless told otherwise: put AGENTSIGNAL_BASE_URL in that env block, http://localhost:8787 while pnpm dev:api is running, or the first thing an agent under development does is page somebody real.

The CLI is npx -y @agentsignalnet/cli, or from the checkout without being installed:

bash
node packages/cli/dist/index.js send --to u_8fk2… "prod is green"

License

Proprietary. © Data Group AI.

Source: README.md at commit b3137f6

Tools

6

open_credit

Get free credit to start sending

Get a credit token with a small block of free deliveries on it. No account, no signup, no wallet, no payment, no human involved. Call this once if you have no AgentSignal API key and want to notify someone. The free block is a TRIAL of reaching a PERSON — it is spent only on deliveries to people, and messages to other agents are paid from the first one, so do not open a token expecting free agent-to-agent traffic. The token it returns is shown once and cannot be recovered — save it somewhere durable and set it as AGENTSIGNAL_CREDIT so a restart does not lose the balance. If you already have a token, do not call this again; use check_credit instead.

Takes no parameters.

check_credit

How many deliveries are left

Report the deliveries left on your credit token, free and bought separately. Free is always spent first. Call this to decide whether you can afford to notify someone, rather than finding out by trying.

Takes no parameters.

check_recipient

What a send would cost, before sending it

Ask what notifying someone would cost in deliveries, and whether they accept free sends at all. Needs no credit token. Worth calling before notify_paid when the balance is tight: the answer distinguishes "this recipient is out of free traffic this month" from "you are out of credit", which need different responses from you.

Parametersrecipient_keyrequired

notify_paid

Notify someone using credit rather than an account

Send a push notification drawing on your credit token instead of an API key. Use this when you have no AgentSignal account. Addresses exactly one recipient key — groups and broadcasts cannot be paid for, so being given one key never lets you reach a whole organisation. Call open_credit first if you have no token.

Parameterstorequiredurlbodyrequiredtitlepriority

join_channel

Become an addressable agent

Become addressable using a join code. Pass the code as `token` if somebody just gave you one — that is all it takes, with no config file to edit and no restart; the tools it unlocks arrive in this same session. If this server was started with AGENTSIGNAL_JOIN_TOKEN already set, you can omit it. No API key and no account needed: a join code can create an agent and nothing else, which is why it is safe to paste into a chat. Pick a stable handle and reuse it on every start — the same handle is the same agent, so restarting rejoins rather than creating a second copy of you. The credential is remembered afterwards, so call this once and not again unless you are changing handle.

Parameterstokenhandlerequiredendpointdescriptioncapabilities

open_account

Open an AgentSignal account

Open your own account with no human, no dashboard and no card. Use this when you have no API key and want one. The key it mints is written to this machine and used immediately -- it is never shown, and there is nothing for you to copy or set, because a key in a response is a key in the transcript. It is read back on the next start. The account can pay from the moment it exists: a small number of deliveries to a PERSON are free for its lifetime, and messages to other agents are paid from the first one via open_credit.

Parametersnamerequired

Version history

1
  1. v0.2.74LatestNov 17, 2026

Score

80% 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 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Signal integrations