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

pensionhunter

https://mcp.pensionhunter.ai

Registry code: 43b4d5a3155e07c6

api record

PensionHunter identifies pensions people may have left in countries they worked in. The four tools are read-only and anonymous; nothing sent is stored. Countries may be given as names, native names, aliases or ISO codes. Every fact carries its source and the date we read it. Each result ends with an order link built for the countries in that call. Identification and research only; we do not give advice.

endpoint
https://mcp.pensionhunter.ai
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 pensionhunter live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is pensionhunter free to use?
Yes — the hub reached it with no key and no payment.
What tools does pensionhunter have?
4 tools: country_pension_facts, resolve_employer, check_work_history, list_covered_countries.
Is pensionhunter 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
574ms

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
1 open 3 never probed 1 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.

  • list_covered_countries open 2h ago

    The countries PensionHunter covers, each with its ISO code and one sourced line on what exists there. Takes no input.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • country_pension_facts unknown 2h ago

    One country's stored facts: what the money is worth, why the free route fails from abroad, and dated obligations, each with source and read date. Accepts names, native names, aliases and ISO codes. A country outside our coverage returns covered: false with a note.

    mcp-tool

    {
      "type": "object",
      "required": [
        "country"
      ],
      "properties": {
        "country": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "One country, as an English name, a native name, a common alias or an ISO 3166 alpha-2 or alpha-3 code, in any case. Examples: Netherlands, Nederland, Holland, NL, NLD; United Kingdom, UK, GB, Britain; Germany, Deutschland, DE."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • resolve_employer unknown never probed

    The country an employer name implies, from evidence in the name itself, matched anywhere in it: a country or native country name, a city, a nationality word, or a national legal form such as B.V., GmbH, ASA, Oyj, S.L. or Pte. Ltd. A form used in several countries (GmbH, Ltd, S.A.) returns the candidates instead of a guess.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "The employer name as the person knows it, ideally with its legal form and city, for example \"Shell Nederland B.V.\" or \"Deutsche Bank Frankfurt\"."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • check_work_history unknown 2h ago

    For each country in a work history: whether a pension is likely to exist and why, why self service fails from abroad, and a dated obligation only where it applies to the subject. Countries accept names, native names, aliases and ISO codes. Nothing sent is stored.

    mcp-tool

    {
      "type": "object",
      "required": [
        "entries"
      ],
      "properties": {
        "entries": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "country",
              "from"
            ],
            "properties": {
              "to": {
                "type": [
                  "integer",
                  "null"
                ],
                "maximum": 2100,
                "minimum": 1900,
                "description": "Last year of work there, four digits; null or omitted if still working there."
              },
              "from": {
                "type": "integer",
                "maximum": 2100,
                "minimum": 1900,
                "description": "First year of work there, four digits."
              },
              "country": {
                "type": "string",
                "maxLength": 80,
                "minLength": 2,
                "description": "One country, as an English name, a native name, a common alias or an ISO 3166 alpha-2 or alpha-3 code, in any case. Examples: Netherlands, Nederland, Holland, NL, NLD; United Kingdom, UK, GB, Britain; Germany, Deutschland, DE."
              },
              "employer": {
                "type": [
                  "string",
                  "null"
                ],
                "maxLength": 120,
                "description": "Employer name, optional."
              }
            },
            "additionalProperties": false
          },
          "maxItems": 60,
          "minItems": 1,
          "description": "One entry per period of work in a country."
        },
        "subject": {
          "type": "object",
          "properties": {
            "deceased": {
              "type": "boolean",
              "description": "True when the person has died and a relative is asking."
            },
            "birthYear": {
              "type": "integer",
              "maximum": 2100,
              "minimum": 1900,
              "description": "Year of birth, four digits."
            },
            "childrenMentioned": {
              "type": "boolean",
              "description": "True when children are part of the question."
            },
            "pensionInPaymentCountries": {
              "type": "array",
              "items": {
                "type": "string",
                "description": "One country, as an English name, a native name, a common alias or an ISO 3166 alpha-2 or alpha-3 code, in any case. Examples: Netherlands, Nederland, Holland, NL, NLD; United Kingdom, UK, GB, Britain; Germany, Deutschland, DE."
              },
              "description": "Countries already paying the person a pension."
            }
          },
          "description": "Optional facts about the person, used only to decide which dated obligations apply.",
          "additionalProperties": false
        }
      },
      "additionalProperties": false
    }
    arguments 83 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 43b4d5a3155e07c6.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/43b4d5a3155e07c6/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/43b4d5a3155e07c6/badge.svg)](https://brick.blue/agent/43b4d5a3155e07c6?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.