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.

Kviria

REMOTE · API.KVIRIA.COM

Location understanding for AI agents: know where, then navigate there. Beta: contiguous US.

Available components

0 this week 40 Trust /100

Last scanned (15 hours ago)

Scores higher than 40% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

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 Security100
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

What we tested

Checks we ran (5)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 6 Nov 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
  • 17 Oct 26 0
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • Authorization: unverified → pass ▲ security
    • First check of Authorization: pass security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 10 Oct 26 0
    • Stability: 0.60 → fail ▼ security
    • Tool “kviria” rewrote its description, which is the text the model reads security
    • Schema quality: 593 → 706 ▼ functional
    • “kviria” made “transcript” required, so existing callers break ▼ functional
    • Server version: 1.0.0 → 1.0.3 functional
    • “kviria” added an optional parameter “state” cosmetic
    • “kviria” reworded the description of “anchor” cosmetic
    • “kviria” reworded the description of “confirmation” cosmetic
    • “kviria” reworded the description of “rangeM” cosmetic
    • “kviria” reworded the description of “transcript” cosmetic
    • “kviria” dropped the optional parameter “candidates” cosmetic
    • “kviria” dropped the optional parameter “intent” cosmetic
    • “kviria” dropped the optional parameter “references” cosmetic
    • “kviria” made “anchor” optional cosmetic
  • 28 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
  • 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
  • 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 0
    • Stability: unverified → 0.03 ▲ functional
  • 19 Sept 26 0

    First indexed and scored.

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 21 Nov 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 9 Oct 2026 8 Jan 2027 ECDSA 256 ECDSA-SHA256 1289dde60e60b5121316597338da053d
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. DS published 19718 13 Verified
kviria.com. DS published 2371 13 Verified
api.kviria.com. Verified address RRset verified with the apex keys
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://api.kviria.com/.well-known/oauth-protected-resource/mcp"

Bearer realm="OAuth", resource_metadata="https://api.kviria.com/.well-known/oauth-protected-resource/mcp"
Header Value
strict-transport-security max-age=15552000
content-security-policy frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
www-authenticate Bearer realm="OAuth", resource_metadata="https://api.kviria.com/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://api.kviria.com/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://api.kviria.com/mcp
Authorisation server https://api.kviria.com

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 Auth required 401
http (plaintext) http://api.kviria.com/mcp HTTPS enforced 301 https://api.kviria.com/mcp
MCP tools · 1 exposed · ~706 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
kviria ~706

Kviria finds the place, address or street corner a user means near their current position and returns its verified coordinate with an evidence trail. When to call: on every user turn of a place conversation, from the first time the user mentions a place, a kind of place, an address, a street, a corner or what is around them, until the place is settled. That includes yes or no answers, picks ("the second one"), corrections ("no, the other one"), follow-ups ("what's across from it") and questions about your last answer ("are you sure?"). Kviria resolves each of these from the state, so do not answer them yourself. What to send: transcript is the user's whole last turn, word for word. state is the `state` field of the previous kviria response, copied exactly: that field only, never the whole response; send an empty string on the first call. anchor is the user's current position exactly as you were given it: send it on the first call, and after that only when the position changes; never invent or round it. What comes back, and your move: one - the place is settled; say its name and distance exactly as returned. one_unconfirmed - ask "Is it {name} ({distanceM} m)?" and send the user's answer as the next call. many - name the candidates with their distances, ask which one, and send the user's answer as the next call. none - Kviria looked and found nothing; say so and ask for a nearby business or landmark. unclear - ask the user to say more about the place. not_a_place_request - the user's words are not about a place; reply to the user yourself. Phrase your reply from the returned facts only; never invent a place, a distance or any other detail. Distances are meters; convert them for your user. Coverage: the contiguous United States. Outside it the answer is none with an out_of_coverage entry and the turn is free; tell the user instead of retrying. Errors: 400 invalid_state means the state was altered; start again with an empty state. 503 parser_unavailable: do not…

NameTypeReqDescription
anchorobject–The user's current position - Kviria resolves relative to this point. Required on the first call of a conversation; later calls may leave it out while the user has not moved.
confirmationstring–"on" (default): a place the user named only in part is returned as one_unconfirmed, and its coordinate is released only after the user verifies it. "off": it is returned as one immediately, for agent…
rangeMinteger–Search radius around the anchor in meters (clamped to 50-350).
statestring–The `state` field of the previous kviria response, copied character for character: that field only, never the whole response, and never shortened. Empty string on the first call.
transcriptstringyesThe user's whole last turn, word for word: yes or no, corrections, hesitations and everything around the place included. Never shorten, rephrase, correct or complete it. If one turn arrived in pieces…
NameTypeReqDescription
candidatesarray–The candidates to present on many. Never send them back: send state.
categorystring–The category that was asked for and is absent, on a none decision.
confirmedboolean–True when the user verified the target through the confirm gate.
decisionstringyesThe decision for this turn: how many answers there are and whether the single answer is certain, or not_a_place_request when the user's words are not about a place. An exact address is "one" with the…
evidencearrayyesWhy this answer: the gate trail behind the decision. Present none of this to the user; it exists for trust and auditability.
statestringyesThe conversation state. Send it back unchanged as `state` on the next call.
target––The settled target (one), or the target waiting for the user's yes or no (one_unconfirmed, without a location).

No examples provided.

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.

remote · api.kviria.com

# add to Claude Code
claude mcp add --transport http com-kviria-kviria 'https://api.kviria.com/mcp'
Common questions

What is the Kviria MCP server?

Kviria is an MCP server listed in the public MCP registry as com.kviria/kviria. Location understanding for AI agents: know where, then navigate there. Beta: contiguous US. This page covers its hosted endpoint (https://api.kviria.com/mcp).

Is the Kviria MCP server safe to use?

Kviria scores 40 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 706 tokens of context every time the server is loaded.

Does the Kviria MCP server require authentication?

Yes. Kviria asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Kviria MCP server still maintained?

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

What did VerifyMCP test on the Kviria MCP server?

VerifyMCP ran 5 checks on Kviria, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Kviria: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.