Skip to main content
The Model Context Protocol (MCP) is an open standard that lets AI agents call external tools and retrieve structured data during a conversation. CORE3 exposes a public MCP server named core3 so you can integrate category quality scores, Proof of Voice (PoV), and related risk metrics into agent workflows without building a custom REST integration.
MCP is defined by the open specification at modelcontextprotocol.io. This documentation covers CORE3’s server—not the full protocol tutorial.

​
What CORE3 offers

Through core3, you get 23 read-only tools that return CORE3 risk intelligence:
  • Project slug resolution — map brand names and tickers to canonical CORE3 slugs via resolve_project_slug
  • Project category quality scores — security, financial, operational, reputational, and regulatory (higher = better; not overall PoL)
  • Project metrics — age, GitHub activity, certifications, red flags, social fraud signals, public registration, and market data
  • Proof of Voice — expert reviews and structured pros/cons
  • Exchange category quality scores — security, transparency, and solvency (higher = better)
  • Historical trends — category score time series for projects and exchanges
Every tool is read-only. No write or mutation operations are exposed.
Overall Probability of Loss (PoL) — where lower = safer — is available through the REST APIs, not as an MCP tool. All MCP score tools return category quality scores (scoreType: "category_quality", higher = better).

​
Server identity

​
Scope and limitations

MCP exposes a curated public subset of CORE3 data. The full REST APIs offer search, ratings pagination, history by timestamp range, exchange dashboards, overall/index PoL, and other endpoints not available as MCP tools. See Projects Data API and Exchanges Data API for the full programmatic surface.
The public tool set may evolve as CORE3 expands its agent integration offering. Rate limits are subject to fair-use policies; contact CORE3 for production-scale REST access.

Getting started

Configure Cursor, Claude Desktop, or another MCP client

Tools reference

Full catalog of 23 tools with parameters and REST mappings

Project PoL methodology

Understand how category scores are calculated
Need full REST API access, higher rate limits, or commercial terms? Contact [email protected]

​
Next steps

  • Follow Getting started to connect your MCP client and run your first tool calls.
  • Use Tools reference when building agent prompts that need specific CORE3 data.
  • Request REST API access via CORE3 for partners if you need the full programmatic surface or commercial terms.