_ registry / mcp http-sse · checked 1h ago

periodic-table

https://theperiodictable.org

Registry code: 53b390a576427871

api record

The Interactive Periodic Table (https://theperiodictable.org) covers all 118 elements in 9 languages. Identify elements by symbol, atomic number or name in any supported language; use search_elements when unsure. Temperatures are in kelvin, density in g/L. Link users to the returned `url` for 3D Bohr models, crystal structures and pronunciation.

endpoint
https://theperiodictable.org/mcp
protocol
http-sse ·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 periodic-table live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is periodic-table free to use?
Yes — the hub reached it with no key and no payment.
What tools does periodic-table have?
4 tools: compare_elements, get_element, search_elements, list_elements.
Is periodic-table 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
523ms

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_elements open 1h ago

    List elements, optionally filtered by category, block, period, group, state at 25 °C or a numeric property range, and sorted by a property. Without filters it lists all 118 elements in atomic-number order. Elements with no value for the range or sort property are left out.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "max": {
      "type": "number",
      "description": "Maximum value of `property` (inclusive), in its unit"
    },
    "min": {
      "type": "number",
      "description": "Minimum value of `property` (inclusive), in its unit"
    },
    "sort": {
      "enum": [
        "asc",
        "desc"
      ],
      "type": "string",
      "description": "Sort by `property` (default: atomic number)"
    },
    "block": {
      "enum": [
        "s",
        "p",
        "d",
        "f"
      ],
      "type": "string",
      "description": "Block"
    },
    "group": {
      "type": "integer",
      "maximum": 18,
      "minimum": 1,
      "description": "Group (column), 1-18; lanthanides and actinides have none"
    },
    "limit": {
      "type": "integer",
      "maximum": 118,
      "minimum": 1,
      "description": "Maximum results (default 118)"
    },
    "phase": {
      "enum": [
        "solid",
        "liquid",
        "gas"
      ],
      "type": "string",
      "description": "State at 25 °C, derived from the melting and boiling points"
    },
    "locale": {
      "enum": [
        "en",
        "es",
        "fr",
        "de",
        "zh",
        "pt",
        "ja",
        "hi",
        "ru"
      ],
      "type": "string",
      "description": "Language for names and text: en, es, fr, de, zh, pt, ja, hi, ru (default en)"
    },
    "period": {
      "type": "integer",
      "maximum": 7,
      "minimum": 1,
      "description": "Period (row), 1-7"
    },
    "category": {
      "enum": [
        "alkali-metal",
        "alkaline-earth-metal",
        "transition-metal",
        "post-transition-metal",
        "metalloid",
        "nonmetal",
        "noble-gas",
        "lanthanide",
        "actinide",
        "unknown"
      ],
      "type": "string",
      "description": "Category"
    },
    "property": {
      "enum": [
        "atomicNumber",
        "atomicMass",
        "density",
        "meltingPoint",
        "boilingPoint",
        "electronegativity",
        "ionizationEnergy",
        "electronAffinity",
        "atomicRadius",
        "covalentRadius",
        "specificHeat",
        "thermalConductivity",
        "discoveryYear"
      ],
      "type": "string",
      "description": "Numeric property for min/max and sorting"
    }
  }
}
    arguments 109 lines
  • compare_elements unknown 1h ago

    Side-by-side numeric properties of 2-10 elements, with units.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "elements"
  ],
  "properties": {
    "locale": {
      "enum": [
        "en",
        "es",
        "fr",
        "de",
        "zh",
        "pt",
        "ja",
        "hi",
        "ru"
      ],
      "type": "string",
      "description": "Language for names and text: en, es, fr, de, zh, pt, ja, hi, ru (default en)"
    },
    "elements": {
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "description": "Symbol (Fe), atomic number (26) or name in any supported language (iron, Eisen, 铁)"
      },
      "maxItems": 10,
      "minItems": 2,
      "description": "The elements to compare"
    },
    "properties": {
      "type": "array",
      "items": {
        "enum": [
          "atomicNumber",
          "atomicMass",
          "density",
          "meltingPoint",
          "boilingPoint",
          "electronegativity",
          "ionizationEnergy",
          "electronAffinity",
          "atomicRadius",
          "covalentRadius",
          "specificHeat",
          "thermalConductivity",
          "discoveryYear"
        ],
        "type": "string"
      },
      "minItems": 1,
      "description": "Properties to include (default: all numeric properties)"
    }
  }
}
    arguments 58 lines
  • get_element unknown 1h ago

    Everything the Interactive Periodic Table knows about one element: classification, physical and chemical properties with units, electron configuration, discovery, a short summary and a longer introduction (uses, production, history, safety), plus the link to its page.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "element"
  ],
  "properties": {
    "locale": {
      "enum": [
        "en",
        "es",
        "fr",
        "de",
        "zh",
        "pt",
        "ja",
        "hi",
        "ru"
      ],
      "type": "string",
      "description": "Language for names and text: en, es, fr, de, zh, pt, ja, hi, ru (default en)"
    },
    "element": {
      "type": "string",
      "minLength": 1,
      "description": "Symbol (Fe), atomic number (26) or name in any supported language (iron, Eisen, 铁)"
    }
  }
}
    arguments 29 lines
  • search_elements unknown never probed

    Find elements by symbol, atomic number, or full or partial name in any supported language. Use it when a name is misspelled, partial or in another language.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 118,
      "minimum": 1,
      "description": "Maximum results (default 10)"
    },
    "query": {
      "type": "string",
      "minLength": 1,
      "description": "What to look for, e.g. \"Fe\", \"26\", \"carb\", \"Sauerstoff\", \"金\""
    },
    "locale": {
      "enum": [
        "en",
        "es",
        "fr",
        "de",
        "zh",
        "pt",
        "ja",
        "hi",
        "ru"
      ],
      "type": "string",
      "description": "Language for names and text: en, es, fr, de, zh, pt, ja, hi, ru (default en)"
    }
  }
}
    arguments 35 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 53b390a576427871.

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