CreditPolicy.ai
ai.creditpolicyPublished by creditpolicy.aiOfficial publisherv1.1.0Updated Oct 25, 2026
Australian lender credit policy library and client files for mortgage and finance brokers.
Overview
A remote MCP endpoint from CreditPolicy.ai giving assistants access to an Australian lender credit policy library and client files for mortgage and finance brok
- What you can do
- The manifest lists no tools, so the exact operations are not documented. Based on the registry description, the server is intended to give an assistant access to an Australian lender credit policy library and to client files used by mortgage and finance brokers. No instructions or README are provided, so how the assistant queries policies or client records cannot be confirmed from the available material.
- When to use it
- Consider it if you are an Australian mortgage or finance broker who wants an assistant to work with lender credit policy material and client files. Because no tools or documentation are published, verify its capabilities directly before relying on it.
- Requirements
- A remote streamable HTTP endpoint at creditpolicy.ai; no local package is needed. The manifest declares no authentication, environment variables or headers, but access to client files may still require an account or sign-in that is not described here.
Installation
In SourceWeft
- Open CreditPolicy.ai in the dashboard and add it to a workspace.
- 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/ai.creditpolicy%2Fcreditpolicy/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"creditpolicy-ai": {
"type": "http",
"url": "https://creditpolicy.ai/api/mcp"
}
}
}Tools
0Version history
2- v1.1.0LatestOct 1, 2026
- v1.0.0Sep 16, 2026
Score
67% 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 listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- 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.