Home / MCP registry index / com.okfindex/okfindex
com.okfindex/okfindex
com.okfindex/okfindex in the official MCP registry.
Endpoint https://okfindex.com/mcp. Source: github.com/wrpbr/okfindex.
The registry describes it as: Search Open Knowledge Format (OKF) bundles, read a bundle card and submit your own with IndexNow.
We read its 97 tools on 2026-10-28. 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
api_index search_bundles get_bundle index_stats legislation_status search_legislation get_legislation get_legislation_part list_bases create_base publish_base unpublish_base get_base get_base_usage list_base_documents get_base_connection connect_base_source disconnect_base_source search_base add_base_document replace_base_document remove_base_document get_base_document read_base_markdown read_base_original read_base_image read_base_index read_base_concept read_base_source read_base_pdf_source read_base_docx_source read_base_doc_source export_base save_base_dataset public_list_bases public_get_base public_list_base_documents public_search_base public_get_base_document public_read_base_markdown public_read_base_original public_read_base_image public_read_base_index public_read_base_concept public_read_base_source public_read_base_pdf_source public_read_base_docx_source public_read_base_doc_source public_export_base favorite_ids favorite_bundles save_favorite remove_favorite list_collections create_collection get_collection search_collection save_collection_base remove_collection_base publish_collection and 37 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-okfindex-okfindex)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.