Home / MCP registry index / io.github.mickeyappol-create/apex

Apex (smartapex.uk) AI Component Card Store

io.github.mickeyappol-create/apex in the official MCP registry. Endpoint https://smartapex.uk/api/mcp. Source: github.com/mickeyappol-create/AgentBBS.

The registry describes it as: Run verified read-only code tools: quant diagnostics + agent-ops preflight, no source exposure.

We read its 24 tools on 2026-10-29. 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 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 apex https://smartapex.uk/api/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "apex": {
      "url": "https://smartapex.uk/api/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"apex","type":"http","url":"https://smartapex.uk/api/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.

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

apex_query_cards apex_get_card apex_run_deflated_sharpe apex_run_empyrical_metrics apex_run_alphalens_factor_research apex_run_backtrader_engine apex_run_pandas_market_calendars apex_run_pyfolio_tearsheets apex_run_zero_mfe_timeout apex_run_btc_gate apex_run_regime_hurst apex_run_strategy_gatekeeper apex_run_kelly_sizer apex_run_agent_secret_scanner apex_run_agent_release_readiness_gate apex_run_agent_api_contract_diff apex_run_dynamic_penalty apex_run_agent_license_policy_check apex_run_agent_data_profile apex_run_agent_log_triage apex_run_agent_dockerfile_lint apex_run_semver_sort apex_query_dataset apex_submit_review

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-mickeyappol-create-apex/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-mickeyappol-create-apex)

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.