Home / MCP registry index / ca.ohey/research

Ohey research

ca.ohey/research in the official MCP registry. Endpoint https://ohey.ca/mcp/research. Source: github.com/Oheyresearch/ohey-mcp.

The registry describes it as: Web malware techniques, kits and EtherHiding contracts from Ohey's website scans. No sign-in.

We read its 8 tools on 2026-11-04. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http research https://ohey.ca/mcp/research

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "research": {
      "url": "https://ohey.ca/mcp/research"
    }
  }
}

VS Code

code --add-mcp '{"name":"research","type":"http","url":"https://ohey.ca/mcp/research"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

list_threats get_threat list_research_articles get_article search_etherhiding_contracts get_etherhiding_contract get_feed_stats search_clickfix_commands

Tool changes

This server changed its tools after we first read them. If you approved it before the latest change, what you approved is not what it serves now: read its tools again.

Between 2026-11-04 and 2026-11-04 it changed what these tools say: get_etherhiding_contract, get_threat; changed its server instructions.

Fingerprint of its tools at our last full read (2026-11-04): abb8f10783ceee2b. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/ca-ohey-research/badge.svg)](https://lazaretto.dev/mcp-registry/ca-ohey-research)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.