_ registry / mcp http-sse · checked 42m ago

mcp-typescript server on vercel

https://www.context-awesome.com

Registry code: 0babaa1a1303c7dd

api record

MCP server for accessing curated awesome list documentation

from a public catalogue that lists it, not from the operator

endpoint
https://www.context-awesome.com/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
179ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 2 tools
1 open 1 never probed 1 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_awesome_items open 2h ago

    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.

    mcp-tool

    {
      "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
    }
    arguments 33 lines
  • find_awesome_section unknown never probed

    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.

    mcp-tool

    {
      "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
    }
    arguments 28 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/0babaa1a1303c7dd/badge.svg)](https://brick.blue/agent/0babaa1a1303c7dd)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.