Vericto account (OAuth)

com.verictoPublished by vericto.comOfficial publisherv1.0.0Updated Nov 7, 2026

Your Vericto workspace over OAuth: setup status, rules, CI reports, docs search and SQL checks.

The publisher's own server: Vericto SQL Firewall

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & Analytics

Overview

AI-generated overview

Remote Vericto workspace server over OAuth that lets an assistant check setup status, rules, CI reports, docs search and SQL checks.

What you can do
  • Check workspace setup status and configuration rules
  • Review CI reports from the workspace
  • Search workspace documentation
  • Run or review SQL checks
  • No tool list is published, so exact actions are limited to what the description names.
When to use it
Useful when you work inside a Vericto workspace and want an assistant to look up setup status, rules, CI reports, documentation or SQL check results without leaving the conversation.
Requirements
A remote endpoint at mcp.vericto.com using streamable HTTP; OAuth authentication is required, so you need a Vericto account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to your Vericto workspace, so the assistant can see whatever that account can see, including CI reports and SQL check results. No tool list is published, so review the permissions granted during sign-in before connecting.

Installation

In SourceWeft

  1. Open Vericto account (OAuth) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.vericto%2Faccount/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "vericto-account-oauth": {
      "type": "http",
      "url": "https://mcp.vericto.com/mcp/account"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 7, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Vericto integrations