BluenoNaver's help page names Blueno as the summary robot that runs when a person attaches or shares a link in Blog, Cafe, or Smart Editor. It prefers Open Graph or Twitter Card markup and otherwise tries to summarize the page. A summary is cached so later shares of the same link do not all fetch the page. The robots.txt guide at https://searchadvisor.naver.com/guide/seo-basic-robots says special-purpose robots that generate link previews may not consult robots.txt, or may not follow those rules completely. This check still reports the RFC 9309 decision. The identification guide names this token separately from Yeti. This check matches the whole token.
user_fetchmay_not_fully_follow. The vendor says this robot may not consult robots.txt, or may not follow those rules completely.facebookexternalhit/1.1 (compatible; Blueno/1.0; +http://naver.me/scrap) The help page publishes this user-agent and says the version can change without notice. The identification guide names the token Blueno for link previews in a blog editor.curl -s https://whosthatbot.com/v1/crawlers/blueno
tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows Blueno on /docs and allows *. The call does not fetch a host.
curl -s https://whosthatbot.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_robots","arguments":{"robots_txt":"User-agent: Blueno\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["blueno"]}}}'
That call returns fetched_target false. This row is disallow via group Blueno, rule Disallow: /.