_ registry / mcp streamable-http · checked 5h ago

vitextra-knowledge-base

https://vitextra.com

Registry code: 54d2426218d1dc66

api record

Public knowledge base of Vitextra (SharePoint web parts and Microsoft 365 apps): product pages with pricing, knowledge base articles, how-to guides, FAQ, glossary and blog. Use search_knowledge_base to find pages, then get_document with a returned url to read the full page as Markdown. list_products shows all products. Every content page also has a Markdown version at the same address with the .md extension.

endpoint
https://vitextra.com/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 it live, free and safe measured by this hub
Is vitextra-knowledge-base live?
Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
Is vitextra-knowledge-base free to use?
Yes — the hub reached it with no key and no payment.
What tools does vitextra-knowledge-base have?
4 tools: ask, search_knowledge_base, get_document, list_products.
Is vitextra-knowledge-base 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
81ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

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.

  • list_products open 5h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "language": {
      "type": "string",
      "description": "Two-letter language code of the content, e.g. en, de, fr, ru. Default: en."
    }
  }
}
    arguments 10 lines
  • ask unknown 5h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "The question or search text."
    },
    "language": {
      "type": "string",
      "description": "Two-letter language code of the content, e.g. en, de, fr, ru. Default: en."
    }
  }
}
    arguments 16 lines
  • search_knowledge_base unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "Number of results, default 8."
    },
    "query": {
      "type": "string",
      "description": "Search text in natural language or keywords."
    },
    "category": {
      "enum": [
        "article",
        "howto",
        "faq",
        "term",
        "post",
        "product",
        "document"
      ],
      "type": "string",
      "description": "Optional filter: article (knowledge base article), howto (how-to guide), faq, term (glossary), post (blog), product, document (PDF)."
    },
    "language": {
      "type": "string",
      "description": "Two-letter language code of the content, e.g. en, de, fr, ru. Default: en."
    }
  }
}
    arguments 35 lines
  • get_document unknown 5h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Page URL (https://vitextra.com/en/products/...) or path (/en/support/kb/1234); a trailing .md is accepted."
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 54d2426218d1dc66.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/54d2426218d1dc66/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/54d2426218d1dc66/badge.svg)](https://brick.blue/agent/54d2426218d1dc66?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

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

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

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.