QVeris Agent Toolkit logo

QVeris Agent Toolkit

Organization
QVerisAI

Bring professional data and tools to the AI you already use: open-source MCP, CLI, SDKs, skills, and docs to find services, call them, and audit usage.

PublisherQVerisAI
Repositoryqveris-agent-toolkit
LanguageJavaScript
Forks
25
Stars
263
Available tools
0
Transport typestdio
Categories
LicenseMIT
Links
  • Connect tools to AI workflows

    QVeris Agent Toolkit exposes MCP capabilities that can be used by compatible AI clients and agents.

  • 0 available tools

    Browse the callable actions below, including names and descriptions when provided by the server.

  • Ready-to-copy setup

    Use the installation snippets to configure this server in your preferred MCP client.

  • Open source signals

    263 stars and 25 forks from the linked repository.


  • Professional data and tools across finance, search, weather, maps, documents, and more
  • Discover / Call is the default path; Inspect and Probe are conditional checks for missing/stale contracts, comparison, parameter validation, or a current quote
  • For provider comparison, Inspect every candidate when current scope or a complete contract must be confirmed; a Discover summary is not confirmation. Probe every candidate when the comparison requires a current quote. Reuse may preserve an exact route, never business parameters or results: build parameters from the current request, and make a fresh Call for current, latest, today, or other time-sensitive data.
  • Discover is free. Call returns structured pre-settlement billing, with final charge outcomes available through usage audit and credits ledger views.
  • NEW QVeris CLI โ€” command-line access to professional data and tools for agents. Learn more
  • Works with CLI / MCP / Python SDK / REST API

When to use QVeris: use it when built-in tools are insufficient, a provider must be found dynamically, comparison or fallback matters, or the user requests it. Keep using local or native tools when they already fit the task.


Quick Start

๐Ÿค– I'm an Agent

Your owner sent you here to learn about QVeris? โ†’ If you are an OpenClaw-style skill agent, use the official skill: skills/openclaw/qveris-official/SKILL.md โ†’ If you are running in Cursor / Claude Code / OpenCode, follow the Agent capability guide & install protocol โ†’ Default path: Discover (free) โ†’ Call; use Inspect or Probe only when additional verification is needed

๐Ÿง‘โ€๐Ÿ’ป I have OpenClaw / Cursor / Claude Code installed

Copy this to your Agent โ€” done in 30 seconds: Install QVeris skill following https://qveris.ai/skill/instruct.md and use QVERIS_API_KEY=your-key โ†’ Get API Key (free, 1,000 one-time trial credits after signup verification)

โš™๏ธ I'm a developer integrating via CLI / MCP / API / SDK

โ†’ QVeris CLI โ€” npm install -g @qverisai/cli or curl -fsSL https://qveris.ai/cli/install | bash โ†’ MCP Server Doc โ†’ REST API Doc โ†’ Python SDK


For Agents

If you are an AI Agent evaluating whether to use QVeris, here is what you need to know.

What QVeris gives you:

  • Discover โ€” find candidate services with natural language (free)
  • Inspect โ€” optionally check missing or stale parameters, available signals, and billing details
  • Call โ€” invoke a selected service and receive structured results and pre-settlement billing when available
  • Usage audit / Credits ledger โ€” review request and credit outcomes through the interfaces that expose them
  • QVeris CLI โ€” access services via qveris discover/inspect/call without preloading the full service catalog
  • Professional data and tools across finance, search, weather, maps, documents, social, blockchain, healthcare, and more
  • Per-tool execution history, success-rate, and latency signals when supplied

How to install:

  • CLI (recommended): curl -fsSL https://qveris.ai/cli/install | bash โ€” then use qveris discover/inspect/call
  • See SETUP.md โ€” supports OpenClaw / Claude Code / Cursor / OpenCode / Trae
  • Install does not modify shell startup files by default (session-scoped)
  • Must pass file checks + CLI verification to confirm success

How to explain to your owner:

QVeris helps me find a service when the tools I already have are insufficient, review its supported scope when needed, and call it. Installation does not change system configuration unless explicitly requested. Call pricing and usage or credit records depend on the selected capability and supported interface.

