> ## Documentation Index
> Fetch the complete documentation index at: https://docs.core3.io/llms.txt
> Use this file to discover all available pages before exploring further.

# CORE3 MCP tools reference

> Complete reference for all 23 core3 tools—parameters, structuredContent fields, REST equivalents, and links to PoL methodology.

This page catalogs every tool exposed by **`core3`**. All tools are read-only. Most accept a **`slug`** parameter identifying the project or exchange.

<Tip>
  Prefer **`resolve_project_slug`** to map a brand name or ticker to a canonical project slug before calling project-specific tools. Use **`get_projects_list`** for the full catalog. Exchange slugs often differ from brand names (for example Coinbase → `coinbase-exchange`); there is no `resolve_exchange_slug` tool—only call exchange tools with a confirmed CORE3 slug.
</Tip>

## Health

| Tool           | Parameters | Returns                                       | REST equivalent                                   |
| -------------- | ---------- | --------------------------------------------- | ------------------------------------------------- |
| `check_health` | —          | Text confirmation that the service is healthy | `GET /projects_data/v1/health` (requires API key) |

## Projects — lookup

| Tool                   | Parameters | Key `structuredContent` fields                                                                                                    | REST equivalent                              | Methodology |
| ---------------------- | ---------- | --------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- | ----------- |
| `resolve_project_slug` | `query`    | `status` (`resolved` \| `ambiguous` \| `not_found`), `entityType`, `query`, optional `resolvedSlug` / `resolvedName`, `matches[]` | Uses projects list (no dedicated REST route) | —           |

On `ambiguous` or `not_found`, do not guess a slug or answer for a different entity.

## Projects — data

| Tool                                        | Parameters | Key `structuredContent` fields                                                    | REST equivalent                                  | Methodology                                         |
| ------------------------------------------- | ---------- | --------------------------------------------------------------------------------- | ------------------------------------------------ | --------------------------------------------------- |
| `get_projects_list`                         | —          | `projects[]` with `name`, `slug`; `totalProjects`                                 | `GET /projects_data/v1/list`                     | —                                                   |
| `get_project_age`                           | `slug`     | `projectLaunchedAt`, `protocolLaunchedAt`                                         | Operational section (longevity)                  | [Project PoL methodology](/project-pol-methodology) |
| `get_project_github_activity`               | `slug`     | `heatmap`, `commitsCount7d`                                                       | Operational section                              | [Project PoL methodology](/project-pol-methodology) |
| `get_project_team_track_record`             | `slug`     | `isEducationRelevant`, `isWorkExperienceRelevant`, `isBusinessExperienceRelevant` | Operational section                              | [Project PoL methodology](/project-pol-methodology) |
| `get_project_certifications`                | `slug`     | `isIso27001Present`, `isCcssPresent`, `ccssLevel`, `isSoc2Present`                | Security section                                 | [Project PoL methodology](/project-pol-methodology) |
| `get_project_red_flags`                     | `slug`     | `mmRedFlags`, `investorRedFlags`                                                  | Reputational section                             | [Project PoL methodology](/project-pol-methodology) |
| `get_project_social_fraud`                  | `slug`     | `social` (Twitter, website, Google Trends metrics)                                | Reputational section                             | [Project PoL methodology](/project-pol-methodology) |
| `get_project_public_registration`           | `slug`     | `isPublicRegistrationPresent`, `jurisdictionQuality`                              | Regulatory section                               | [Project PoL methodology](/project-pol-methodology) |
| `get_project_proof_of_voice_pros_and_cons`  | `slug`     | `pros[]`, `cons[]`                                                                | `GET /projects_data/v1/{slug}/proof_of_voice`    | [Proof of Voice](/proof-of-voice)                   |
| `get_project_proof_of_voice_expert_reviews` | `slug`     | `reviews[]` with `author`, `content`, `publishedAt`                               | `GET /projects_data/v1/{slug}/proof_of_voice`    | [Proof of Voice](/proof-of-voice)                   |
| `get_project_market_data`                   | `slug`     | `price`, `marketCap`                                                              | `GET /projects_data/v1/{slug}` (partial overlap) | —                                                   |

For red flags and empty Proof of Voice lists, **`none_identified`** means no findings—not a failed fetch.

`jurisdictionQuality` on public registration is licence-tier quality (**1–4**, lower = stricter jurisdiction). It may be empty or `not_returned` when unavailable.

## Projects — category quality scores

Each category score tool returns envelope fields plus a **`score`** object with `score` (numeric, higher = better), `rating` (AAA–D), and `confidence` (Exceptional, High, Moderate, or Low). Responses include `scoreType: "category_quality"` and `scoreDirection: "higher_is_better"`. These are **not** overall PoL (lower = safer).

