Kviria
REMOTE · API.KVIRIA.COM · SCANNED SEP 28
The location engine for AI agents: one verified coordinate from where a user means. Beta: US.
Available components
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 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
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.
remote · api.kviria.com
claude mcp add --transport http com-kviria-kviria 'https://api.kviria.com/mcp'
{
"mcpServers": {
"com-kviria-kviria": {
"url": "https://api.kviria.com/mcp"
}
}
} {
"servers": {
"com-kviria-kviria": {
"type": "http",
"url": "https://api.kviria.com/mcp"
}
}
} [mcp_servers.com-kviria-kviria] url = "https://api.kviria.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-kviria-kviria": {
"type": "remote",
"url": "https://api.kviria.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-kviria-kviria --url 'https://api.kviria.com/mcp' --transport streamable-http
mcp_servers:
com-kviria-kviria:
url: "https://api.kviria.com/mcp" {
"McpServers": {
"com-kviria-kviria": {
"Transport": "http",
"Url": "https://api.kviria.com/mcp"
}
}
} assistant mcp add com-kviria-kviria -t streamable-http -u 'https://api.kviria.com/mcp'
{
"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.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 21 Sept 26 0
- 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 functional
- 20 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 19 Sept 26 65
First indexed and scored.
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 28 Sept 2026 · Probed https://api.kviria.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kviria.com | CN=WE1,O=Google Trust Services,C=US | 11 Aug 2026 | 10 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 8bbf079407d229820eee8b7164a7e745 |
| SANs: kviria.com, api.kviria.com, *.api.kviria.com | ||||||
| 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 secure
Validation of api.kviria.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| kviria.com. | present | 2371 | 13 | Verified |
| api.kviria.com. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.kviria.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.kviria.com/mcp | HTTPS enforced | 301 | https://api.kviria.com/mcp |
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 →
kviria Kviria ~593
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.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor | object | yes | 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`. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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). |
No examples provided.
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.