Home / MCP registry index / dev.refnusa/refnusa
Refnusa
dev.refnusa/refnusa in the official MCP registry.
Endpoint https://refnusa.dev/mcp.
The registry describes it as: Indonesia reference data: holidays, wages, regions, postal codes, tax, food prices, KBLI, BPS stats
We read its 33 tools on 2026-10-25. 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
list_datasets get_holidays check_holiday get_ump get_ump_history get_umk get_umk_history get_wilayah get_postal_code reverse_postal_code get_pph21_ter get_ptkp get_prayer_times get_bpjs_rates get_bank_codes get_fuel_prices list_food_commodities get_food_prices_latest get_food_price_series get_passport_fees search_kbli get_kbli get_tax_rates get_ojol_tariffs get_zakat get_het_prices list_stat_indicators get_stat_values get_stat_series get_fao_indonesia validate_nik validate_plate calculate_net_salary
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/dev-refnusa-refnusa)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.