# VegvisAI guide (remote · vegvis.ai)

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

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `vegvis.ai`: 75/100 (this document), [markdown](https://verifymcp.io/servers/ai-vegvis-vegvisai/vegvis.md), [page](https://verifymcp.io/servers/ai-vegvis-vegvisai/vegvis)

## Channel facts

- Endpoint: `https://vegvis.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add --transport http ai-vegvis-vegvisai 'https://vegvis.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-vegvis-vegvisai": {
      "url": "https://vegvis.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-vegvis-vegvisai": {
      "type": "http",
      "url": "https://vegvis.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-vegvis-vegvisai]
url = "https://vegvis.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-vegvis-vegvisai": {
      "type": "remote",
      "url": "https://vegvis.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-vegvis-vegvisai --url 'https://vegvis.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-vegvis-vegvisai:
    url: "https://vegvis.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-vegvis-vegvisai": {
      "Transport": "http",
      "Url": "https://vegvis.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-vegvis-vegvisai -t streamable-http -u 'https://vegvis.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-vegvis-vegvisai": {
      "type": "http",
      "url": "https://vegvis.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 75, +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.

### 2026-10-20 (score 74, +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.

### 2026-10-18 (score 73, +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.

### 2026-10-15 (score 72, +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.

### 2026-10-13 (score 71, +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.

### 2026-10-11 (score 70, +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.

### 2026-10-10 (score 69, +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.

### 2026-10-07 (score 68, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Stability: unverified → 0.10
- [functional] Server version: 1.5.0 → 1.5.1

## MCP tools (5)

### `find_public_help` (~92 tokens)

Find public help

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.

Input parameters:

- `municipality` (string): Name of a Norwegian municipality, e.g. Bodø, if the consumer needs local services
- `topic` (string): What the consumer needs help with. Use municipality together with the municipality field.

### `find_political_party` (~138 tokens)

What the parties say themselves

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.

Input parameters:

- `name` (string): Name of the party, e.g. Høyre. Leave out to list all parties in the index.

### `check_business` (~74 tokens)

Check a Norwegian business in Brønnøysund

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

Input parameters:

- `name` (string): Name or part of the name, if the organisation number is not known
- `org_number` (string): Norwegian organisation number, 9 digits

### `find_business` (~148 tokens)

Find a business

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.

Input parameters:

- `country` (string): ISO country code where the service is needed, e.g. NO, SE, DE. Leave out to search all countries.
- `need` (string, required): What the consumer needs, e.g. birthday cake
- `postal_code` (string): Where the service is needed. Ask the consumer if you are not sure (for example when travelling).

### `ai_check` (~199 tokens)

AI check of a website

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.

Input parameters:

- `profile` (string): Optional yardstick. Leave out to detect it from the site.
- `url` (string, required): The web address, e.g. https://www.business.com

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-vegvis-vegvisai/vegvis#diagnostics

## Score history

- 2026-10-23: 75
- 2026-10-22: 75
- 2026-10-21: 74
- 2026-10-20: 74
- 2026-10-19: 73
- 2026-10-18: 73
- 2026-10-17: 72
- 2026-10-16: 72
- 2026-10-15: 72
- 2026-10-14: 71
- 2026-10-13: 71
- 2026-10-12: 70
- 2026-10-11: 70
- 2026-10-10: 69
- 2026-10-07: 68
- 2026-10-04: 66

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

## Links

- Remote endpoint: https://vegvis.ai/mcp
- Repository: https://github.com/vegvisai/vegvisai
- Website: https://vegvis.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-vegvis-vegvisai/vegvis.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-vegvis-vegvisai/vegvis.json
- HTML version of this page: https://verifymcp.io/servers/ai-vegvis-vegvisai/vegvis