VISEON for Web
REMOTE · VISEON.IO
VISEON's Schema.org knowledge graph: products, services, people, FAQs and terms, from viseon.io
Available components
Last scanned (21 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
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
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1186 tokens (~169/item across 7 items; 7 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
- HTTPS
- 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.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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.
- 16 Nov 26 0
- Server version: 6.0.16 → 6.1.0 functional
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 7 Nov 26 0
- Server version: 4.0.0-dev → 6.0.16 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_entity” rewrote its description, which is the text the model reads security
- Schema quality: 147 → 169 ▼ functional
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://viseon.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=viseon.io | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 940c43795a5bfce113fbe2423d3a8f39 |
| SANs: viseon.io, chat.viseon.io, *.chat.viseon.io | ||||||
| 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 viseon.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| viseon.io. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self' https:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://s.w.org https://www.google-analytics.com https://cdn.jsdelivr.net https://code.jquery.com https://www.google.com https://www.gstatic.com https://www.googletagmanager.com https://static.cloudflareinsights.com https://challenges.cloudflare.com https://challenges.cloudflare.com/cdn-cgi/ https://www.youtube.com https://cdnjs.cloudflare.com; style-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net https://cdnjs.cloudflare.com https://fonts.googleapis.com; img-src 'self' data: https:; font-src 'self' data: https://cdnjs.cloudflare.com https://fonts.gstatic.com https://fonts.googleapis.com; connect-src 'self' https: https://challenges.cloudflare.com/cdn-cgi/; child-src https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com https://www.google.com https://www.youtube-nocookie.com data: blob:; worker-src 'self' blob:; frame-ancestors 'self'; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), fullscreen=(self "https://challenges.cloudflare.com" "https://www.youtube.com" "https://www.youtube-nocookie.com" "https://player.vimeo.com"), payment=(), sync-xhr=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://viseon.io/mcp | Verified | 200 | |
| http (plaintext) | http://viseon.io/mcp | HTTPS enforced | 301 | https://viseon.io/mcp |
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 →
find_by_type ~39
Find all entities of a specific schema.org type (exact type name, for example Service, Person, DefinedTerm).
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| items | array | yes | – |
No examples provided.
fuzzy_find_and_traverse ~148
Find and rank schema.org entities from natural language, tolerating typos and alternative names. Returns bounded entity context with relationship IDs; use get_entity for full detail. The optional detail argument is summary (for each hit: id, type, name, url, the start of the description and the match score) or full (every property and relationship). A client on protocol 2026-07-28 or later gets summary unless it asks for full; an older client gets full unless it asks for summary.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| type | string | – | – |
| weights | object | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| items | array | yes | – |
No examples provided.
get_citable_passages ~197
Return passages of the VISEON articles word for word, each with a link to the passage itself, the article it is part of and how much of the query it holds, so an answer can quote and cite them. query: the distinctive words asked about (a name, a term, a phrase the article uses). article: optional, an article's @id, page url or title, to look inside that article only. limit: 1 to 5 passages, default 3. The text is verbatim and unaltered: no model has read or paraphrased it. It matches the article's own words, so ask in the words the article would use; for what the graph says about an article (description, author, date, topics) use fuzzy_find_and_traverse and get_entity.
| Name | Type | Req | Description |
|---|---|---|---|
| article | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| items | array | yes | – |
| note | string | – | – |
No examples provided.
get_entity ~102
Get complete schema.org entity data by URL (its @id), including relationships the graph holds in either direction. Use this before selecting an entity's image or other media: retain the canonical subject ID and use only assets explicitly linked by the retrieved record. A matching name, caption or filename alone does not establish identity. If no supported asset is available, state the limitation; do not add externally searched media to a KG-grounded answer.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
query_relationships ~60
Find entities connected to a subject: one row per property value, with object_type 'uri' for links to other entities and 'literal' for values. Optionally filter by predicate.
| Name | Type | Req | Description |
|---|---|---|---|
| predicate | string | – | – |
| subject | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| items | array | yes | – |
No examples provided.
search_content ~33
Substring search across the text of every entity; returns up to 20 entity URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| items | array | yes | – |
No examples provided.
traverse_path ~260
Walk the knowledge graph from one entity in a single call. start: an entity @id or a name (resolved like fuzzy_find_and_traverse). path: one entry per hop, each a predicate or a list of predicates; prefix a predicate with ^ to follow it backwards (e.g. ^worksFor finds who works for an organisation). Literal values (dates, names, emails) named in a hop are returned in values. Example, who founded the company Hamza works for and when: start "Hamza Ashraf", path [["worksFor"], ["founder", "foundingDate"]]. Without path, follows every link for maxHops (1-3, default 2) and returns links only, with a budget of 100 rows shared between hops, so hubs are cut short rather than hiding later hops (use a path to go deeper: a path call may return up to 400 rows). Returns edges [{hop, from, predicate, to, to_name, to_types}], values [{hop, subject, subject_name, predicate, value}], truncated and truncated_hops (the hops that hit a limit).
| Name | Type | Req | Description |
|---|---|---|---|
| maxHops | integer | – | – |
| path | array | – | – |
| start | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| edges | array | yes | – |
| hops | integer | – | – |
| start | object | yes | – |
| truncated | boolean | – | – |
| truncated_hops | array | – | – |
| values | array | yes | – |
No examples provided.
How do I install the VISEON for Web MCP server?
VISEON for Web is a hosted endpoint at https://viseon.io/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 · viseon.io
claude mcp add --transport http io-viseon-semantic-intelligence 'https://viseon.io/mcp'
What is the VISEON for Web MCP server?
VISEON for Web is an MCP server listed in the public MCP registry as io.viseon/semantic-intelligence. VISEON's Schema.org knowledge graph: products, services, people, FAQs and terms, from viseon.io. This page covers its hosted endpoint (https://viseon.io/mcp).
Is the VISEON for Web MCP server safe to use?
VISEON for Web scores 76 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 VISEON for Web MCP server expose?
VISEON for Web exposes 7 tools: get_entity, query_relationships, find_by_type, search_content, fuzzy_find_and_traverse, and 2 more. Their descriptions and schemas cost roughly 839 tokens of context every time the server is loaded.
Does the VISEON for Web MCP server require authentication?
No. We connected to VISEON for Web without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the VISEON for Web MCP server still maintained?
VISEON for Web 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 VISEON for Web MCP server?
VerifyMCP ran 12 checks on VISEON for Web, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about VISEON for Web: Authorization. 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.