hn-tech-signal-mcp

Overview Schema Source Related Servers Discussions Admin

github_trending_ai

Read-onlyIdempotent

Identify emerging AI/tech trends by searching GitHub for trending repositories by topic. Returns JSON with stars, forks, and language.

Instructions

Search GitHub for trending repositories by topic.

A surge of starred repos on a topic is a strong adoption signal. No auth required (60 req/h). Set GITHUB_TOKEN for 5,000 req/h.

Args: params (GithubTrendingAiInput): - topic (str): GitHub topic tag (e.g. 'llm', 'mcp', 'ai-agents') - limit (int): Repos to return (1–15) - min_stars (int): Minimum stars filter - sort (str): 'stars' or 'updated'

Returns: str: JSON with topic, total_found, count, repos[]. Each repo: name, description, stars, forks, language, topics, updated_at, url.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`sort`	Yes
`count`	Yes
`repos`	Yes
`topic`	Yes
`fetched_at`	Yes
`total_found`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.5.0Sep 30, 2026

addedOutput schema / $defs

Added value: +{
+  "GithubRepo": {
+    "additionalProperties": false,
+    "properties": {
+      "description": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Description"
+      },
+      "forks": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Forks"
+      },
+      "language": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Language"
+      },
+      "name": {
+        "title": "Name",
+        "type": "string"
+      },
+      "stars": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Stars"
+      },
+      "topics": {
+        "anyOf": [
+          {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Topics"
+      },
+      "updated_at": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Updated At"
+      },
+      "url": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Url"
+      }
+    },
+    "required": [
+      "name",
+      "description",
+      "stars",
+      "forks",
+      "language",
+      "topics",
+      "updated_at",
+      "url"
+    ],
+    "title": "GithubRepo",
+    "type": "object"
+  }
+}

addedOutput schema / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / count

Added value: +{
+  "title": "Count",
+  "type": "integer"
+}

addedOutput schema / properties / fetched_at

Added value: +{
+  "title": "Fetched At",
+  "type": "string"
+}

addedOutput schema / properties / repos

Added value: +{
+  "items": {
+    "$ref": "#/$defs/GithubRepo"
+  },
+  "title": "Repos",
+  "type": "array"
+}

removedOutput schema / properties / result

Removed value: -{
-  "title": "Result",
-  "type": "string"
-}

addedOutput schema / properties / sort

Added value: +{
+  "title": "Sort",
+  "type": "string"
+}

addedOutput schema / properties / topic

Added value: +{
+  "title": "Topic",
+  "type": "string"
+}

addedOutput schema / properties / total_found

Added value: +{
+  "title": "Total Found",
+  "type": "integer"
+}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "topic",
+  "sort",
+  "fetched_at",
+  "total_found",
+  "count",
+  "repos"
+]

changedOutput schema / title

Previous value: -"github_trending_aiOutput"New value: +"GithubTrendingOutput"

First observedv0.2.4Jul 11, 2026

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context beyond the annotations: unauthenticated rate limit (60 req/h) versus 5,000 req/h with GITHUB_TOKEN, plus the JSON return shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose sentence and the adoption-signal rationale before the arg/return listings. The structured Args/Returns block is scannable, though it partially duplicates what the schema already encodes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only search tool with an output schema, the description covers auth/rate limits, all parameters, and the return shape, so an agent has what it needs. Minor gaps: no pagination or result-truncation behavior notes, and no explicit routing against the other signal-source siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Reported schema description coverage is 0%, so the description carries the parameter burden and does so reasonably: it names all four params, gives the limit range (1–15), the sort values ('stars'/'updated'), and concrete topic examples. It doesn't add much beyond the values already in the schema, but it does compensate for the stated coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Search) and resource (GitHub trending repositories) with the scoping dimension (by topic). The GitHub source inherently distinguishes it from the hn_* / arxiv_* / lobsters_* siblings, though it never explicitly frames that contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'A surge of starred repos on a topic is a strong adoption signal' explains why one would want this data, which implies usage, but there is no explicit when-to-use-this-vs-alternatives guidance and no mention of the sibling tools that surface other signal types.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server