Skip to main content

MCP Services

Cred Protocol provides Model Context Protocol (MCP) services that enable AI agents and assistants to access on-chain credit scoring, financial reporting, and identity attestation data.
MCP is an open protocol that allows AI systems to securely interact with external tools and data sources. Learn more about MCP →

What is MCP?

The Model Context Protocol (MCP) is a standardized way for AI agents (like Claude, GPT, or custom LLM applications) to:
  • Discover available tools and their capabilities
  • Call tools with structured parameters
  • Receive structured responses
Unlike traditional REST APIs that require manual integration, MCP allows AI agents to automatically understand and use your tools through natural language.

Why Use MCP Services?

AI-Native Integration

AI agents can discover and use Cred Protocol tools without custom code

Natural Language

Users can ask “What’s this wallet’s credit score?” and the agent handles it

Sandbox Data

Safe testing with deterministic mock data - no real blockchain calls

No Authentication

MCP endpoints don’t require API tokens for easy development

Available Tools

ToolDescription
get_credit_scoreGet credit score (300-1000) for an Ethereum address
get_credit_scores_batchGet scores for multiple addresses at once
get_financial_summaryComprehensive financial report with assets, DeFi positions, and activity
get_identity_attestationsVerified identity credentials (ENS, Gitcoin Passport, POAPs)
get_portfolio_valueTotal portfolio value in USD across all chains
get_chain_portfolio_valuePortfolio value on a specific blockchain

Access Methods

Cred Protocol MCP services can be accessed two ways:

1. HTTP/REST Endpoints

Standard HTTP endpoints at /mcp/sandbox/* - works with any HTTP client:
curl https://api.credprotocol.com/mcp/sandbox/score/vitalik.eth

2. MCP Protocol (stdio)

Native MCP protocol for AI agents like Cursor, Claude Desktop, or custom MCP clients:
{
  "mcpServers": {
    "cred-protocol": {
      "command": "python",
      "args": ["mcp_server.py"]
    }
  }
}

MCP vs REST API

FeatureMCP ServicesREST API
DataSandbox/mockReal blockchain data
AuthenticationNone requiredAPI token required
PurposeDevelopment, AI agentsProduction applications
BillingFreeConsumes Cred Units
Response TimeInstant (~10ms)3-5 seconds
MCP services use sandbox data for safe testing. For production applications with real blockchain data, use the REST API.

Next Steps