com.pulsemcp/appsignal
appsignal-mcp-server
Is the com.pulsemcp/appsignal MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-01.
MCP server for AppSignal — get alert details, search logs, and retrieve logs within time ranges.
alive probed 2026-11-15 · unchanged since 2026-11-01
- Run it
- npx -y appsignal-mcp-server@0.5.4 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- appsignal-mcp-server 0.5.4
- Capabilities
- resources, tools
- Instructions
- none
- Of a 1M window
- 1.9 % of a 1M context window
- Count
- 19k tokens in Claude, exact, measured 2026-10-25. With the Claude Code prefix mcp__…__ on each tool name: 20k. The o200k_base estimate is 12k. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/pulsemcp/mcp-servers
- Registry
- active, updated 2026-06-17 · registry entry
- Changes
- 2 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.66×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| get_perf_samples | 1 460 | 882 | 8 % |
| get_metrics | 1 409 | 851 | 7 % |
| get_perf_incident_sample_timeline | 1 402 | 847 | 7 % |
| search_logs | 1 344 | 812 | 7 % |
| get_perf_incidents | 1 323 | 799 | 7 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Promptibus MCP com.promptibus/mcp · alive
- ProofTell com.prooftell/mcp · alive
- ProtocolProbe com.protocolprobe/protocolprobe-mcp · alive
- com.pulsemcp.servers/pulse-fetch · needs network
- com.pulsemcp/dynamodb · alive
- com.pulsemcp/fetchpet · alive
- com.pulsemcp/fly-io · needs env
- com.pulsemcp/gcs · needs env
Servers that mention retrieve or details.
- PuroAir ai.agenticshelf/puroair · server error
- LinkedIn MCP Server ai.com.mcp/linkedin · not MCP
- ai.smithery/CollectiveSpend-collectivespend-smithery-mcp · not found
- ai.smithery/DynamicEndpoints-powershell-exec-mcp-server · not found
- ai.smithery/IlyaGusev-academia_mcp · not found
- ai.smithery/JunoJunHyun-festival-finder-mcp · not found
- ai.smithery/aamangeldi-dad-jokes-mcp · not found
- ai.smithery/alex-llm-attack-mcp-server · not found
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-25 06:50 | alive | 353 ms | 20 | 19k | 12k |
| 2026-10-18 06:38 | alive | 555 ms | 20 | 12k |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- This server is in the heaviest 10 % of the registry. Its 5 most expensive tools are 36 % of the cost. Shorter descriptions, fewer optional parameters and fewer tools cut the cost. The command npx mcpcost --url <endpoint> --tools 50 lists every tool with its cost.