Ohey research
REMOTE · OHEY.CA
Web malware techniques, kits and EtherHiding contracts from Ohey's website scans. No sign-in.
Available components
Last scanned (17 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Security
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 Security83
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 588 tokens (~98/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 73
First indexed and scored.
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 4 Nov 2026 · Probed https://ohey.ca/mcp/research
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ohey.ca | CN=WE1,O=Google Trust Services,C=US | 7 Oct 2026 | 5 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 9c9eda6fd6bc52c00e7fe408f6ac2164 |
| SANs: ohey.ca, api.ohey.ca, *.api.ohey.ca | ||||||
| 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 ohey.ca. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ca. | present | 26384 | 13 | Verified |
| ohey.ca. | present | 2371 | 13 | Verified |
| ohey.ca. | 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 |
|---|---|
| strict-transport-security | max-age=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ohey.ca/mcp/research | Verified | 200 | |
| http (plaintext) | http://ohey.ca/mcp/research | HTTPS enforced | 301 | https://ohey.ca/mcp/research |
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 →
get_etherhiding_contract Get an EtherHiding contract ~47
One contract's destinations over time, the contracts or endpoints it names next, and when Ohey first and last read it.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The contract address. |
No output schema declared.
No examples provided.
get_feed_stats Get feed statistics ~140
The size of the Ohey feed and the last seven full UTC days of changes to it, ending the day before asOf. hosts: hosts in the feed now. denied: hosts confirmed as legitimate services and kept out. week.added (and daily): hosts that entered the feed. week.entered: website tips that reached review. week.accepted: of those, the ones accepted into the feed. week.removed: tips an analyst rejected at review. week.denied: hosts confirmed legitimate that week. archive: the scanner's captures, the responses in them, host IP observations, response bodies judged malicious or clean, and feed status changes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_threat Get a technique or kit ~91
A technique or kit page's statistics: sites matched by month, how many sites were still infected when rescanned, WordPress and Joomla shares, common plugins and core versions, kits seen together on the same sites, its EtherHiding contracts and the articles about it.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | A slug from list_threats, such as clickfix, etherhiding or socgholish. |
No output schema declared.
No examples provided.
list_research_articles List research articles ~43
Ohey research articles, newest first: incident write-ups with timelines, code analysis and indicators.
| Name | Type | Req | Description |
|---|---|---|---|
| threat | string | – | Only articles about this technique or kit. |
No output schema declared.
No examples provided.
list_threats List techniques ~29
Every technique Ohey publishes, with its page, a summary, site counts and its kits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_etherhiding_contracts Search EtherHiding contracts ~123
Smart contracts that compromised websites read their next stage from, as the EtherHiding contract tracker lists them: chain, kit, current destinations and when Ohey last read each one. Set destination to find the contracts that point, or pointed, at a host.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | A chain name, such as Polygon or BNB Smart Chain. |
| destination | string | – | A host or URL, fanged or defanged. |
| kit | string | – | A kit slug, such as clearshort. |
| limit | integer | – | – |
No output schema declared.
No examples provided.
How do I install the Ohey research MCP server?
Ohey research is a hosted endpoint at https://ohey.ca/mcp/research, 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 · ohey.ca
claude mcp add --transport http ca-ohey-research 'https://ohey.ca/mcp/research'
What is the Ohey research MCP server?
Ohey research is an MCP server listed in the public MCP registry as ca.ohey/research. Web malware techniques, kits and EtherHiding contracts from Ohey's website scans. No sign-in. This page covers its hosted endpoint (https://ohey.ca/mcp/research).
Is the Ohey research MCP server safe to use?
Ohey research scores 73 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 Ohey research MCP server expose?
Ohey research exposes 6 tools: list_threats, get_threat, list_research_articles, search_etherhiding_contracts, get_etherhiding_contract, get_feed_stats. Their descriptions and schemas cost roughly 473 tokens of context every time the server is loaded.
Does the Ohey research MCP server require authentication?
No. We connected to Ohey research without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Ohey research MCP server still maintained?
Ohey research is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.