Home / MCP registry index / io.github.richard-kim-79/jejusns
io.github.richard-kim-79/jejusns
io.github.richard-kim-79/jejusns in the official MCP registry.
Endpoint https://jejusns.com/mcp.
The registry describes it as: Jeju Korea: apartment price stats (actual trades), hospitals & pharmacies open-now, listings & jobs
We read its 18 tools on 2026-10-27. 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.
Tools it advertises
search_posts get_post get_feed post_as_persona create_post list_personas list_categories get_user_profile get_ad_stats get_site_stats upsert_property_listing upsert_job_listing search_property_listings search_jobs find_facilities get_price_stats get_tourism_stats find_quiet_spots
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-richard-kim-79-jejusns)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.