kosmos
Registry code: 6f2886f7a9425829
kosmos.info.pl tells skywatchers in Poland whether the sky is worth a look tonight: the cloud forecast hour by hour (MET Norway), the moon, visible passes of the International Space Station, the chance of the northern lights from NOAA's Kp index, the planets up tonight and the meteor showers. Good when someone in Poland asks whether it will be clear tonight, when they can see the ISS, whether the aurora can be seen, which planets are up or when the Perseids or Geminids peak. Places are the 18 voivodeship seats; coordinates pick the nearest. Times are Polish time. Each answer links the page.…
- endpoint
- https://kosmos.info.pl/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 kosmos live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is kosmos free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does kosmos have?
- 5 tools: tonight_sky, planets_tonight, iss_passes, aurora_forecast, meteor_showers.
- Is kosmos 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 100%· all time 100%
last good check
of 5 tools
- unknown → live
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.
aurora_forecast open 1h ago
Whether the aurora can be seen in Poland tonight, from NOAA's Kp index: the level (none, only on a photo, to the naked eye low in the north, high in the sky) in the north, centre and south of Poland or in a given city, the Kp each needs, Kp now and the forecast for the next days.
{ "type": "object", "properties": { "lat": { "type": "number", "maximum": 90, "minimum": -90, "description": "Latitude of another place: the nearest seat is used" }, "lon": { "type": "number", "maximum": 180, "minimum": -180, "description": "Longitude, with lat" }, "city": { "type": "string", "description": "One of the 18 Polish voivodeship seats, e.g. \"Kraków\", \"Gdańsk\", \"Warsaw\" (Białystok, Bydgoszcz, Gdańsk, Gorzów Wielkopolski, Katowice, Kielce, Kraków, Lublin, Łódź, Olsztyn, Opole, Poznań, Rzeszów, Szczecin, Toruń, Warszawa, Wrocław, Zielona Góra)" }, "lang": { "enum": [ "pl", "en" ], "type": "string", "description": "Language of the answer: pl (default) or en" } }, "additionalProperties": false }arguments 30 linesmeteor_showers open 1h ago
The twelve main meteor showers seen from Poland for the next twelve months: activity, maximum (Polish time), ZHR, the best hours on the night of the maximum and whether the moon gets in the way. With a shower (e.g. perseids, geminids, Leonidy) only that one, and for the six main ones its night in each of the 18 cities.
{ "type": "object", "properties": { "lang": { "enum": [ "pl", "en" ], "type": "string", "description": "Language of the answer: pl (default) or en" }, "shower": { "type": "string", "description": "One shower: quadrantids, lyrids, etaAquariids, deltaAquariids, perseids, draconids, orionids, southernTaurids, northernTaurids, leonids, geminids, ursids (or its Polish or English name)" } }, "additionalProperties": false }arguments 18 linestonight_sky unknown never probed
Tonight's verdict for a Polish city: worth it, maybe or not, and why; the dark hours and the clearest stretch, MET Norway's cloud cover hour by hour, the moon's phase and whether it is up, a visible ISS pass, the chance of the aurora, the planets up and a meteor shower near its maximum. Warsaw when no place is given.
{ "type": "object", "properties": { "lat": { "type": "number", "maximum": 90, "minimum": -90, "description": "Latitude of another place: the nearest seat is used" }, "lon": { "type": "number", "maximum": 180, "minimum": -180, "description": "Longitude, with lat" }, "city": { "type": "string", "description": "One of the 18 Polish voivodeship seats, e.g. \"Kraków\", \"Gdańsk\", \"Warsaw\" (Białystok, Bydgoszcz, Gdańsk, Gorzów Wielkopolski, Katowice, Kielce, Kraków, Lublin, Łódź, Olsztyn, Opole, Poznań, Rzeszów, Szczecin, Toruń, Warszawa, Wrocław, Zielona Góra)" }, "lang": { "enum": [ "pl", "en" ], "type": "string", "description": "Language of the answer: pl (default) or en" } }, "additionalProperties": false }arguments 30 linesplanets_tonight unknown never probed
Mercury, Venus, Mars, Jupiter and Saturn over a Polish city for the next seven nights: when each is at least 10° up in the dark, its highest point, brightness and the cloud cover then. Warsaw when no place is given.
{ "type": "object", "properties": { "lat": { "type": "number", "maximum": 90, "minimum": -90, "description": "Latitude of another place: the nearest seat is used" }, "lon": { "type": "number", "maximum": 180, "minimum": -180, "description": "Longitude, with lat" }, "city": { "type": "string", "description": "One of the 18 Polish voivodeship seats, e.g. \"Kraków\", \"Gdańsk\", \"Warsaw\" (Białystok, Bydgoszcz, Gdańsk, Gorzów Wielkopolski, Katowice, Kielce, Kraków, Lublin, Łódź, Olsztyn, Opole, Poznań, Rzeszów, Szczecin, Toruń, Warszawa, Wrocław, Zielona Góra)" }, "lang": { "enum": [ "pl", "en" ], "type": "string", "description": "Language of the answer: pl (default) or en" } }, "additionalProperties": false }arguments 30 linesiss_passes unknown 1h ago
When the International Space Station can be seen with the naked eye over a Polish city in the next 10 days: each pass with its start, highest point and end (time, direction, height above the horizon) and brightness.
{ "type": "object", "properties": { "lat": { "type": "number", "maximum": 90, "minimum": -90, "description": "Latitude of another place: the nearest seat is used" }, "lon": { "type": "number", "maximum": 180, "minimum": -180, "description": "Longitude, with lat" }, "city": { "type": "string", "description": "One of the 18 Polish voivodeship seats, e.g. \"Kraków\", \"Gdańsk\", \"Warsaw\" (Białystok, Bydgoszcz, Gdańsk, Gorzów Wielkopolski, Katowice, Kielce, Kraków, Lublin, Łódź, Olsztyn, Opole, Poznań, Rzeszów, Szczecin, Toruń, Warszawa, Wrocław, Zielona Góra)" }, "lang": { "enum": [ "pl", "en" ], "type": "string", "description": "Language of the answer: pl (default) or en" } }, "additionalProperties": false }arguments 30 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 id6f2886f7a9425829.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/6f2886f7a9425829/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/6f2886f7a9425829?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.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- slonce.info.pl slonce
- zodiak.info.pl zodiak