Veripoint MCP server
ai.veripoint/mcp
We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 85 of 100 (grade B), higher than 31.2% of the 33,003 registry servers that responded over HTTPS that day. Ready for MCP Registry. Not ready for Gemini. Unverified for Claude and ChatGPT.
Measured facts
- Score
- 85B
- Sign-in
- OAuth
- Tools listed
- Behind sign-in
- Protocol version
- None returned
Store readiness
| Store | Status | Reason |
|---|---|---|
| Claude Connectors Directory | Unverified | Nothing failed, but tools/list returns tools, inputSchema is an object schema, readOnlyHint or destructiveHint on every tool and Human-readable title on every tool could not run in a check without credentials. |
| ChatGPT app directory | Unverified | Nothing failed, but tools/list returns tools, inputSchema is an object schema, readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT) and Human-readable title on every tool could not run in a check without credentials. |
| Gemini Connected Apps | Not ready | Blocked by First metadata URL Gemini tries answers 200 with the required fields. |
| Official MCP Registry | Ready | No blocking check failed. |
MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.
3 checks to fix
- Fails
First metadata URL Gemini tries answers 200 with the required fields
auth_gemini_discoveryBlocks Gemini.
Measured
Gemini tries https://auth.openai.com/.well-known/oauth-authorization-server first and gets HTTP 200 without authorization server metadata; it uses that answer aMake https://auth.openai.com/.well-known/oauth-authorization-server answer HTTP 200 with the authorization server metadata (authorization_endpoint, token_endpoint, response_types_supported ["code"], registration_endpoint). Gemini tries http
- Warning
Client registration (DCR or Client ID Metadata Documents)
auth_registrationMeasured
No registration_endpoint and no client_id_metadata_document_supportedAdd a Dynamic Client Registration endpoint (RFC 7591) or set client_id_metadata_document_supported: true; otherwise every store needs a manually issued client id.
- Warning
initialize latency
latencyMeasured
1936 msBring initialize under 1.5 s: avoid cold starts and upstream calls in the handshake.
11 checks passed, 13 did not run
Passed. Served over HTTPS, initialize over Streamable HTTP, GET answers SSE or 405, Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, refresh_token grant advertised.
Not run. Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, serverInfo name and version, Server instructions, tools capability declared, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT), Human-readable title on every tool, Tool descriptions. The tools sit behind sign-in, and the check runs without credentials.
Run a fresh check
This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.
README badge
The badge shows the latest score for this URL and links to this report.
Markdown
[](https://www.mcpstamp.com/r/ai-veripoint-mcp/)
HTML
<a href="https://www.mcpstamp.com/r/ai-veripoint-mcp/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fveripoint.sens663.chatgpt.site%2Fmcp" alt="McpStamp score" height="20"></a>
About this server
AI financial research for private and public companies, with evidence and saved workspace reports.
The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.
More grade B servers
All grade B servers · All server reports · State of MCP readiness, November 2026