_ registry / mcp streamable-http · checked 4m ago

Star Wars API & MCP server (swapi.build)

listed under this name in a public catalogue; the server gives only its address, swapi.build

https://swapi.build

Registry code: 9b3c808337b28f36

api record

swapi.build serves Star Wars data from the six films of Episodes I-VI only:

people, films, planets, species, starships and vehicles. Read-only, no API key.

endpoint
https://swapi.build/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 Star Wars API & MCP server (swapi.build) live?
Yes — it answered the hub's last check (checked 4m ago). It answered 100% of checks over the last 30 days.
Is Star Wars API & MCP server (swapi.build) free to use?
Yes — the hub reached it with no key and no payment.
What tools does Star Wars API & MCP server (swapi.build) have?
4 tools: sw_random, sw_get, sw_search, sw_list.
Is Star Wars API & MCP server (swapi.build) 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 98.4%· all time 98.4%

latency
580ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 254 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • look up star wars characters
  • search star wars films and planets
  • get a random star wars entity
takes → gives
text → data
tools
4 reads
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 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.

  • sw_random reads unknown 10h ago

    Returns one random Star Wars entity of the given resource type as a JSON object. Each call can return a different entity, so it is not idempotent. Useful for demos and quizzes; to fetch a specific entity use sw_search or sw_get.

    mcp-tool

    {
      "type": "object",
      "required": [
        "resource"
      ],
      "properties": {
        "resource": {
          "enum": [
            "PEOPLE",
            "FILMS",
            "PLANETS",
            "SPECIES",
            "STARSHIPS",
            "VEHICLES"
          ],
          "type": "string",
          "description": "Resource type: PEOPLE, FILMS, PLANETS, SPECIES, STARSHIPS or VEHICLES. Any other value returns a tool error."
        }
      }
    }
    arguments 20 lines
  • sw_get reads unknown 10h ago

    Gets one Star Wars entity by numeric record id and returns it as a JSON object. Take the id from the end of an entity's url field (from sw_search, sw_list or a relation URL). Ids are record ids, not episode numbers: FILMS id 1 is A New Hope (Episode IV). An unknown id returns a tool error, e.g. 'No films found with id 99'. Pass expand to get related records in the same call, e.g. ["homeworld", "species"]; name only the relations you need; * on a film can pass 50 KB.

    mcp-tool

    {
      "type": "object",
      "required": [
        "resource",
        "id"
      ],
      "properties": {
        "id": {
          "type": "integer",
          "description": "Numeric record id: the last segment of the entity's url field (1 in .../api/people/1)."
        },
        "expand": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional. Relations to embed, one level deep, under a final \"expanded\" key: PEOPLE homeworld, films, species, vehicles, starships; FILMS characters, planets, starships, vehicles, species; PLANETS residents, films; SPECIES homeworld, people, films; STARSHIPS and VEHICLES pilots, films; or [\"*\"] alone for all. Up to 8 names; an unknown name returns a tool error."
        },
        "resource": {
          "enum": [
            "PEOPLE",
            "FILMS",
            "PLANETS",
            "SPECIES",
            "STARSHIPS",
            "VEHICLES"
          ],
          "type": "string",
          "description": "Resource type: PEOPLE, FILMS, PLANETS, SPECIES, STARSHIPS or VEHICLES. Any other value returns a tool error."
        }
      }
    }
    arguments 32 lines
  • sw_search reads unknown 2h ago

    Start here. Finds Star Wars entities by name (title for FILMS) with a case-insensitive substring match: 'sky' finds Luke, Anakin and Shmi Skywalker. Returns a JSON array of full entities; an empty array [] means no match; pass fields to shorten each entity. The id to pass to sw_get is the last segment of each entity's url field. Data covers Episodes I-VI only.

    mcp-tool

    {
      "type": "object",
      "required": [
        "resource",
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Name or title fragment, case-insensitive (e.g. 'falcon', 'hope')."
        },
        "fields": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional. Field names to keep in each entity (url is always kept), e.g. [\"name\"] (FILMS: [\"title\"]). Up to 24 names; an unknown name returns a tool error listing the valid ones. Omit for full entities."
        },
        "resource": {
          "enum": [
            "PEOPLE",
            "FILMS",
            "PLANETS",
            "SPECIES",
            "STARSHIPS",
            "VEHICLES"
          ],
          "type": "string",
          "description": "Resource type: PEOPLE, FILMS, PLANETS, SPECIES, STARSHIPS or VEHICLES. Any other value returns a tool error."
        }
      }
    }
    arguments 32 lines
  • sw_list reads unknown 10h ago

    Lists every entity of one Star Wars resource type as a JSON array (Episodes I-VI data). Responses are large (all 82 PEOPLE, about 38 KB); to find a single entity, prefer sw_search, then sw_get; for a compact index pass fields, e.g. ["name"] (about 5 KB).

    mcp-tool

    {
      "type": "object",
      "required": [
        "resource"
      ],
      "properties": {
        "fields": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional. Field names to keep in each entity (url is always kept), e.g. [\"name\"] (FILMS: [\"title\"]). Up to 24 names; an unknown name returns a tool error listing the valid ones. Omit for full entities."
        },
        "resource": {
          "enum": [
            "PEOPLE",
            "FILMS",
            "PLANETS",
            "SPECIES",
            "STARSHIPS",
            "VEHICLES"
          ],
          "type": "string",
          "description": "Resource type: PEOPLE, FILMS, PLANETS, SPECIES, STARSHIPS or VEHICLES. Any other value returns a tool error."
        }
      }
    }
    arguments 27 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 9b3c808337b28f36.

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