Skip to content
MCPSTAMP
MCP server report

CreditPolicy.ai MCP server

ai.creditpolicy/creditpolicy

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. Unverified for Claude, ChatGPT and Gemini.

Measured facts

Score
85B
Sign-in
OAuth
Tools listed
Behind sign-in
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
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 Unverified Nothing failed, but tools/list returns tools and inputSchema is an object schema could not run in a check without credentials.
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.

Fixes

2 checks to fix

  1. Warning

    initialize latency

    latency

    Measured 1651 ms

    Bring initialize under 1.5 s: avoid cold starts and upstream calls in the handshake.

  2. Warning

    JSON-RPC error for unknown method

    jsonrpc_errors

    Measured HTTP 401 instead of a JSON-RPC error

    Route the method first and answer unknown methods with JSON-RPC error -32601 before the auth check, or return a JSON-RPC error body with the 401.

18 checks passed, 7 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, GET answers SSE or 405, serverInfo name and version, Server instructions, tools capability declared, 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), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised.

Not run. 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.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for CreditPolicy.ai

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fcreditpolicy.ai%2Fapi%2Fmcp)](https://www.mcpstamp.com/r/ai-creditpolicy-creditpolicy/)

HTML

<a href="https://www.mcpstamp.com/r/ai-creditpolicy-creditpolicy/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fcreditpolicy.ai%2Fapi%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Australian lender credit policy library and client files for mortgage and finance brokers.
Registry name
ai.creditpolicy/creditpolicy
Remote URL
https://creditpolicy.ai/api/mcp
Version
1.1.0
Website
creditpolicy.ai/mcp
Checked
2 November 2026, engine 1.2.0, no credentials

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