# Context Awesome (remote · www.context-awesome.com)

MCP server for accessing curated awesome list documentation

- Trust score: 66/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `www.context-awesome.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/bh-rat-context-awesome/api-mcp.md), [page](https://verifymcp.io/servers/bh-rat-context-awesome/api-mcp)
- npm · `context-awesome`: 35/100, [markdown](https://verifymcp.io/servers/bh-rat-context-awesome/context-awesome.md), [page](https://verifymcp.io/servers/bh-rat-context-awesome/context-awesome)

## Channel facts

- Endpoint: `https://www.context-awesome.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## 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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 396 tokens (~198/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http bh-rat-context-awesome https://www.context-awesome.com/api/mcp
```

### Codex

```toml
[mcp_servers.bh-rat-context-awesome]
url = "https://www.context-awesome.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bh-rat-context-awesome": {
      "type": "remote",
      "url": "https://www.context-awesome.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bh-rat-context-awesome --url https://www.context-awesome.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  bh-rat-context-awesome:
    url: "https://www.context-awesome.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "bh-rat-context-awesome": {
      "type": "http",
      "url": "https://www.context-awesome.com/api/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-08-03 (score 66, +1)

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

### 2026-07-31 (score 65, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 63, +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-07-28 (score 62, +1)

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

### 2026-07-27 (score 61, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (2)

### `find_awesome_section` (~228 tokens)

Discovers sections/categories across awesome lists matching a search query and returns matching sections from awesome lists.

You MUST call this function before 'get_awesome_items' to discover available sections UNLESS the user explicitly provides a githubRepo or listId.

Selection Process:
1\. Analyze the query to understand what type of resources the user is looking for
2\. Return the most relevant matches based on:
   \- Name similarity to the query and the awesome lists section
   \- Category/section relevance of the awesome lists 
   \- Number of items in the section
   \- Confidence score

Response Format:
\- Returns matching sections of the awesome lists with metadata
\- Includes repository information, item counts, and confidence score
\- Use the githubRepo or listId with relevant sections from results for get_awesome_items

For ambiguous queries, multiple relevant sections will be returned for the user to choose from.

Input parameters:

- `confidence` (number): Minimum confidence score (0-1)
- `limit` (number): Maximum sections to return
- `query` (string, required): Search terms for finding sections across awesome lists

### `get_awesome_items` (~168 tokens)

Retrieves items from a specific awesome list or section with token limiting. You must call 'find_awesome_section' first to discover available sections, UNLESS the user explicitly provides a githubRepo or listId.

Input parameters:

- `githubRepo` (string): GitHub repo path (e.g., 'sindresorhus/awesome') from find_awesome_section results
- `listId` (string): UUID of the list (from find_awesome_section results)
- `offset` (number): Pagination offset for retrieving more items
- `section` (string): Category/section name to filter
- `subcategory` (string): Subcategory to filter
- `tokens` (number): Maximum number of tokens to return (default: 10000). Higher values provide more items but consume more tokens.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/bh-rat-context-awesome/api-mcp#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 65
- 2026-07-31: 65
- 2026-07-30: 63
- 2026-07-29: 63
- 2026-07-28: 62
- 2026-07-27: 61
- 2026-07-26: 61

## Links

- Remote endpoint: https://www.context-awesome.com/api/mcp
- Repository: https://github.com/bh-rat/context-awesome
- Website: https://www.context-awesome.com/
- Changelog RSS feed: https://verifymcp.io/servers/bh-rat-context-awesome/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/bh-rat-context-awesome/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/bh-rat-context-awesome/api-mcp