Billing and audit:

  • Discover: free
  • Call: priced by structured billing_rule; call responses may include compact pre-settlement billing
  • Final charge status: check qveris usage / usage_history
  • Final balance movement: check qveris ledger / credits_ledger
  • Free tier: 1,000 one-time trial credits after signup verification
  • $19 = 10,000 credits (pay-as-you-go, credits never expire)
  • Details: qveris.ai/pricing

30-Second Setup

  1. Get API Key (free, 1,000 one-time trial credits after signup verification)

OpenClaw users

Send this to your Agent:

Install QVeris skill following https://qveris.ai/skill/instruct.md and use QVERIS_API_KEY=your-key

The Agent will download the official OpenClaw skill and complete installation automatically.

Cursor / Claude Code / OpenCode users

Follow the setup guide (agent/SETUP.md) โ€” your Agent will configure MCP server + skill for your environment.

Cursor Marketplace plugin

The Cursor plugin in this repository bundles the hosted QVeris MCP connection and the official QVeris skills. After installing it from Cursor Marketplace:

  1. Open the plugin configuration and enter your QVERIS_API_KEY.
  2. Start a new agent session so Cursor can connect to https://mcp.qveris.ai/mcp.
  3. Confirm that discover, inspect, probe, call, usage_history, and credits_ledger are available.

The API key is stored by Cursor as a plugin variable and is never committed to this repository.

Gemini CLI extension

Install QVeris directly from this repository:

bash
gemini extensions install https://github.com/QVerisAI/qveris-agent-toolkit

During installation, enter your QVERIS_API_KEY when prompted. Gemini CLI stores it as a sensitive extension setting and connects to the hosted QVeris MCP server at https://mcp.qveris.ai/mcp.

Restart Gemini CLI after installation, then run /mcp to confirm that the qveris server is connected and its tools are available.

After setup

Try a task: "Check the current weather in Tokyo"

Safety:

  • Install does not modify your shell config (unless you explicitly ask)
  • Capability calls are remote API requests and do not grant a called service access to your local filesystem or system configuration
  • You can review usage and credit records through supported interfaces

QVeris CLI

Access professional data and tools from your agent's shell.

CLI executes as a subprocess and finds services on demand, without preloading the full service catalog. Instructions, commands, and results still consume context tokens. QVeris MCP likewise exposes a compact tool surface instead of every service definition.

bash
# Install (one-liner)
curl -fsSL https://qveris.ai/cli/install | bash

# Or via npm
npm install -g @qverisai/cli
bash
# Guided first call: `init` handles selection and validation for you
$ qveris init

# Default agent workflow: discover โ†’ call
$ qveris discover "weather forecast API"
Found 5 capabilities matching your query
1. gridpoint_forecast  by Weather.gov
   params: wfo (string, required), x (number, required), y (number, required)

$ qveris call 1 --params '{"wfo":"LWX","x":90,"y":90}'
โœ“ success
{ "forecast": "Sunny, high near 75..." }

# Optional when selection or request construction needs missing details
$ qveris inspect 1

# Optional when parameters need validation or a budget decision needs a current quote
$ qveris probe 1 --params '{"wfo":"LWX","x":90,"y":90}' --checks schema,quote

$ qveris usage --mode search --execution-id <execution_id>
# Confirms charge_outcome and actual_amount_credits for that call

Why CLI over MCP for agents?

CLIMCP
Token costNo upfront catalog schemas; command/result tokens still applyDepends on client context handling and exposed routing schemas
StartupInstant (npx or global install)Requires server process + transport handshake
OutputDeterministic schema, --json for parsingJSON over stdio, varies by client
ScalabilityOn-demand discovery, no catalog preloadingRouting schemas stay separate from catalog size
DebuggingVisible in terminal, --dry-run previewOpaque, buried in MCP logs
AuthBuilt-in endpoint; explicit override via QVERIS_BASE_URLSame

Usage and ledger commands default to aggregated summaries. Large audit exports are written to local JSONL files under .qveris/exports/ instead of being printed into Agent context.

When to use CLI: Agent frameworks that support exec / bash tool (Claude Code, OpenClaw, Cursor terminal, etc.) When to use MCP: IDE integrations that only support MCP protocol (Cursor inline, Claude Desktop)

