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

# MCPHereBot

> Self-described in its user-agent as "MCPHereBot/1.0", an MCP-focused bot. No operator page or public documentation could be found as of 2026-10-23.

## Dossier

- Kind: Agentic web & MCP registries
- Operator: unknown
- Documentation: none found
- robots.txt tokens: none documented
- Feeds: registry / directory
- Respects robots.txt: Not documented. No mcphere.* domain resolved on 2026-10-23.
- Verification: Unknown
- Labels matched in our logs: mcpherebot

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

Likely an MCP directory crawler; unattributed, treat as low-signal registry traffic.

## Observed behaviour

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

## Sources

- No public source found; the dossier describes only what the client declares and did.

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