HyperXosist-Agent Remote MCP
REMOTE · MCP.KGNINJA.DEV · SCANNED SEP 20
X feedback discovery, noise-reduced query planning, signal filtering, and AI handoffs.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 240 tokens (~80/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the HyperXosist-Agent Remote MCP server?
HyperXosist-Agent Remote MCP is a hosted endpoint at https://mcp.kgninja.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.kgninja.dev
claude mcp add --transport http kg-ninja-hyperxosist-agent 'https://mcp.kgninja.dev/mcp'
{
"mcpServers": {
"kg-ninja-hyperxosist-agent": {
"url": "https://mcp.kgninja.dev/mcp"
}
}
} {
"servers": {
"kg-ninja-hyperxosist-agent": {
"type": "http",
"url": "https://mcp.kgninja.dev/mcp"
}
}
} [mcp_servers.kg-ninja-hyperxosist-agent] url = "https://mcp.kgninja.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kg-ninja-hyperxosist-agent": {
"type": "remote",
"url": "https://mcp.kgninja.dev/mcp",
"enabled": true
}
}
} openclaw mcp add kg-ninja-hyperxosist-agent --url 'https://mcp.kgninja.dev/mcp' --transport streamable-http
mcp_servers:
kg-ninja-hyperxosist-agent:
url: "https://mcp.kgninja.dev/mcp" {
"McpServers": {
"kg-ninja-hyperxosist-agent": {
"Transport": "http",
"Url": "https://mcp.kgninja.dev/mcp"
}
}
} assistant mcp add kg-ninja-hyperxosist-agent -t streamable-http -u 'https://mcp.kgninja.dev/mcp'
{
"mcpServers": {
"kg-ninja-hyperxosist-agent": {
"type": "http",
"url": "https://mcp.kgninja.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 0
- DNSSEC: fail → pass ▲ security
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.kgninja.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kgninja.dev | CN=WE1,O=Google Trust Services,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ed160149d9dc20c80e24b24e61394a3b |
| SANs: kgninja.dev, mcp.kgninja.dev, *.mcp.kgninja.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.kgninja.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| kgninja.dev. | present | 2371 | 13 | Verified |
| mcp.kgninja.dev. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.kgninja.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.kgninja.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
hyperxosist_build_handoff ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| feedback | array | yes | Previously collected X feedback text. |
| productName | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| agentPrompt | object | yes | – |
| handoff | object | yes | – |
| signalToFixInput | object | yes | – |
| type | – | yes | – |
No examples provided.
hyperxosist_filter_signals ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| feedback | array | yes | Previously collected X post text to classify in memory. |
| Name | Type | Req | Description |
|---|---|---|---|
| discard | array | yes | – |
| discardCount | integer | yes | – |
| keep | array | yes | – |
| keepCount | integer | yes | – |
| summary | object | yes | – |
| type | – | yes | – |
No examples provided.
hyperxosist_search_plan ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| intent | string | yes | An X-specific research goal, for example: Find user complaints and bug reports on X about Acme. |
| Name | Type | Req | Description |
|---|---|---|---|
| estimatedCostUsd | number | yes | – |
| mission | object | yes | – |
| missionId | string | yes | – |
| paymentPolicy | object | yes | – |
| qualityScores | array | yes | – |
| queries | array | yes | – |
| requiresPaymentForAutomatedProductionUse | boolean | yes | – |
| searchUrls | array | yes | – |
| type | – | yes | – |
No examples provided.
What is the HyperXosist-Agent Remote MCP server?
HyperXosist-Agent Remote MCP is listed in the public MCP registry as io.github.KG-NINJA/hyperxosist-agent. X feedback discovery, noise-reduced query planning, signal filtering, and AI handoffs. This page covers its hosted endpoint (https://mcp.kgninja.dev/mcp).
Is the HyperXosist-Agent Remote MCP server safe to use?
HyperXosist-Agent Remote MCP scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the HyperXosist-Agent Remote MCP server expose?
HyperXosist-Agent Remote MCP exposes 3 tools: hyperxosist_search_plan, hyperxosist_filter_signals, hyperxosist_build_handoff. Their descriptions and schemas cost roughly 240 tokens of context every time the server is loaded.
Does the HyperXosist-Agent Remote MCP server require authentication?
No. We connected to HyperXosist-Agent Remote MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HyperXosist-Agent Remote MCP server still maintained?
HyperXosist-Agent Remote MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.