Full CLI documentation: packages/cli/README.md


Developer Integration

Access methods

MethodUse caseDocs
CLI (recommended)Claude Code / OpenClaw / any agent with execCLI docs
MCP ServerCursor / Claude Desktop / MCP-only clientsMCP docs
Python SDKPython projects, agent frameworksPython SDK docs
TypeScript SDKNode.js / TypeScript projectsJS SDK docs
REST APIAny language, custom integrationsREST API docs

Stuck? See Troubleshooting & FAQ.

Service access workflow

Agents use three service-access actions, plus two read-only record paths:

ActionAPI endpointDescription
DiscoverPOST /searchFind capabilities with natural language, returns candidates
InspectPOST /tools/by-idsView capability details, parameters, quality signals
CallPOST /tools/executeInvoke a capability, get structured results, and optionally record model attribution
Usage auditGET /auth/usage/history/v2Check request status, charge outcome, and actual charge
Credits ledgerGET /auth/credits/ledgerCheck final credit balance movements

The reproducible Discover โ†’ Call accuracy benchmark measures grounded selection, parameterization, and real execution success per model. Its task set, runner, raw-record format, and deterministic scorer are public under benchmarks/discover-call.

Professional data and tool access

  • A service catalog across multiple professional-data and tool categories
  • Parameter schemas, examples, success rate, and average latency are available when supplied for a service
  • Supports private / org / public service visibility levels
  • Browse available services: qveris.ai/providers

Pricing

QVeris uses pay-as-you-go pricing. No subscriptions.

PlanPriceCreditsNotes
Free$01,000 trial creditsOne-time grant after signup verification
Standard$1910,000 creditsBuy on demand, never expire
ScaleSee pricing pageBased on selected packageCurrent packages and bonuses shown at checkout
  • Discover is free โ€” Agents can explore all capabilities at zero cost
  • Call is priced by structured billing rules, with final charges auditable through usage history and the credits ledger
  • No monthly fees, no auto-renewal
  • Details: qveris.ai/pricing

Security & Trust

  • Capability calls are remote API requests and do not grant a called service access to your local filesystem or system configuration
  • Session-scoped config, no system file modifications by default
  • Usage and credit records through supported interfaces
  • RBAC and per-capability access control
  • Rate limiting and quota enforcement
  • Enterprise options (VPC / private cloud) planned

What's New

Latest capabilities and updates: qveris.ai


Open Ecosystem

QVeris provides managed service access alongside open-source client tooling. We actively support the ecosystem by open-sourcing the MCP server, SDKs, Agent skills, and plugins, and by contributing code upstream.

Monorepo packages

This repository (QVerisAI/qveris-agent-toolkit) is the primary monorepo for QVeris client-side tooling:

PackagePathDistribution
MCP Serverpackages/mcp@qverisai/mcp
CLIpackages/cli@qverisai/cli
Python SDKpackages/python-sdkqveris
TypeScript SDKpackages/js-sdk@qverisai/sdk
Agent docsagent/โ€”
Skillsskills/โ€”

Recipes and ecosystem manifests

Use recipes/ for copy-paste workflow templates across finance research, risk/compliance, crypto monitoring, data analysis, and developer automation. The flagship recipes ship a runnable run.sh, and each package has runnable examples: js-sdk, MCP, CLI, and Python SDK.

Use ecosystem/ for the versioned QVeris manifest schema, marketplace-ready listing fields, permission declarations, contribution guide, and compatibility matrix.

Other repositories

RepositoryDescription
QVerisAI/open-qveris-skillsCommunity skills (stock copilot, market reports, etc.)
QVerisAI/openclaw-qveris-pluginOpenClaw plugin
QVerisAI/vscode-qveris-aiVS Code extension

Full list: github.com/orgs/QVerisAI/repositories

Distribution channels

Upstream contributions

QVeris actively contributes to the broader Agent ecosystem:


Community


โญ Star & Share

If you are building AI products or workflows that need professional data and tools, star this repo and share it with other builders.

Use QVeris Agent Toolkit MCP with multiple AI models

