Koskamo

VISEON MCP

An official MCP server operated by VISEON that provides a Schema.org knowledge graph for enterprise AI agents. It enables deterministic discovery, discussion, and transaction capabilities by serving governed, canonical facts about an organization's entities, products, and services directly from the vendor's domain.

Visit VISEON

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

VISEON MCP logo, by VISEONVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by VISEON
MCP endpoint (Streamable HTTP)
https://viseon.io/mcp
Vendor documentation

What its tools do

7 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (7)

7 of 7 have a description · 0 of 7 declare behavior hints · 0 of 7 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to viseon.io ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Perform exact entity lookups and relationship queries via the knowledge graph
  • Enable AI agents to discover and understand organizational brands and products
  • Support deterministic AI answers with traceable source evidence
  • Facilitate agentic workflows for internal and external AI systems

Source and maintenance

Vendor evidenceRegistry 6.0.15
mcp-registry: io.viseon/semantic-intelligence@6.0.15Source repositoryProject website
Maintenance checked

Protocol and capabilities

Server
VISEON for Web 4.0.0-dev
MCP protocol negotiated in check
2025-11-25
Tools
7 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Use this KG as the sole source for KG-grounded answers. Do not embellish with external facts, images or media. Preserve canonical entity IDs. Before selecting media, call get_entity for the resolved entity and use only its explicitly linked assets. If evidence is absent, ambiguous or inaccessible, say so; do not substitute a namesake. If MCP is unavailable, report that limitation; do not switch to web search without explicit user authorisation. Queries the VISEON schema.org knowledge graph, served from the edge. Prefer fuzzy_find_and_traverse for natural-language discovery: it returns a bounded ranked set of entities with relationship IDs, and tolerates typos and alternative names. Use get_entity when full detail is required. The optional "type" argument (Question, Person, Service, Article, Organization, Product, SoftwareApplication, DefinedTerm, Event) constrains results; "limit" accepts 1..10 (default 5). Use traverse_path for a known chain of relationships in one call (for example worksFor, then founder and foundingDate); prefix a predicate with ^ to follow it backwards. The other tools are exact lookups by URL, type or predicate, and a substring search. Results are in structuredContent. For a client on protocol 2026-07-28 or later the text block of a fuzzy_find_and_traverse result is only a short table (id, name, type) and the hits are summaries: call get_entity for one entity in full. To quote what an article says, word for word and with a link to the passage, use get_citable_passages (the entity tools give an article's description, author, date and topics, not its text).

Tools

7 advertised

get_entity
Advertised by the server during the last successful anonymous check.

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.

get_entity input schema
{
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string"
    }
  }
}
get_entity output schema
{
  "type": "object",
  "additionalProperties": true
}
query_relationships
Advertised by the server during the last successful anonymous check.

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.

query_relationships input schema
{
  "type": "object",
  "required": [
    "subject"
  ],
  "properties": {
    "subject": {
      "type": "string"
    },
    "predicate": {
      "type": "string"
    }
  }
}
query_relationships output schema
{
  "type": "object",
  "required": [
    "items",
    "count"
  ],
  "properties": {
    "count": {
      "type": "integer"
    },
    "items": {
      "type": "array",
      "items": {
        "type": "object"
      }
    }
  }
}
find_by_type
Advertised by the server during the last successful anonymous check.

Find all entities of a specific schema.org type (exact type name, for example Service, Person, DefinedTerm).

find_by_type input schema
{
  "type": "object",
  "required": [
    "type"
  ],
  "properties": {
    "type": {
      "type": "string"
    }
  }
}
find_by_type output schema
{
  "type": "object",
  "required": [
    "items",
    "count"
  ],
  "properties": {
    "count": {
      "type": "integer"
    },
    "items": {
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  }
}
search_content
Advertised by the server during the last successful anonymous check.

Substring search across the text of every entity; returns up to 20 entity URLs.

search_content input schema
{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string"
    }
  }
}
search_content output schema
{
  "type": "object",
  "required": [
    "items",
    "count"
  ],
  "properties": {
    "count": {
      "type": "integer"
    },
    "items": {
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  }
}
fuzzy_find_and_traverse
Advertised by the server during the last successful anonymous check.

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.

fuzzy_find_and_traverse input schema
{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "type": {
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "default": 5,
      "maximum": 10,
      "minimum": 1
    },
    "query": {
      "type": "string"
    },
    "detail": {
      "enum": [
        "summary",
        "full"
      ],
      "type": "string"
    },
    "weights": {
      "type": "object",
      "properties": {
        "predicates": {
          "type": "object"
        },
        "entityTypes": {
          "type": "object"
        }
      }
    }
  }
}
fuzzy_find_and_traverse output schema
{
  "type": "object",
  "required": [
    "items",
    "count"
  ],
  "properties": {
    "count": {
      "type": "integer"
    },
    "items": {
      "type": "array",
      "items": {
        "type": "object"
      }
    }
  }
}
traverse_path
Advertised by the server during the last successful anonymous check.

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).

traverse_path input schema
{
  "type": "object",
  "required": [
    "start"
  ],
  "properties": {
    "path": {
      "type": "array",
      "items": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          }
        ]
      },
      "maxItems": 3
    },
    "start": {
      "type": "string"
    },
    "maxHops": {
      "type": "integer",
      "default": 2,
      "maximum": 3,
      "minimum": 1
    }
  }
}
traverse_path output schema
{
  "type": "object",
  "required": [
    "start",
    "edges",
    "values"
  ],
  "properties": {
    "hops": {
      "type": "integer"
    },
    "edges": {
      "type": "array",
      "items": {
        "type": "object"
      }
    },
    "start": {
      "type": "object"
    },
    "values": {
      "type": "array",
      "items": {
        "type": "object"
      }
    },
    "truncated": {
      "type": "boolean"
    },
    "truncated_hops": {
      "type": "array",
      "items": {
        "type": "integer"
      }
    }
  }
}
get_citable_passages
Advertised by the server during the last successful anonymous check.

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.

get_citable_passages input schema
{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 3,
      "maximum": 5,
      "minimum": 1
    },
    "query": {
      "type": "string"
    },
    "article": {
      "type": "string"
    }
  }
}
get_citable_passages output schema
{
  "type": "object",
  "required": [
    "items",
    "count"
  ],
  "properties": {
    "note": {
      "type": "string"
    },
    "count": {
      "type": "integer"
    },
    "items": {
      "type": "array",
      "items": {
        "type": "object"
      }
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1105 ms
95th percentile latency
1105 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1105 ms · metadata changed · 7 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http viseon-mcp https://viseon.io/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add viseon-mcp --url https://viseon.io/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable viseon-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "viseon-mcp": {
      "url": "https://viseon.io/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "viseon-mcp": {
      "type": "streamableHttp",
      "url": "https://viseon.io/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start viseon-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "viseon-mcp": {
      "type": "http",
      "url": "https://viseon.io/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http viseon-mcp https://viseon.io/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://viseon.io/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "viseon-mcp": {
      "serverUrl": "https://viseon.io/mcp"
    }
  }
}

Let your agent find its tools

Find servers like VISEON MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 5,159

Do you run VISEON MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing