Multicines Ortega (MCP)
Registry code: 3cc5553be48614bc
Cartelera, horarios y venta de entradas de Multicines Ortega, en Puertollano.
from a public catalogue that lists it, not from the operator
- endpoint
- https://multicinesortega.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is Multicines Ortega (MCP) live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
- Is Multicines Ortega (MCP) free to use?
- Not measured yet.
- What tools does Multicines Ortega (MCP) have?
- 3 tools: cines, cartelera, buscar_pelicula.
- Is Multicines Ortega (MCP) safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 98.8%· all time 98.8%
last good check
of 3 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- get cinema showtimes
- search a film by title
- list cinemas and opening hours
- takes → gives
- text → data
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
cines reads unknown never probed
Los cines de este operador: nombre, identificador para filtrar, dirección, zona horaria y horario de apertura cuando consta.
{ "type": "object", "required": [], "properties": {}, "additionalProperties": false }arguments 6 linescartelera reads unknown never probed
Qué películas se proyectan y a qué horas, con la URL exacta donde se compra cada pase. Se puede acotar a un día concreto y, en una cadena, a un cine. Sin «dia» devuelve todos los días programados. Las horas son hora local del cine (nunca UTC) y los días son el día operativo del cine, que empieza y acaba en su hora de cierre: un pase de madrugada pertenece a la noche anterior. Cada pase lleva «disponibilidad»: available (hay sitio), few (quedan pocas) o soldout (agotado); null significa que no consta. Es una banda aproximada, refrescada cada pocos minutos, y no dice cuántas entradas quedan: para confirmarlo y comprar hay que abrir la URL de compra.
{ "type": "object", "required": [], "properties": { "dia": { "type": "string", "description": "Día operativo en formato AAAA-MM-DD. Hoy es 2026-10-20. Días con pases: 2026-10-20, 2026-10-21, 2026-10-29." }, "cine": { "type": "string", "description": "Identificador del cine (ver la herramienta «cines»). Se omite para verlos todos." } }, "additionalProperties": false }arguments 15 linesbuscar_pelicula reads unknown never probed
Busca una película por su título (acepta el título original y coincidencias parciales) y devuelve su ficha completa —sinopsis, duración, dirección, reparto, calificación— junto con todos sus pases y la URL donde se compra cada uno. Las horas son hora local del cine (nunca UTC) y los días son el día operativo del cine, que empieza y acaba en su hora de cierre: un pase de madrugada pertenece a la noche anterior.
{ "type": "object", "required": [ "titulo" ], "properties": { "titulo": { "type": "string", "description": "Título o parte del título." } }, "additionalProperties": false }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id3cc5553be48614bc.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/3cc5553be48614bc/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/3cc5553be48614bc?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.