TypingMind connects MCP tools at the workspace level, so once QVeris Agent Toolkit is connected, you can use it with different AI models in TypingMind instead of setting it up separately for each model. This MCP runs locally through the TypingMind MCP connector on your device.

Setup guide to use the local connector

Use this when the MCP server needs access to local files, apps, or private resources on your computer.

1

Open the MCP settings

In TypingMind, go to Settings, Advanced Settings, then Model Context Protocol and choose Setup Connector.

  1. Open TypingMind in your browser.
  2. Click the Settings icon.
  3. Go to Advanced Settings.
  4. Open the Model Context Protocol section.
  5. Click Setup Connector and choose This Device.
TypingMind MCP connector setup screen with This Device selected
2

Run the connector command

Choose This Device, copy the command from TypingMind, and run it in Terminal. Keep the process running while you use MCP.

  1. Copy the setup command shown by TypingMind.
  2. Open Terminal on macOS or Windows Terminal on Windows.
  3. Paste and run the command.
  4. Approve the package install if Terminal asks you to proceed.
  5. Keep the Terminal window running while using MCP tools.
3

Add QVeris Agent Toolkit as a server

When the connector status is Ready, click Edit Servers and paste the MCP server configuration.

  1. Wait until the connector status shows Ready.
  2. Click Edit Servers.
  3. Paste the QVeris Agent Toolkit MCP server configuration.
  4. Save the server list.
  5. Refresh if you want to confirm the connector is still ready.
TypingMind MCP settings showing active server and Edit Servers button
{
  "mcpServers": {
    "qveris-agent-toolkit": {
      "command": "npx",
      "args": [
        "-y",
        "<mcp-server-package>"
      ]
    }
  }
}
4

Use it across models

Save the server list, open Plugins, enable the QVeris Agent Toolkit MCP tools, then select any supported AI model in TypingMind and use the tools in chat or assign them to an AI agent.

  1. Open the Plugins page in TypingMind.
  2. Enable the QVeris Agent Toolkit MCP tools.
  3. Start a chat and choose the AI model you want to use.
  4. Use the MCP tools in chat or assign them to an AI agent.
  5. Switch to another AI model whenever needed without reconnecting MCP.
TypingMind chat using enabled MCP tools with a selected AI model
Can you use QVeris Agent Toolkit to help me with this task?
QVeris Agent Toolkit
Sure. I read it.
Here is what I found using QVeris Agent Toolkit.

Frequently asked questions

What is the QVeris Agent Toolkit MCP server used for?

QVeris Agent Toolkit is an MCP server that lets compatible AI clients connect to external tools and context. In TypingMind, you can add this MCP server once and make its tools available in your AI workspace.

Can I use QVeris Agent Toolkit MCP with multiple AI models in TypingMind?

Yes. TypingMind connects MCP tools at the workspace level, so you can use QVeris Agent Toolkit with different AI models such as Claude, ChatGPT, Gemini, or other models you have configured in TypingMind without setting up the MCP server separately for each model.

Why use QVeris Agent Toolkit MCP with TypingMind?

TypingMind is one of the best frontends for LLM chat because it brings multiple AI models, prompts, plugins, AI agents, API keys, and MCP tools into one workspace. With QVeris Agent Toolkit connected, you can use its MCP tools across your preferred models while keeping your chat workflow organized in TypingMind.

How do I connect QVeris Agent Toolkit MCP to TypingMind?

QVeris Agent Toolkit runs through the TypingMind local MCP connector. This is best when the MCP server needs access to local files, desktop apps, command-line tools, or private resources on your computer.

What tools does QVeris Agent Toolkit MCP provide in TypingMind?

QVeris Agent Toolkit exposes MCP capabilities that can be enabled from the TypingMind Plugins page and used in chat or assigned to AI agents.

Do I need to share my API keys with TypingMind to use QVeris Agent Toolkit MCP?

No. TypingMind is local-first and lets you keep your model providers, API keys, prompts, and MCP configuration under your control. If QVeris Agent Toolkit requires authentication, add the required headers, OAuth settings, or local configuration for that MCP server when you create the connection.

Related MCP Servers

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter ๐Ÿ‘‡