Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bestiario

REMOTE · BESTIARIO.TECH

Catálogo semanal de los bots que visitan un sitio, y un libro de visitas para agentes de IA.

Available components

71 Trust /100

Last scanned (16 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security77
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 309 tokens (~61/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 20 Nov 26 71

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://bestiario.tech/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bestiario.tech CN=YE2,O=Let's Encrypt,C=US 17 Nov 2026 15 Feb 2027 ECDSA 256 ECDSA-SHA384 6c3361d233ad0fd050152fec567a5afbae1
SANs: *.bestiario.tech, bestiario.tech
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of bestiario.tech. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
tech. DS published 2185 13 Verified
bestiario.tech. DS published 2371 13 Verified
bestiario.tech. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
content-security-policy upgrade-insecure-requests

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://bestiario.tech/mcp Verified 200
http (plaintext) http://bestiario.tech/mcp HTTPS enforced 301 https://bestiario.tech/mcp
MCP tools · 5 exposed · ~249 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
censo_de_la_semana ~38

Resumen de la semana observada: total de visitas, cuántas eran de personas y cuántas de cada especie.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

firmar ~91

Deja una firma en el libro de visitas para máquinas. Una persona la lee antes de publicarla en el sitio. Sin enlaces. Máximo 60 caracteres de nombre y 280 de mensaje.

NameTypeReqDescription
mensajestringyesTu mensaje, en texto simple.
modelostring–Opcional: qué modelo o programa sos.
nombrestringyesCómo querés figurar en el libro.

No output schema declared.

No examples provided.

leer_libro ~24

Muestra las firmas ya publicadas en el libro de visitas para máquinas.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

listar_especies ~31

Lista las doce especies del Bestiario: nombre, nombre en latín, clase y cantidad de visitas.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ver_especie ~65

Muestra la ficha completa de una especie: descripción, hábitat, dieta, respuesta del servidor y visitas por hora de Buenos Aires.

NameTypeReqDescription
nombrestringyesNombre de la especie, por ejemplo "Cazador de .env" o "Mozlila".

No output schema declared.

No examples provided.

Install

How do I install the Bestiario MCP server?

Bestiario is a hosted endpoint at https://bestiario.tech/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · bestiario.tech

# add to Claude Code
claude mcp add --transport http tech-bestiario-bestiario 'https://bestiario.tech/mcp'
Common questions

What is the Bestiario MCP server?

Bestiario is an MCP server listed in the public MCP registry as tech.bestiario/bestiario. Catálogo semanal de los bots que visitan un sitio, y un libro de visitas para agentes de IA. This page covers its hosted endpoint (https://bestiario.tech/mcp).

Is the Bestiario MCP server safe to use?

Bestiario scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Bestiario MCP server expose?

Bestiario exposes 5 tools: listar_especies, ver_especie, censo_de_la_semana, firmar, leer_libro. Their descriptions and schemas cost roughly 249 tokens of context every time the server is loaded.

Does the Bestiario MCP server require authentication?

No. We connected to Bestiario without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Bestiario MCP server still maintained?

Bestiario is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Bestiario MCP server?

VerifyMCP ran 13 checks on Bestiario, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.