VISEON for Web

endpoint

https://viseon.io/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is VISEON for Web live?

Yes — it answered the hub's last check (checked 5h ago). It answered 98% of checks over the last 30 days.

Is VISEON for Web free to use?

Yes — the hub reached it with no key and no payment.

What tools does VISEON for Web have?

7 tools: search_content, query_relationships, fuzzy_find_and_traverse, traverse_path, get_citable_passages, find_by_type, get_entity.

Is VISEON for Web safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• search_content reads unknown 5h ago

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

  mcp-tool

  1234567891011

  {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "query": {
        "type": "string"
      }
    }
  }

  arguments 11 lines copy
• query_relationships reads unknown 5h ago

  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.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "required": [
      "subject"
    ],
    "properties": {
      "subject": {
        "type": "string"
      },
      "predicate": {
        "type": "string"
      }
    }
  }

  arguments 14 lines copy
• fuzzy_find_and_traverse reads unknown 13h ago

  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.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738

  {
    "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"
          }
        }
      }
    }
  }

  arguments 38 lines copy
• traverse_path unknown never probed

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

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334

  {
    "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
      }
    }
  }

  arguments 34 lines copy
• get_citable_passages unknown 5h ago

  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.

  mcp-tool

  1234567891011121314151617181920

  {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "default": 3,
        "maximum": 5,
        "minimum": 1
      },
      "query": {
        "type": "string"
      },
      "article": {
        "type": "string"
      }
    }
  }

  arguments 20 lines copy
• find_by_type reads unknown 13h ago

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

  mcp-tool

  1234567891011

  {
    "type": "object",
    "required": [
      "type"
    ],
    "properties": {
      "type": {
        "type": "string"
      }
    }
  }

  arguments 11 lines copy
• get_entity reads unknown 13h ago

  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.

  mcp-tool

  1234567891011

  {
    "type": "object",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string"
      }
    }
  }

  arguments 11 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.