Skip to content
Vitextra logo

Vitextra MCP server

Which MCP servers are Vitextra's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-20

← Back to Vitextra

Whose server it is
  • Registry namecom.vitextra/knowledge-baseverified in the MCP registry

The registry name sits under vitextra.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-20
  • Stateanswerschecked 2026-10-20
  • Tools4
  • Server calls itselfvitextra-knowledge-base
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 604 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: Look up colleagues and view org charts; Publish announcements and run quick polls for staff.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 15, the first on 2026-10-20
  • INITE MCP score72 of 100answers 100 · does the job 0 · definitions 100 · context 100 · connects 100
  • What an agent can do with it0 of 2 use cases
  • Answered100% of days15 of 15 daily checks
  • Median first answer553 ms
  • Space in an agent's context≈ 537 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • cannot · Look up colleagues and view org charts
  • cannot · Publish announcements and run quick polls for staff
  • not sure · Filter large SharePoint lists without writing code

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-20
  • search_knowledge_base

    Search Vitextra knowledge base, documentation, product pages, how-to guides, FAQ, glossary and blog. Returns titles, page URLs, Markdown URLs and short descriptions; read a page in full with get_document.

  • get_document

    Read a Vitextra page as Markdown: knowledge base article, how-to guide, blog post, product page (with pricing, features, platforms, FAQ), the FAQ or the glossary. Pass a url from search_knowledge_base or list_products.

  • list_products

    List all Vitextra products with their page URLs, Markdown URLs and one-line descriptions.

  • ask

    NLWeb-compatible question answering over the site content: returns the most relevant pages as schema.org objects in the NLWeb result format (url, name, site, score, description, schema_object).

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "knowledge-base": {
      "type": "http",
      "url": "https://vitextra.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http vitextra https://vitextra.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://vitextra.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.