VISEON Ask
REMOTE · VISEON.IO · SCANNED SEP 29
VISEON's Schema.org knowledge graph: products, services, people, FAQs and terms, from viseon.io
Available components
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 5 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 Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 329 tokens (~65/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the VISEON Ask MCP server?
VISEON Ask 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'
{
"mcpServers": {
"io-viseon-semantic-intelligence": {
"url": "https://viseon.io/mcp"
}
}
} {
"servers": {
"io-viseon-semantic-intelligence": {
"type": "http",
"url": "https://viseon.io/mcp"
}
}
} [mcp_servers.io-viseon-semantic-intelligence] url = "https://viseon.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-viseon-semantic-intelligence": {
"type": "remote",
"url": "https://viseon.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-viseon-semantic-intelligence --url 'https://viseon.io/mcp' --transport streamable-http
mcp_servers:
io-viseon-semantic-intelligence:
url: "https://viseon.io/mcp" {
"McpServers": {
"io-viseon-semantic-intelligence": {
"Transport": "http",
"Url": "https://viseon.io/mcp"
}
}
} assistant mcp add io-viseon-semantic-intelligence -t streamable-http -u 'https://viseon.io/mcp'
{
"mcpServers": {
"io-viseon-semantic-intelligence": {
"type": "http",
"url": "https://viseon.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 29 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 6.0.14 → 6.0.16 functional
- 28 Sept 26 65
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 29 Sept 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 | 3 Aug 2026 | 1 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 390ade7d5246252e13ced55193c56ce4 |
| SANs: 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. | present | 57355 | 8 | Verified |
| viseon.io. | absent | 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 |
| x-content-type-options | nosniff |
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 ~26
Find all entities of a specific schema.org type
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| items | array | yes | – |
No examples provided.
fuzzy_find_and_traverse ~121
Find and rank schema.org entities from natural language. Returns bounded entity context with relationship IDs; use get_entity for full detail.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Optional: maximum ranked entities to return (default 5, maximum 10) |
| query | string | yes | Search terms (e.g., "AI optimisation services", "schema markup articles") |
| type | string | – | Optional: filter by entity type (Organization, Service, Article, Person, WebPage, Question) |
| weights | object | – | Optional: Custom weight multipliers for ranking |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| items | array | yes | – |
No examples provided.
get_entity ~29
Get complete schema.org entity data by URL
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL of the entity |
Structured output declared, but exposes no named fields.
No examples provided.
query_relationships ~30
Find entities connected to a subject
| Name | Type | Req | Description |
|---|---|---|---|
| predicate | string | – | – |
| subject | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| items | array | yes | – |
No examples provided.
search_content ~21
Full-text search across graph
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| items | array | yes | – |
No examples provided.
What is the VISEON Ask MCP server?
VISEON Ask 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 Ask MCP server safe to use?
VISEON Ask scores 65 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 Ask MCP server expose?
VISEON Ask exposes 5 tools: get_entity, query_relationships, find_by_type, search_content, fuzzy_find_and_traverse. Their descriptions and schemas cost roughly 227 tokens of context every time the server is loaded.
Does the VISEON Ask MCP server require authentication?
No. We connected to VISEON Ask without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the VISEON Ask MCP server still maintained?
VISEON Ask is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.