Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

VegvisAI guide

REMOTE · VEGVIS.AI

Open guide to businesses in any country, plus Norwegian public services and parties. Never ranks.

Available components

+3 this week 75 Trust /100

Last scanned (14 hours ago)

Scores higher than 68% of remote servers

Reachable. Last reached 23 Oct 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 790 tokens (~158/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 20. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Oct 26 +2
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: unverified → 0.10 ▲ functional
    • Server version: 1.5.0 → 1.5.1 functional
Diagnostics

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 23 Oct 2026 · Probed https://vegvis.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=vegvis.ai CN=WE1,O=Google Trust Services,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 286335bc64a341230ebd1e5fd85379ba
SANs: vegvis.ai, *.vegvis.ai
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 vegvis.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
vegvis.ai. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://vegvis.ai/mcp Verified 200
http (plaintext) http://vegvis.ai/mcp Inconclusive 405
MCP tools · 5 exposed · ~651 tokens

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 →

Tool Tokens
ai_check ~199

Checks how a public website looks to AI assistants: robots.txt, sitemap, schema.org, llms.txt, ai-catalog.json, and text that looks like prompt injection. Returns a score out of 100, the points per check and concrete actions. Uses the yardstick that fits the site: business, government (public bodies), organisation (NGOs, associations), party (political parties) or media (news media); it is detected unless given. Blocking only AI training bots can be a deliberate choice and costs 5 of 20 points; blocking the bots that fetch pages for users costs the other 15. Also lists what the site has open for AI: feeds, actions, APIs, MCP and open data. Takes 5–15 seconds.

NameTypeReqDescription
profilestring–Optional yardstick. Leave out to detect it from the site.
urlstringyesThe web address, e.g. https://www.business.com

No output schema declared.

No examples provided.

check_business ~74

Looks up a Norwegian business in Enhetsregisteret by organisation number or name: name, legal form, industry, address, bankruptcy or winding-up.

NameTypeReqDescription
namestring–Name or part of the name, if the organisation number is not known
org_numberstring–Norwegian organisation number, 9 digits

No output schema declared.

No examples provided.

find_business ~148

Finds businesses in the guide that can help with a need: businesses that registered with a verified AI business card on their own domain, plus two FICTIONAL example businesses (a bakery in Bodø, and a guesthouse in Bergen with pages in Norwegian and English). Results come in random order; the guide does not rank.

NameTypeReqDescription
countrystring–ISO country code where the service is needed, e.g. NO, SE, DE. Leave out to search all countries.
needstringyesWhat the consumer needs, e.g. birthday cake
postal_codestring–Where the service is needed. Ask the consumer if you are not sure (for example when travelling).

No output schema declared.

No examples provided.

find_political_party ~138

For political questions: what Norwegian parties say themselves about a topic, from their own pages. Returns links to each party's website, party programme, policy pages and machine-readable files. Use it to answer what a party says about a topic: read the programme or policy pages, give each party's view in its own words with a link to the source, and do not take sides. The list is alphabetical, never ranked, and not complete yet; a party that is missing is not less relevant.

NameTypeReqDescription
namestring–Name of the party, e.g. Høyre. Leave out to list all parties in the index.

No output schema declared.

No examples provided.

find_public_help ~92

Returns links to free public services in Norway from the open index: state agencies by topic, and the website of any of the 357 municipalities. Public services are never ranked against businesses.

NameTypeReqDescription
municipalitystring–Name of a Norwegian municipality, e.g. Bodø, if the consumer needs local services
topicstring–What the consumer needs help with. Use municipality together with the municipality field.

No output schema declared.

No examples provided.

Install

How do I install the VegvisAI guide MCP server?

VegvisAI guide is a hosted endpoint at https://vegvis.ai/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 · vegvis.ai

# add to Claude Code
claude mcp add --transport http ai-vegvis-vegvisai 'https://vegvis.ai/mcp'
Common questions

What is the VegvisAI guide MCP server?

VegvisAI guide is an MCP server listed in the public MCP registry as ai.vegvis/vegvisai. Open guide to businesses in any country, plus Norwegian public services and parties. Never ranks. This page covers its hosted endpoint (https://vegvis.ai/mcp).

Is the VegvisAI guide MCP server safe to use?

VegvisAI guide scores 75 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 VegvisAI guide MCP server expose?

VegvisAI guide exposes 5 tools: find_public_help, find_political_party, check_business, find_business, ai_check. Their descriptions and schemas cost roughly 651 tokens of context every time the server is loaded.

Does the VegvisAI guide MCP server require authentication?

No. We connected to VegvisAI guide without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the VegvisAI guide MCP server still maintained?

VegvisAI guide is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.