VI Update
REMOTE · MCP.VIUPDATE.COM
Search and read VI Update and Good Day (U.S. Virgin Islands news) and The Straight Record.
Available components
Last scanned (15 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category News and Social
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1662 tokens (~207/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
- Server version: 1.2.2 → 1.2.3 functional
- Server version: 1.2.0 → 1.2.2 functional
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “fetch” rewrote its description, which is the text the model reads security
- Server version: 1.1.0 → 1.2.0 functional
- 9 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “about” rewrote its description, which is the text the model reads security
- Tool “fetch” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Schema quality: 175 → 200 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.1.0 functional
- “fetch” reworded the description of “id” cosmetic
- “search” reworded the description of “section” cosmetic
- 8 Nov 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.viupdate.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=viupdate.com | CN=WE1,O=Google Trust Services,C=US | 7 Nov 2026 | 5 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 579ec9336e034df113d10e64dd585b57 |
| SANs: viupdate.com, mcp.viupdate.com, *.mcp.viupdate.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.viupdate.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| viupdate.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.viupdate.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.viupdate.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
about About this server: coverage and counts ~85
What this server holds: how many published items each publication has, the date range each covers, when the VI Update and Good Day data were last refreshed, how each publication is credited, and what is not included; also every published Paper by id, with its date, version, DOI and license. Use for questions about scope, or before reading an empty search as a gap in coverage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
claims_of_the_week Claims of the Week (The Straight Record) ~94
The Claim of the Week fact check from Straight Record Sunday editions, newest first: the claim as quoted, who said it and when, the verdict and the analysis, with the edition date, URL and citeAs line. Use for what The Straight Record has fact-checked. Verdicts are the edition's assessment as of its date.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | How many, 1 to 50. Default 10. |
No output schema declared.
No examples provided.
fetch Read one item in full ~274
The full text of one published item, by the id search or a list returns (such as "viupdate:<slug>", "goodday:036", "straightrecord:042" or "paper:<slug>") or by its public URL. Use for reading an article or edition before quoting or summarizing it. Returns up to 40,000 characters at a time inside a fence labeled as untrusted data; a longer item continues from next_offset. Metadata carries the date, the credit, the citeAs line and, for a VI Update article with a video, the Facebook link. A Paper is also found by its PDF link or its DOI. A Paper with a text edition (Markdown published beside the PDF) comes back as that text, served only when it matches the SHA-256 its listing gives, with the PDF as the version of record. Any other Paper comes back as its listing: the summary, the PDF and DOI links, the data behind it, its license and its citeAs line; this server does not read PDFs.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | An id from search, latest or list_items, or the item's public URL; for a Paper, also its PDF link or DOI. |
| offset | – | – | Character position to start from, for the next window of a long item. Default 0. |
No output schema declared.
No examples provided.
get_good_day_edition Get a Good Day, This Week edition ~130
One Good Day, This Week edition in full and in structure, by its number (such as "036" or "36"), or the newest when no number is given. Use for the week's stories with their sources, the tracked weekly items (WAPA, government, federal, infrastructure), By the Numbers and Also This Week. Good Day is an automated news digest and analysis, operated by Brian Louden, and each edition says so in its byline.
| Name | Type | Req | Description |
|---|---|---|---|
| edition | – | – | Edition number, such as "036" or 36, or the edition URL. Default: the newest edition. |
No output schema declared.
No examples provided.
get_straight_record_edition Get a Straight Record edition ~142
One Straight Record edition in full, by its id (such as "042", "42" or "P001", or the edition URL), or the newest when no id is given. Use for reading every story's The Gap, Left Said, Right Said and The Record (or The Record So Far), with sources, verbatim quotes and their attributions, per-story anchor URLs, Consensus Watch, and on Sundays the Claim of the Week and Democracy Watch. Facts are as of the edition date.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | – | Edition id, such as "042" or "P001", or an edition URL. Default: the newest edition. |
No output schema declared.
No examples provided.
latest Latest from each publication ~148
The newest published items: by default the newest VI Update articles, the newest Good Day, This Week edition and the newest Straight Record edition; or the newest items of one publication. Use for "what is new" or for current coverage. Each item has an id for fetch, its date, headlines or an excerpt, a URL and a citeAs line.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | How many items per publication, 1 to 20. Default 5 for VI Update and 1 for each edition series when all three are asked for; 5 for one publication. |
| section | string | – | One publication: "vi_update", "good_day" or "straight_record". Default: all three. |
No output schema declared.
No examples provided.
list_items List items by date ~201
Published items of one publication, newest first, optionally between two dates, with paging. Use for browsing what a publication ran in a week, month or year. VI Update articles are dated by the date the article shows; Good Day and Straight Record editions by their publication date.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | – | – | Earliest date, inclusive: a year (2026), a month (2026-10) or a day (2026-10-05). |
| date_to | – | – | Latest date, inclusive: a year, a month (its last day) or a day. |
| limit | – | – | How many items, 1 to 50. Default 20. |
| offset | – | – | How many items to skip, for the next page. Default 0. |
| section | string | yes | Which publication: "vi_update" (VI Update articles), "good_day" (Good Day, This Week editions) or "straight_record" (The Straight Record editions). |
No output schema declared.
No examples provided.
search Search VI Update, Good Day and The Straight Record ~278
Keyword search across published VI Update articles, Good Day, This Week editions, The Straight Record editions and VI Update's Papers (long-form reports from the public record), or one of them. Use for finding coverage of a person, place, agency or event. Each result has an id for fetch, a title, a URL with a story anchor where there is one, a snippet, a match tier (exact phrase, all words, some words) with the reason, and its own citeAs line; a Paper also carries its summary, its PDF link and its DOI where it has one. Papers are matched on their title and summary. Results are ranked by tier, then by whether the headline carries the match; across publications they take turns within a tier. Paging uses offset and next_offset. Facts are as of each item's date.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | How many results, 1 to 25. Default 10. |
| offset | – | – | How many ranked results to skip, for the next page. Default 0. |
| query | string | yes | Words or a phrase, such as "WAPA rationing" or "Strait of Hormuz". |
| section | string | – | Limit to one publication: "vi_update", "good_day", "straight_record" or "papers" (VI Update's Papers). Default: all of them. |
No output schema declared.
No examples provided.
How do I install the VI Update MCP server?
VI Update is a hosted endpoint at https://mcp.viupdate.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.viupdate.com
claude mcp add --transport http com-viupdate-news 'https://mcp.viupdate.com/mcp'
What is the VI Update MCP server?
VI Update is an MCP server listed in the public MCP registry as com.viupdate/news. Search and read VI Update and Good Day (U.S. Virgin Islands news) and The Straight Record. This page covers its hosted endpoint (https://mcp.viupdate.com/mcp).
Is the VI Update MCP server safe to use?
VI Update scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the VI Update MCP server expose?
VI Update exposes 8 tools: search, fetch, latest, list_items, get_good_day_edition, and 3 more. Their descriptions and schemas cost roughly 1,352 tokens of context every time the server is loaded.
Does the VI Update MCP server require authentication?
No. We connected to VI Update without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the VI Update MCP server still maintained?
VI Update is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the VI Update MCP server?
VerifyMCP ran 12 checks on VI Update, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about VI Update: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.