com.vericto/account
Vericto account (OAuth)
Is the Vericto account (OAuth) MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-15.
Your Vericto workspace over OAuth: setup status, rules, CI reports, docs search and SQL checks.
needs auth probed 2026-11-15 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":{"code":"UNAUTHORIZED","message":"Authorization required. Sign in with OAuth: the protected resource - Endpoint
- https://mcp.vericto.com/mcp/account (streamable-http)
- Host
- mcp.vericto.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.vericto.com/mcp/account registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server api.vericto.com, PKCE S256, grants authorization_code, refresh_token.
Scopes setup:read proxy:read events:read docs:read config:read ruleset:read reports:read sql:check.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://vericto.com/docs/mcp#oauth
- Registry
- active, updated 2026-11-07 · registry entry
Compare this server with others.
More servers
Other registry entries on mcp.vericto.com.
- Vericto: database guardrails for AI agents com.vericto/mcp · needs auth
Servers that mention account.
- AdAdvisor MCP Server ai.adadvisor/mcp-server · needs auth
- Inside Ads ad.inside/inside-ads · alive
- AIﾉアカリ☆ One-Minute Akari ai.ai-akari/one-minute-akari · paid (402)
- ai.augmentev/paseo · needs auth
- ai.aqta/seal · alive
- Google Ads ai.b77/google-ads · needs auth
- Bindry ai.bindry/bindry · needs auth
- Boolsai Scan ai.boolsai/scan · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.