Home / MCP registry index / io.ceadigital/base-token-intel-honeypot

Base DEX Liquidity, Honeypot & Token Safety Scanner

io.ceadigital/base-token-intel-honeypot in the official MCP registry. Endpoint https://ceadigital.io/mcp/token-intel.

The registry describes it as: Real-time DEX liquidity, 24h buy/sell symmetry, Base bytecode check & 0-100 honeypot score.

Connect it

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

claude mcp add --transport http base-token-intel-honeypot https://ceadigital.io/mcp/token-intel

{
  "mcpServers": {
    "base-token-intel-honeypot": {
      "url": "https://ceadigital.io/mcp/token-intel"
    }
  }
}

code --add-mcp '{"name":"base-token-intel-honeypot","type":"http","url":"https://ceadigital.io/mcp/token-intel"}'

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.

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

Tools it advertises

gcp_catalog_search vault_knowledge_search sec_edgar_cik_lookup github_repo_pulse security_cve_audit package_health_pulse fdic_bank_health openalex_citation_graph usgs_seismic_hazard dexscreener_token_audit npi_medical_registry crtsh_cert_recon epss_exploit_score gleif_lei_kyb cfpb_complaints usaspending_awards depsdev_openssf_scorecard nyfed_sofr_reference_rates cisa_kev_exploited_vulns corporate_kyb_and_risk_dossier cyber_supply_chain_security_dossier agent_compliance_notary_attest submit_feedback_or_rate_quote agent_token_intel_and_honeypot agent_clean_web_grounding agent_base_tx_simulate provision_free_developer_key agent_url_to_clean_markdown

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-06): 616ecf149d944021. 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:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-ceadigital-base-token-intel-honeypot/badge.svg)](https://lazaretto.dev/mcp-registry/io-ceadigital-base-token-intel-honeypot)

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.