# Celo Docs (remote · docs.celo.org)

Search and read the Celo developer documentation

- Trust score: 78/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `docs.celo.org`: 78/100 (this document), [markdown](https://verifymcp.io/servers/org-celo-docs-mcp/docs.md), [page](https://verifymcp.io/servers/org-celo-docs-mcp/docs)

## Channel facts

- Endpoint: `https://docs.celo.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1276 tokens (~319/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Celo Docs MCP server?

Celo Docs is a hosted endpoint at https://docs.celo.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http org-celo-docs-mcp 'https://docs.celo.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-celo-docs-mcp": {
      "url": "https://docs.celo.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-celo-docs-mcp": {
      "type": "http",
      "url": "https://docs.celo.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-celo-docs-mcp]
url = "https://docs.celo.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-celo-docs-mcp": {
      "type": "remote",
      "url": "https://docs.celo.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-celo-docs-mcp --url 'https://docs.celo.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-celo-docs-mcp:
    url: "https://docs.celo.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-celo-docs-mcp": {
      "Transport": "http",
      "Url": "https://docs.celo.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-celo-docs-mcp -t streamable-http -u 'https://docs.celo.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-celo-docs-mcp": {
      "type": "http",
      "url": "https://docs.celo.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 74)

First indexed and scored.

## MCP tools (3)

### `search_celo_docs` (~150 tokens)

Search documentation

Search across the Celo Docs knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Celo Docs, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).

Input parameters:

- `query` (string, required): Search query

### `query_docs_filesystem_celo_docs` (~760 tokens)

Query documentation filesystem

Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Celo Docs documentation pages. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks.

This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`.

\**Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered.

\**Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path.

Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage.

Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call.

Examples (replace the placeholder paths with real ones from `tree` or search):
\- `tree / -L 2` — see the top-level directory layout
\- `rg -il "rate limit" /` — find all files mentioning "rate limit"
\- `rg -C 3 "apiK…

Input parameters:

- `command` (string, required): A shell command to run against the virtualized documentation filesystem (e.g., `rg -il "keyword" /`, `tree / -L 2`, `head -80 /path/file.mdx`).

### `submit_feedback` (~125 tokens)

Submit documentation feedback

Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.

Input parameters:

- `feedback` (string, required): A clear description of the documentation issue or suggestion — what is incorrect, outdated, missing, or confusing.
- `path` (string, required): The URL path of the documentation page the feedback is about (the page you were reading, without the `.mdx` extension).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-celo-docs-mcp/docs#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 77
- 2026-11-03: 77
- 2026-11-02: 76
- 2026-11-01: 76
- 2026-10-31: 75
- 2026-10-30: 75
- 2026-10-29: 74
- 2026-10-28: 74
- 2026-10-27: 74

## Common questions

### What is the Celo Docs MCP server?

Celo Docs is an MCP server listed in the public MCP registry as org.celo/docs-mcp. Search and read the Celo developer documentation. This page covers its hosted endpoint (https://docs.celo.org/mcp).

### Is the Celo Docs MCP server safe to use?

Celo Docs scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Celo Docs MCP server expose?

Celo Docs exposes 3 tools: search_celo_docs, query_docs_filesystem_celo_docs, submit_feedback. Their descriptions and schemas cost roughly 1,035 tokens of context every time the server is loaded.

### Does the Celo Docs MCP server require authentication?

No. We connected to Celo Docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Celo Docs MCP server still maintained?

Celo Docs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Celo Docs MCP server?

VerifyMCP ran 13 checks on Celo Docs, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://docs.celo.org/mcp
- Changelog RSS feed: https://verifymcp.io/servers/org-celo-docs-mcp/docs.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-celo-docs-mcp/docs/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/org-celo-docs-mcp/docs.json
- HTML version of this page: https://verifymcp.io/servers/org-celo-docs-mcp/docs