The Creditcorp MCP server — Public API guides

What MCP is here for

The Model Context Protocol is an open standard for exposing tools to language-model agents. Credicorp's public MCP server lets an assistant fetch accurate, live Credicorp figures — products, a representative quote, eligibility criteria, the application steps and the loyalty ladder — without scraping the marketing site or hallucinating numbers. It sits on the unauthenticated public ring, so an agent can call it with no credential.

The tool catalogue

Tool	Returns
list_products	The three products with names + one-liners + enabled flag
product_details	A product's published description + figures
get_quote	A representative Business Loan quote for an amount + term
eligibility_criteria	Who can apply
how_to_apply	The application steps
loyalty_tiers	The tier ladder + thresholds

Calling it

The transport is MCP Streamable HTTP: one JSON-RPC 2.0 request in, one response out, at POST /public/v1/mcp. The methods are the MCP standard set — initialize, tools/list, tools/call, ping. A GET returns the server card for discovery. See calling the MCP server for a full request.

Frequently asked questions

Does the MCP server need authentication?

No. The public MCP server is on the unauthenticated /public/v1 ring and exposes only read-only, published data, so any agent can call it without a token. There is also a token-gated partner MCP server on /partner/v1/mcp for authenticated capabilities.

Which transport does it use?

MCP Streamable HTTP over JSON-RPC 2.0. You POST a single JSON-RPC request to /public/v1/mcp and receive a single JSON-RPC response. A GET returns the server card for discovery.