Skip to content

HyperXosist-Agent Remote MCP server

io.github.KG-NINJA/hyperxosist-agentKG-NINJAstreamable-httpv2.5.1Scanned

X feedback discovery, noise-reduced query planning, signal filtering, and AI handoffs.

3 tools: 2 change things and 1 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 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 HyperXosist-Agent Remote MCP server can do

The HyperXosist-Agent Remote MCP server is published by the GitHub account KG-NINJA. It has 3 tools. It can create or change data (2 tools: hyperxosist_filter_signals and hyperxosist_build_handoff), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

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.

Last scanned Nov 15, 2026, version 2.5.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.

3 tools

Changes things 2Claude Code: ask
  • hyperxosist_build_handoffUse to turn previously collected X feedback into a structured Signal-to-Fix package and coding-agent prompt.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
    Use to turn previously collected X feedback into a structured Signal-to-Fix package and coding-agent prompt. It does not perform general summarization, search the web, scrape X, or modify source code.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • hyperxosist_filter_signalsUse after X posts or tweet text have already been collected.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
    Use after X posts or tweet text have already been collected. Separates actionable bugs, feature requests, and UX friction from empty praise, engagement bait, and spam. It does not fetch, scrape, or search X.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • hyperxosist_search_planUse only for specialized X (Twitter) research planning: complaints, bug reports, feature requests, product feedback, or community signals.No findings

    Why it is in this group

    • The name "hyperxosist_search_plan" says "search": a word for reading.
    Description, as the server wrote it
    Use only for specialized X (Twitter) research planning: complaints, bug reports, feature requests, product feedback, or community signals. Builds multiple noise-reduced official x.com/search URLs and quality scores. It is not general web search and does not scrape X or collect posts.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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 private-data or untrusted-input or outbound.

Reads private data0
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 20, 2026, 18:58 UTC, unchanged since Oct 22, 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
2
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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.kgninja.dev/mcp: tools/list returned 3 tools to an anonymous client, including hyperxosist_filter_signals (write), hyperxosist_build_handoff (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.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http hyperxosist-agent https://mcp.kgninja.dev/mcp
claude mcp add --transport http hyperxosist-agent https://mcp.kgninja.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__hyperxosist-agent__hyperxosist_search_plan"
    ],
    "ask": [
      "mcp__hyperxosist-agent__hyperxosist_filter_signals",
      "mcp__hyperxosist-agent__hyperxosist_build_handoff"
    ],
    "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 hyperxosist-agent. Review it before you use it.

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/io.github.KG-NINJA/hyperxosist-agent/verify?hash=51f03219086d592c71342d90d6518845721fbae70770684a9b16c3386ac9783f" | jq -e '.changed == false'

Pinned hash 51f03219086d, from Nov 15, 2026, 23:17 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.KG-NINJA/hyperxosist-agent/changes.xml

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

Badge

Anlyon Radar badge for io.github.KG-NINJA/hyperxosist-agent
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.KG-NINJA/hyperxosist-agent.svg)](https://radar.anlyon.com/servers/io.github.KG-NINJA/hyperxosist-agent)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:17 UTC.

HyperXosist-Agent Remote MCP server: questions and answers

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

Is the HyperXosist-Agent Remote MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 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 HyperXosist-Agent Remote MCP server delete data?

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

Can the HyperXosist-Agent Remote 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 HyperXosist-Agent Remote MCP server have?

3 tools: 2 write, 1 read. hyperxosist_filter_signals, hyperxosist_build_handoff and hyperxosist_search_plan.

Does the HyperXosist-Agent Remote MCP server need sign-in or OAuth?

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

Does the HyperXosist-Agent Remote MCP server send data to outside services?

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

Has the HyperXosist-Agent Remote MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.