Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.oswarld/technical

REMOTE · WWW.BULLBEAR.NINJA · SCANNED SEP 21

Technical analysis (RSI, MA, signal score) for 9,400+ global stocks, by ticker or name.

0 this week 86 Trust /100
Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 513 tokens (~102/item across 5 items; 5 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 Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 41% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.oswarld/technical MCP server?

io.github.oswarld/technical is a hosted endpoint at https://www.bullbear.ninja/api/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 · www.bullbear.ninja

# add to Claude Code
claude mcp add --transport http oswarld-technical 'https://www.bullbear.ninja/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "oswarld-technical": {
      "url": "https://www.bullbear.ninja/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "oswarld-technical": {
      "type": "http",
      "url": "https://www.bullbear.ninja/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.oswarld-technical]
url = "https://www.bullbear.ninja/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "oswarld-technical": {
      "type": "remote",
      "url": "https://www.bullbear.ninja/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add oswarld-technical --url 'https://www.bullbear.ninja/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  oswarld-technical:
    url: "https://www.bullbear.ninja/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "oswarld-technical": {
      "Transport": "http",
      "Url": "https://www.bullbear.ninja/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add oswarld-technical -t streamable-http -u 'https://www.bullbear.ninja/api/mcp'
// mcp.json
{
  "mcpServers": {
    "oswarld-technical": {
      "type": "http",
      "url": "https://www.bullbear.ninja/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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 +1
    • 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 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Aug 26 0
    • The server changed its declared name: ooooo-technical → argos-technical security
  • 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
  • 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
Diagnostics

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 21 Sept 2026 · Probed https://www.bullbear.ninja/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.bullbear.ninja CN=YR1,O=Let's Encrypt,C=US 20 Sept 2026 19 Dec 2026 RSA 2048 SHA256-RSA 6ed6a6eaa23f8e2140f56435ae64d2a1b6b
SANs: www.bullbear.ninja
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.bullbear.ninja. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ninja. present 46082 8 Verified
bullbear.ninja. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.bullbear.ninja/api/mcp Verified 200
http (plaintext) http://www.bullbear.ninja/api/mcp HTTPS enforced 308 https://www.bullbear.ninja/api/mcp
MCP tools · 5 exposed · ~462 tokens

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 →

Tool Tokens
fetch ~58

Fetch the full technical record for one stock by id, ticker, or company name. Returns a readable summary and structured metadata.

NameTypeReqDescription
idstringyesTicker or company name, e.g. '005930' or 'SK Hynix'.

No output schema declared.

No examples provided.

get_technical_analysis ~114

Technical levels for one or more covered stocks (KR/US/HK/CN/JP/TW/EU) from the precomputed cache: price, MA5/20/60/120, RSI14, Bollinger position, support/resistance, 52-week range, momentum, volatility, trend, and a 0-100 signal score. Accepts tickers or Korean/English company names.

NameTypeReqDescription
tickersarrayyesTickers or company names (KR/EN), up to 25.

No output schema declared.

No examples provided.

list_covered_stocks ~73

Browse the covered universe, optionally filtered by market, sector, or ticker/name. Results include the latest signal score and trend when available.

NameTypeReqDescription
limitintegerDefault 50, max 200.
marketstring
querystring
sectorstring

No output schema declared.

No examples provided.

screen_technicals ~145

Screen the covered universe by trend, signal score, RSI, market, and sector. Sort by 'below_high' or 'rsi_asc' for pullbacks/oversold stocks, or 'signal_desc'/'momentum_desc' for leaders.

NameTypeReqDescription
limitintegerDefault 50, max 200.
marketstring
max_signal_scorenumber
min_signal_scorenumber
rsi_abovenumber
rsi_belownumber
sectorstring
sortstringDefault 'signal_desc'.
trendstring

No output schema declared.

No examples provided.

search ~72

Search the covered stock universe by company name or ticker (KR/EN). Returns ids, titles, URLs, and short technical snippets. Pair with fetch for a full record.

NameTypeReqDescription
limitintegerDefault 20, max 50.
querystringyesCompany name or ticker substring (KR/EN).

No output schema declared.

No examples provided.

Common questions

What is the io.github.oswarld/technical MCP server?

io.github.oswarld/technical is an MCP server listed in the public MCP registry as io.github.oswarld/technical. Technical analysis (RSI, MA, signal score) for 9,400+ global stocks, by ticker or name. This page covers its hosted endpoint (https://www.bullbear.ninja/api/mcp).

Is the io.github.oswarld/technical MCP server safe to use?

io.github.oswarld/technical scores 86 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 io.github.oswarld/technical MCP server expose?

io.github.oswarld/technical exposes 5 tools: get_technical_analysis, screen_technicals, list_covered_stocks, search, fetch. Their descriptions and schemas cost roughly 462 tokens of context every time the server is loaded.

Does the io.github.oswarld/technical MCP server require authentication?

No. We connected to io.github.oswarld/technical without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.oswarld/technical MCP server still maintained?

io.github.oswarld/technical is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.