Home / MCP registry index / io.github.SharpLu/ko-mcp

io.github.SharpLu/ko-mcp

io.github.SharpLu/ko-mcp in the official MCP registry. Endpoint https://mcp.ko.io/mcp. Source: github.com/SharpLu/ko-mcp.

The registry describes it as: Real SEC, 13F, insider, congress & macro data your AI agent can cite. Hosted MCP, 24 tools.

We read its 32 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules.

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 every week.

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 ko-mcp https://mcp.ko.io/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "ko-mcp": {
      "url": "https://mcp.ko.io/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"ko-mcp","type":"http","url":"https://mcp.ko.io/mcp"}'

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. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

get_institution_holdings list_institutions get_stock_profile get_stock_holders get_stock_activity get_stock_price get_insider_trades list_insider_traders get_congress_trades get_congress_member search get_form144_notices sec_list_filings sec_get_filing_index sec_get_filing_document get_stock_financials get_treasury_yields get_fed_rates get_economic_indicators get_ftd_data get_financial_stress get_crypto_exposure get_crypto_holders get_crypto_holder get_eu_markets get_eu_insider_dealings get_eu_major_holdings get_eu_short_positions get_eu_annual_reports get_eu_issuer get_gov_contracts search_gov_contracts

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-sharplu-ko-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-sharplu-ko-mcp)

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. What we found across the registry.

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