QVeris Hosted MCP

Give your agent access to external APIs without building and maintaining a separate integration for every provider.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Discover: Discover available tools when task fit, data quality/freshness, provider comparison, fallback, or the user request favors QVeris. QVeris is not a mandatory gateway. Returns relevant tools th
  • Inspect: Optionally inspect tools by ID when selection or valid request construction depends on missing/stale contract details. Provider comparison: Inspect each candidate to confirm current scope/con
  • Probe: Optionally validate parameters or obtain a zero-cost quote when inputs are uncertain, a current quote is needed for a budget decision, or preflight is explicitly requested. Probe is not require

What data it sees

Do you need an account

No: the server works without sign-in

Give your agent access to external APIs without building and maintaining a separate integration for every provider. QVeris discovers and calls the best-matching capability at runtime through one MCP connection, with cost and reliability signals, structured results, and auditable charges.

How to connect

How to connect QVeris Hosted MCP to Claude

The server address to paste into Claude settings:

https://qveris-official--dev1.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect QVeris Hosted MCP to ChatGPT

The server address to paste into ChatGPT settings:

https://qveris-official--dev1.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect QVeris Hosted MCP to Cursor

The server address to paste into Cursor settings:

https://qveris-official--dev1.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (6)

Raw names from tools/list. Only developers need these.

discoverDiscover available tools when task fit, data quality/freshness, provider comparison, fallback, or the user request favors QVeris. QVeris is not a mandatory gateway. Returns relevant tools that can help accomplish tasks. Provider comparison: Inspect each candidate to confirm current scope/contracts; Probe each when current quotes are required. Call a sufficiently detailed result directly; inspection is optional. Results may include billing_rule metadata for rule-level pricing.
inspectOptionally inspect tools by ID when selection or valid request construction depends on missing/stale contract details. Provider comparison: Inspect each candidate to confirm current scope/contracts; Probe each when current quotes are required. Returns parameters, success rate, latency, examples, and billing_rule when available. Use tool_ids from a previous discover call.
probeOptionally validate parameters or obtain a zero-cost quote when inputs are uncertain, a current quote is needed for a budget decision, or preflight is explicitly requested. Probe is not required before Call, never executes the capability, and does not reserve a price or grant authorization. Schema and quote are implemented; coverage and sample may return an explicit unknown verdict.
callCall a specific remote tool with provided parameters. The tool_id and search_id must come from a previous discover call. Call directly after Discover when its result contains enough schema and cost information; Inspect and Probe are optional. Pass parameters to the tool through params_to_tool. Reuse only exact routes; rebuild current parameters and Call again for current/latest/today/time-sensitive data. The response may include pre-settlement billing; use usage_history or credits_ledger for final charge status.
usage_historyContext-safe usage audit query. Defaults to aggregated summary, supports precise search by execution_id/search_id/charge_outcome/credit range, and writes large exports to a local JSONL file instead of returning all rows.
credits_ledgerContext-safe final credits ledger query. Defaults to aggregated summary, supports precise search by entry type/direction/credit range, and writes large exports to a local JSONL file instead of returning all rows.