---
schema_version: "newruntime-reader-dossiers-v1"
type: "reader_dossier"
slug: "talandorbot"
kind: "agentic_registry"
operator: "Talandor"
researched_at: "2026-10-23"
confidence: "low"
json_url: "https://newruntime.com/readers/talandorbot.json"
canonical_url: "https://newruntime.com/readers/talandorbot/"
---

# TalandorBot

> Likely the checker behind Talandor, an MCP server checker and monitoring tool that indexes Official MCP Registry entries, negotiates protocol versions and reads public tools/list results without calling tools. Talandor's pages do not document the TalandorBot user-agent.

## Dossier

- Kind: Agentic web & MCP registries
- Operator: Talandor (https://talandor.com/)
- Documentation: none found
- robots.txt tokens: none documented
- Feeds: monitoring
- Respects robots.txt: Not documented. Attribution inferred from the unique name match only; methodology page does not mention robots.txt. Opt-out via support@talandor.com.
- Verification: No published method
- Labels matched in our logs: talandorbot

## Why it matters to New Runtime (our interpretation)

Would track availability and tool-contract changes of our MCP server in a public report and change feed.

## Observed behaviour

- Baseline 2026-10-23 (93-day window): 96 requests on 7 days; first seen 2026-09-25, last seen 2026-10-23; Returning.
- Live numbers: https://newruntime.com/bot-traffic-history.json and https://newruntime.com/crawler-journeys.json

## Sources

- https://talandor.com/en
- https://talandor.com/en/methodology

Identity: A family name is what a client claims in its user agent. It is verified only when its request came from the operator's published IP ranges or passed forward-confirmed reverse DNS, as reported per family in /crawler-journeys.json. Anyone can claim any name.

All dossiers: https://newruntime.com/readers.md