| Tool                                    | Parameters     | Returns                                                 | REST equivalent                                                     | Methodology                                         |
| --------------------------------------- | -------------- | ------------------------------------------------------- | ------------------------------------------------------------------- | --------------------------------------------------- |
| `get_project_security_score`            | `slug`         | Category quality score for security                     | `GET /projects_data/v1/{slug}/pol/by_category` (security slice)     | [Project PoL methodology](/project-pol-methodology) |
| `get_project_financial_score`           | `slug`         | Category quality score for financial                    | `GET /projects_data/v1/{slug}/pol/by_category` (financial slice)    | [Project PoL methodology](/project-pol-methodology) |
| `get_project_operational_score`         | `slug`         | Category quality score for operational                  | `GET /projects_data/v1/{slug}/pol/by_category` (operational slice)  | [Project PoL methodology](/project-pol-methodology) |
| `get_project_reputational_score`        | `slug`         | Category quality score for reputational                 | `GET /projects_data/v1/{slug}/pol/by_category` (reputational slice) | [Project PoL methodology](/project-pol-methodology) |
| `get_project_regulatory_score`          | `slug`         | Category quality score for regulatory                   | `GET /projects_data/v1/{slug}/pol/by_category` (regulatory slice)   | [Project PoL methodology](/project-pol-methodology) |
| `get_project_categories_scores_dynamic` | `slug`, `days` | `points[]` time series with per-category quality scores | `GET /projects_data/v1/{slug}/pol/by_category/history/chart?days=`  | [Project PoL methodology](/project-pol-methodology) |

## Exchanges — category quality scores

| Tool                                     | Parameters     | Returns                                                 | REST equivalent                                                      | Methodology                                 |
| ---------------------------------------- | -------------- | ------------------------------------------------------- | -------------------------------------------------------------------- | ------------------------------------------- |
| `get_exchange_security_score`            | `slug`         | Category quality score for security                     | `GET /exchanges_data/v1/{slug}/pol/by_category` (security slice)     | [CEX PoL methodology](/cex-pol-methodology) |
| `get_exchange_transparency_score`        | `slug`         | Category quality score for transparency                 | `GET /exchanges_data/v1/{slug}/pol/by_category` (transparency slice) | [CEX PoL methodology](/cex-pol-methodology) |
| `get_exchange_solvency_score`            | `slug`         | Category quality score for solvency                     | `GET /exchanges_data/v1/{slug}/pol/by_category` (solvency slice)     | [CEX PoL methodology](/cex-pol-methodology) |
| `get_exchange_categories_scores_dynamic` | `slug`, `days` | `points[]` time series with per-category quality scores | `GET /exchanges_data/v1/{slug}/pol/by_category/history/chart?days=`  | [CEX PoL methodology](/cex-pol-methodology) |

## Example response

Calling **`get_project_security_score`** with `slug: "ethereum"` returns an MCP tool result like this:

```json theme={null}
{
  "content": [
    {
      "type": "text",
      "text": "Security score fetched successfully for \"ethereum\". Score: 86.6. Rating: AAA. Confidence: High. Higher is better; lower is worse (category quality score, not overall PoL)."
    }
  ],
  "structuredContent": {
    "status": "ok",
    "entityType": "project",
    "metric": "security_score",
    "requestedSlug": "ethereum",
    "resolvedSlug": "ethereum",
    "scoreType": "category_quality",
    "scoreDirection": "higher_is_better",
    "interpretationHint": "This is a category quality/calculation score, not overall PoL. Higher scores are better (stronger quality). Lower scores are worse. Never treat a high category score as higher risk.",
    "score": {
      "score": 86.6,
      "rating": "AAA",
      "confidence": "High"
    }
  }
}
```

The **`content`** array is for the agent's conversational context. The **`structuredContent`** object is structured JSON your code or agent logic should use.

Historical tools such as **`get_project_categories_scores_dynamic`** return `points[]` where each point includes a Unix `timestamp` and category quality score objects for each category (security, financial, operational, reputational, regulatory).

## REST endpoints without MCP tools

These [Projects Data API](/projects-data-api) and [Exchanges Data API](/exchanges-data-api) operations are **not** available as MCP tools:

* Search and trending
* Ratings with pagination and filters
* Index-level PoL and overall/aggregate PoL (lower = safer)
* Per-entity metric-level breakdowns
* History by timestamp range (`from` / `to` query parameters)
* Exchange list, dashboard, listed assets, and transparency stats

See [Projects Data API](/projects-data-api) and [Exchanges Data API](/exchanges-data-api) for the full REST surface.

<Tip>Need full REST API access, higher rate limits, or commercial terms? Contact [info@core3.io](mailto:info@core3.io)</Tip>

## Next steps

* Connect your client: [Getting started](/mcp-getting-started)
* Request REST API access: [CORE3 for partners](/core3-for-partners)
* Interpret scores: [Project PoL scoring logic](/project-pol-scoring-logic) and [CEX PoL scoring logic](/cex-pol-scoring-logic)