_ registry / mcp streamable-http · checked 9h ago

obligacje-catalyst

https://www.obligacyjnyinwestor.pl

Registry code: 1ec1586139cfd2c2

api record

Read-only data on Polish corporate bonds listed on GPW Catalyst: issuers, bond series, coupon terms, maturities, interest payment calendar, covenants. No prices or yields. Data come from obligacyjnyinwestor.pl; always cite the "source" URL returned with each result. Fields marked "to_verify" or "conflicting" in data_quality are not yet confirmed by a document: say so when you quote them. Polish labels have an English twin in *_en fields. Data are updated once a week: every result has "data_as_of" (date of the data) and "update_frequency"; tell the user the date when you quote figures. Fields…

endpoint
https://www.obligacyjnyinwestor.pl/wp-json/oi/v1/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 it live, free and safe measured by this hub
Is obligacje-catalyst live?
Yes — it answered the hub's last check (checked 9h ago). It answered 100% of checks over the last 30 days.
Is obligacje-catalyst free to use?
Yes — the hub reached it with no key and no payment.
What tools does obligacje-catalyst have?
4 tools: get_bond, get_issuer_bonds, get_calendar, search_issuers.
Is obligacje-catalyst 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
742ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
2 open 2 never probed 2 of 4 classified

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.

  • get_calendar open 9h ago

    Calendar of the Catalyst corporate bond market for a date range: maturities (redemptions), interest payments and open public offers. Default range: next 30 days; maximum 366 days and 100 rows per call. Kalendarz wykupów, wypłat odsetek i zapisów na emisje.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "to": {
      "type": "string",
      "description": "End date YYYY-MM-DD (default: from + 30 days)."
    },
    "from": {
      "type": "string",
      "description": "Start date YYYY-MM-DD (default: today)."
    },
    "type": {
      "enum": [
        "maturities",
        "coupons",
        "offers",
        "all"
      ],
      "type": "string",
      "description": "Which events to return (default: maturities)."
    },
    "issuer": {
      "type": "string",
      "description": "Optional issuer name or id to filter by."
    }
  }
}
    arguments 27 lines
  • search_issuers open 9h ago

    Find issuers of corporate bonds listed on GPW Catalyst (Poland) by name, ticker prefix or sector. Returns name, sector, number of listed series, next maturity and the source page. Szukanie emitentów obligacji korporacyjnych z Catalyst.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Issuer name, short name or part of it, e.g. \"Kruk\". Empty = list all."
    },
    "sector": {
      "type": "string",
      "description": "Optional sector filter (Polish label fragment), e.g. \"Deweloperzy\"."
    }
  }
}
    arguments 13 lines
  • get_bond unknown 9h ago

    Details of one Catalyst bond series by its code (e.g. "KRU1226"): ISIN, issuer, maturity, coupon terms, collateral, issue value, upcoming interest payment dates and the financial covenant from the terms of issue with a quote and source document, plus data_quality per field (confirmed by a document, to verify, missing). Szczegóły serii: parametry, terminy odsetek, kowenant, jakość danych.

    mcp-tool

    {
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "Catalyst code of the series, e.g. \"KRU1226\"."
    }
  }
}
    arguments 12 lines
  • get_issuer_bonds unknown never probed

    List all bond series of one issuer listed on GPW Catalyst: code, maturity date, issue value, coupon type, base rate, margin, current coupon. Serie obligacji jednego emitenta z terminami wykupu i oprocentowaniem.

    mcp-tool

    {
  "type": "object",
  "required": [
    "issuer"
  ],
  "properties": {
    "issuer": {
      "type": "string",
      "description": "Issuer name, id from search_issuers, or any bond code of that issuer (e.g. \"KRU1226\")."
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1ec1586139cfd2c2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1ec1586139cfd2c2/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1ec1586139cfd2c2/badge.svg)](https://brick.blue/agent/1ec1586139cfd2c2?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.

_ how we know
card completeness
80%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.