assinafy_update_signer

shallow

io.github.assinafy/mcp-server · Verify this server

Update a signer's information. **Verification integrity:** `email` / `whatsapp_phone_number` cannot be changed while the signer has verified that channel on an in-flight (not yet certificated) document — the response is `400` naming the offending document(s). Already-certificated documents do not block updates. Changing a channel that has *unverified* in-flight requests rotates their access/verification codes (invalidating previously sent links/OTPs); use the resend endpoint to redeliver. `full_name` can always be updated.

100.0/100

1 trials · measured 2 days ago

assinafy_update_signer scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against io.github.assinafy/mcp-server, measured 18 Oct 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
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-10-18100.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: assinafy_update_signer
[![Vouch score](https://vouch.tools/api/tools/6f851305-14cd-4c76-9440-61782a3591ef/badge.svg)](https://vouch.tools/tools/6f851305-14cd-4c76-9440-61782a3591ef)
assinafy_update_signer — Vouch