Skip to content

Upstar MCP server

dev.upstar/upstarupstar.devstreamable-httpv1.0.1Scanned

Rising GitHub repos per topic, ranked by star velocity, plus repos spotted early. Free, read-only.

9 tools: 4 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 4 write, 5 read.
  • Reads private data · 3
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Upstar MCP server can do

The Upstar MCP server is published by upstar.dev, a domain the MCP Registry verified. It has 9 tools. It can create or change data (4 tools: emerging, spotted_early, topic_ranking and trending), but cannot delete data. 5 tools only read.

3 tools read private data (get_repo, list_topics and search).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Changes things 4Claude Code: ask
  • emergingSmall GitHub repositories (under 1,000 stars a week ago, at least 30 days old) gaining stars at least twice as fast as in a usual week, by that ratio; optionally in one topic.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Small GitHub repositories (under 1,000 stars a week ago, at least 30 days old) gaining stars at least twice as fast as in a usual week, by that ratio; optionally in one topic. The same list as Upstar's Emerging page (or the topic's Emerging tab).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Emerging repositories
  • spotted_earlyRepositories whose stars at least doubled since Upstar first ranked them in a topic, at any rank: when, in which topic and at which rank it first ranked them, their stars then and …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Repositories whose stars at least doubled since Upstar first ranked them in a topic, at any rank: when, in which topic and at which rank it first ranked them, their stars then and now. Most grown first: the same list as Upstar's Spotted early page.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Spotted early by Upstar
  • topic_rankingRanks a topic's GitHub repositories by star velocity (stars gained ÷ √stars before) over the last 24 hours, 7 days or 30 days, with the stars each gained: the same list as the topi…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Ranks a topic's GitHub repositories by star velocity (stars gained ÷ √stars before) over the last 24 hours, 7 days or 30 days, with the stars each gained: the same list as the topic's page on Upstar. Page with offset (next_offset).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: A topic's ranking
Only reads 5Show 5 read-only tools
  • get_collectionA collection's ranking (score = momentum and health with the collection's weights) and its rising newcomers under 90 days old: the same lists as the collection's page on Upstar.No findings

    Why it is in this group

    • The name "get_collection" says "get": a word for reading.
    Description, as the server wrote it
    A collection's ranking (score = momentum and health with the collection's weights) and its rising newcomers under 90 days old: the same lists as the collection's page on Upstar.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: A collection's ranking
  • get_repoOne GitHub repository as Upstar sees it, the same facts as its Upstar page: stars and gains, its usual week, its star total week by week over 12 weeks, its topics and ranks, when U…Reads private dataNo findings

    Why it is in this group

    • The name "get_repo" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_repo" says "get" and "repo": it reads repositories.
    • private-dataThe description's first sentence says "repository": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    One GitHub repository as Upstar sees it, the same facts as its Upstar page: stars and gains, its usual week, its star total week by week over 12 weeks, its topics and ranks, when Upstar spotted it, its latest release, license, activity and collections. Answers for every repository with an Upstar page, kept-out ones included; blocked ones have none.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: A repository's facts
  • list_collectionsUpstar's collections: open-source tools that do one job, or alternatives to one product, each ranked by momentum and health.No findings

    Why it is in this group

    • The name "list_collections" says "list": a word for reading.
    Description, as the server wrote it
    Upstar's collections: open-source tools that do one job, or alternatives to one product, each ranked by momentum and health. Use a slug with get_collection.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: List Upstar's collections
  • list_topicsLists the topics Upstar ranks GitHub repositories in (emulation, self-hosted, Rust, MCP…): slug, name, category, description and how many repositories rank in each this week.Reads private dataNo findings

    Why it is in this group

    • The name "list_topics" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "repository": it reads repositories.
    Description, as the server wrote it
    Lists the topics Upstar ranks GitHub repositories in (emulation, self-hosted, Rust, MCP…): slug, name, category, description and how many repositories rank in each this week. Use a slug with topic_ranking or emerging.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: List Upstar's topics

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:22 UTC, unchanged since Nov 4, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://upstar.dev/mcp: tools/list returned 9 tools to an anonymous client, including emerging (write), spotted_early (write), topic_ranking (write), trending (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools7 changed.~7 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http upstar https://upstar.dev/mcp
claude mcp add --transport http upstar https://upstar.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__upstar__get_collection",
      "mcp__upstar__get_repo",
      "mcp__upstar__list_collections",
      "mcp__upstar__list_topics",
      "mcp__upstar__search"
    ],
    "ask": [
      "mcp__upstar__emerging",
      "mcp__upstar__spotted_early",
      "mcp__upstar__topic_ranking",
      "mcp__upstar__trending"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as upstar. Review it before you use it.

Capability tags behind 3 rules
  • mcp__upstar__get_repo private-data
  • mcp__upstar__list_topics private-data
  • mcp__upstar__search private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.upstar/upstar/verify?hash=cee908866ecbee918c1c987ad159e4dc6e664106e4aa86916e324282af9c3729" | jq -e '.changed == false'

Pinned hash cee908866ecb, from Nov 17, 2026, 09:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.upstar/upstar/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.upstar/upstar
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.upstar/upstar.svg)](https://radar.anlyon.com/servers/dev.upstar/upstar)

Source: MCP Registry. Synced Nov 3, 2026, 20:17 UTC.

Upstar MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Upstar MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Upstar MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Upstar MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Upstar MCP server have?

9 tools: 4 write, 5 read. emerging, spotted_early, topic_ranking, trending, get_collection, get_repo, list_collections, list_topics and 1 more.

Does the Upstar MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Upstar MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Upstar MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.