# Kviria (remote · api.kviria.com)

The location engine for AI agents: one verified coordinate from where a user means. Beta: US.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `api.kviria.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-kviria-kviria/api.md), [page](https://verifymcp.io/servers/com-kviria-kviria/api)

## Channel facts

- Endpoint: `https://api.kviria.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

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

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 593 tokens (~593/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 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 Kviria MCP server?

Kviria is a hosted endpoint at https://api.kviria.com/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 com-kviria-kviria 'https://api.kviria.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-kviria-kviria": {
      "url": "https://api.kviria.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-kviria-kviria": {
      "type": "http",
      "url": "https://api.kviria.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-kviria-kviria]
url = "https://api.kviria.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-kviria-kviria --url 'https://api.kviria.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-kviria-kviria:
    url: "https://api.kviria.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-kviria-kviria": {
      "Transport": "http",
      "Url": "https://api.kviria.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-kviria-kviria -t streamable-http -u 'https://api.kviria.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-kviria-kviria": {
      "type": "http",
      "url": "https://api.kviria.com/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-09-28 (score 70, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 69, +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-09-25 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 68, +1)

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

### 2026-09-22 (score 67, +1)

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

### 2026-09-21 (score 66, 0)

- [functional] MCP protocol: Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
- [functional] MCP protocol version: 2026-07-28 → 2025-11-25

### 2026-09-20 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-19 (score 65)

First indexed and scored.

## MCP tools (1)

### `kviria` (~593 tokens)

Kviria

Kviria narrows a user's spoken reference down to exactly one place or address and returns its verified coordinate with an evidence trail. Call it with the user's raw message and their current anchor {lat, lng}. Phrase your reply from the returned facts ONLY: state names, distances, and categories exactly as returned; never invent distances, crosswalks, landmarks, opening hours, or any sensory detail. For a 'confirm' decision, ask the user "is it {name} ({distanceM} m)?" and pass their bare yes/no back as the next transcript, echoing the candidates array verbatim. For 'candidates', list them with their distances and ask which one; on the user's next message echo the SAME candidates array back so the engine binds the pick mechanically. Preserve the pendingConfirm marker on the candidate it came with. The target is the final outcome: present its coordinate, never paraphrase the place name. If the user rejects (no), present the returned candidates or ask for more detail. Do not call with invented anchors; the anchor is the user's real position. Kviria is in beta: current coverage is the contiguous United States (approximately lat 24.4 to 49.5, lng -125.0 to -66.8). Queries outside the covered area return an honest notFound with an out_of_coverage evidence entry, and that turn is free. Tell the user the area is outside current coverage instead of retrying.

Input parameters:

- `anchor` (object, required): The user's current position - Kviria resolves relative to this point.
- `candidates` (array): The pending candidates from the previous response, echoed VERBATIM (including the pendingConfirm marker) so clarification answers and confirm yes/no bind mechanically.
- `confirmation` (string): "on" (default): a single survivor emits a confirm decision, and the coordinate is released only after the user verifies it. "off": agents without a human in the loop get direct resolution.
- `intent` (object): The structured meaning of the user's words. Send exactly one of transcript or intent. Category filters take EXACT labels from the area's real categories (provided in every response). Unfiltered `acro…
- `rangeM` (integer): Search radius around the anchor in meters (clamped to 50-1000).
- `references` (array): Previously resolved places, most recent first, so "it" and "that cafe" resolve on later turns. Optional. Echo any lat/lng Kviria returned so distances stay real.
- `transcript` (string): The user's raw message (voice transcript or text), as spoken, typos and all. Do not normalize or paraphrase it. Mutually exclusive with `intent`.

Output parameters:

- `candidates` (array): The pending candidate set. Echo it back verbatim on the next turn.
- `category` (string): The absent category on notFound decisions.
- `confirmed` (boolean): True when the user verified the target through the confirm gate.
- `decision` (string): The decision for this turn. An exact address resolves as "resolved" with the door facts riding target.address; several door clusters for one number come back as "candidates".
- `evidence` (array): Why this answer: the gate trail behind the decision. Present none of this to the user; it exists for trust and auditability.
- `target`: The resolved or pending target (on resolved, confirm, address).

## Diagnostics

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

## Score history

- 2026-09-28: 70
- 2026-09-27: 69
- 2026-09-26: 69
- 2026-09-25: 68
- 2026-09-24: 68
- 2026-09-23: 67
- 2026-09-22: 67
- 2026-09-21: 66
- 2026-09-20: 66
- 2026-09-19: 65

## Common questions

### What is the Kviria MCP server?

Kviria is an MCP server listed in the public MCP registry as com.kviria/kviria. The location engine for AI agents: one verified coordinate from where a user means. Beta: US. This page covers its hosted endpoint (https://api.kviria.com/mcp).

### Is the Kviria MCP server safe to use?

Kviria scores 70 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 Kviria MCP server expose?

Kviria exposes 1 tool: kviria. Their descriptions and schemas cost roughly 593 tokens of context every time the server is loaded.

### Does the Kviria MCP server require authentication?

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

### Is the Kviria MCP server still maintained?

Kviria is still listed as active in the MCP registry. We last reached this channel on 28 September 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://api.kviria.com/mcp
- Website: https://kviria.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-kviria-kviria/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-kviria-kviria/api.json
- HTML version of this page: https://verifymcp.io/servers/com-kviria-kviria/api