Is the Bh Rat Context Awesome MCP server down?

mcp-registry/io.github.bh-rat/context-awesome · v0.1.0

healthy
Last checked 2026-10-23 16:05 UTC · handshake 141ms

As of 2026-10-23 16:05 UTC, the Bh Rat Context Awesome MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 2 minutes.

uptime (30d checks)
100%
checks observed
4,476
outages (90d)
2
tools
3

MCP server for accessing curated awesome list documentation

Install Bh Rat Context Awesome MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "bh-rat-context-awesome-mcp-server": {
      "type": "http",
      "url": "https://www.context-awesome.com/api/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 2 tool(s); ~569 tokens of tool definitions.
Scores higher than 47% of 15,589 MCP servers Glimind has audited.
Its tool list costs an agent ~569 tokens per session — lighter than 90% of servers.
84 → 85 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (2)

2 of 2 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: find_awesome_section, get_awesome_items

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.bh-rat%2Fcontext-awesome/fixes

find_awesome_section 1 change
{
  "name": "find_awesome_section",
  "description": "Discovers sections/categories across awesome lists matching a search query and returns matching sections from awesome lists.\n\nYou MUST call this function before 'get_awesome_items' to discover available sections UNLESS the user explicitly provides a githubRepo or listId.\n\nSelection Process:\n1. Analyze the query to understand what type of resources the user is looking for\n2. Return the most relevant matches based on:\n   - Name similarity to the query and the awesome lists section\n   - Category/se",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "number",
        "default": 10,
        "maximum": 50,
        "minimum": 1,
        "description": "Maximum sections to return"
      },
      "query": {
        "type": "string",
        "description": "Search terms for finding sections across awesome lists"
      },
      "confidence": {
        "type": "number",
        "default": 0.3,
        "maximum": 1,
        "minimum": 0,
        "description": "Minimum confidence score (0-1)"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_awesome_items 1 change
{
  "name": "get_awesome_items",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "listId": {
        "type": "string",
        "description": "UUID of the list (from find_awesome_section results)"
      },
      "offset": {
        "type": "number",
        "default": 0,
        "minimum": 0,
        "description": "Pagination offset for retrieving more items"
      },
      "tokens": {
        "type": "number",
        "description": "Maximum number of tokens to return (default: 10000). Higher values provide more items but consume more tokens."
      },
      "section": {
        "type": "string",
        "description": "Category/section name to filter"
      },
      "githubRepo": {
        "type": "string",
        "description": "GitHub repo path (e.g., 'sindresorhus/awesome') from find_awesome_section results"
      },
      "subcategory": {
        "type": "string",
        "description": "Subcategory to filter"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.bh-rat/context-awesome"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.bh-rat/context-awesome"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.bh-rat%2Fcontext-awesome.svg)](https://glimind.com/server/mcp-registry%2Fio.github.bh-rat%2Fcontext-awesome?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.bh-rat%2Fcontext-awesome?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.bh-rat%2Fcontext-awesome.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.bh-rat%2Fcontext-awesome.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.bh-rat%2Fcontext-awesome?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:81155af53a82d3f0…, first seen 2026-10-17, included at leaf 14915 of 52,964. Version history · verify what your client received.

Tools (3)

Compare: most reliable search servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Bh Rat Context Awesome MCP server down right now?

As of 2026-10-23 16:05 UTC, the Bh Rat Context Awesome MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 2 minutes.

How many tools does Bh Rat Context Awesome MCP server provide?

Bh Rat Context Awesome MCP server advertises 3 tools, including find_awesome_section, get_awesome_items, search_awesome_items.

How do I install Bh Rat Context Awesome MCP server?

Point your MCP client at this streamable-http endpoint: https://www.context-awesome.com/api/mcp

Is the Bh Rat Context Awesome MCP server safe to connect to an AI agent?

Glimind scanned all 2 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Bh Rat Context Awesome MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve