update_signal

shallow

io.github.valuein/mcp-sec-edgar · Verify this server

Edit an existing signal IN PLACE — rename it, change what it watches, or change where it delivers — keeping its id, its fire history (`trigger_count`, `last_triggered_at`) and every inbox item and delivery already tied to it. Pass only the fields to change; omitted fields keep their stored value. `channels` REPLACES the whole delivery list (1–4, distinct type+target); a webhook entry that keeps its URL and omits `hmac_secret` keeps the stored secret. A soft-deleted signal is refused — `restore_deleted` first. Same tier rules as `create_signal`: `price_move` / `fundamental_change` / `watchlist_restatement` conditions need Pro+. Cap-neutral: an edit never takes a signal slot.

100.0/100

1 trials · measured 27 days ago

update_signal scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against io.github.valuein/mcp-sec-edgar, measured 23 Sept 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
self-provisionable
Category
Finance & compliance
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-09-23100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: update_signal
[![Vouch score](https://vouch.tools/api/tools/2c74c9bd-9ca5-4fcd-9299-2d6f2aa19955/badge.svg)](https://vouch.tools/tools/2c74c9bd-9ca5-4fcd-9299-2d6f2aa19955)
update_signal — Vouch