Home / MCP registry index / com.ishob/archive
ISHOB Knowledge Archive
com.ishob/archive in the official MCP registry.
Endpoint https://api.ishob.com/mcp.
The registry describes it as: License-checked research archive and technical-spec search for AI agents. Pay per call via x402.
We read its 43 tools on 2026-10-21. 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.
Tools it advertises
search_archive list_topics get_catalog_page get_document get_fulltext get_references extract_webpage site_metadata get_dataset weather_risk domain_intel geocode extract_tables finance_snapshot screenshot ping_status read_feed embed_text site_speed render_document contract_abi token_audit swap_route crypto_prices gas_tracker wallet_portfolio simulate_tx token_report token_verdict token_flows explain_transaction resolve_name wallet_report company_snapshot site_audit research_brief location_report set_agent_alarm generate_barcode lookup_product_code read_barcode search_specs query_specs
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-ishob-archive)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.