io.github.GeiserX/biblical-atlas-mcp

What it mainly works on, as our AI model read its tool descriptions: nothing outside itself: it only answers questions.

None of its 9 tools are described as changing anything.

• dataset_infoon 7 other serversreads or searches

  “What the loaded atlas contains and how fresh it is: build date, record counts, which Bible books the atlas has read verse by verse and which it has not, and where the data came from.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  Takes no inputs.

• find_connectionon 1 other serverreads or searches

  “How two people are connected: the shortest chain of family ties, succession, discipleship and companionship between them, one step at a time with the atlas's Spanish phrase and the Bible reference be…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  3 inputs, 2 required

  • fromstringrequired“Person id from search.”
  • max_stepsinteger“Longest chain to look for.”
  • tostringrequired“Another person id from search.”
• get_recordon 39 other serversreads or searches

  “Get one atlas record in full: a person with family, relations, offices and events; a place with coordinates, candidate sites, the gates, towers and other sites inside it, and what happened there; an …”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  4 inputs, 2 required

  • idstringrequired“Record id, from search.”
  • relations_offsetinteger“Person only: relations to skip.”
  • sources_offsetinteger“Sources to skip.”
  • typestringrequired“Record type, from search.”
• list_eventson 106 other serversreads or searches

  “List events in date order, filtered by any mix of year or year range, person, place, kind of event and Bible book.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  10 inputs

  • anchored_onlyboolean“Leave out events placed only by the order of the story (date kind "narrativa").”
  • bookstring“Bible book: name, abbreviation or slug ("Rut", "Hch", "1-samuel").”
  • from_yearinteger“Signed historical year: -607 is 607 a.e.c.”
  • kindstring“Kind of event, for example "speech", "death", "birth", "writing".”
  • limitinteger“Results per page.”
  • offsetinteger“Results to skip; use next_offset from the previous page.”
  • personstring“Person id from search.”
  • placestring“Place id from search.”
  • rolestring“The person's role in the event, for example "born", "died", "spoke".”
  • to_yearinteger“End of the range, same convention.”
• list_recordson 11 other serversreads or searches

  “List the atlas's small collections in full: periods (reigns, empires, eras, high priests, governors), letters, journeys, archaeological finds, guided tours, Bible books, Hebrew months and calendar to…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  4 inputs, 1 required

  • kindstring“Required for person (an office, for example "high_priest" or "king") and place (a place kind, for example "rio" or "ciudad").”
  • limitinteger“Results per page.”
  • offsetinteger“Results to skip; use next_offset from the previous page.”
  • typestringrequired“What to list.”
• lookup_passagereads or searches

  “What the atlas has on a Bible passage: the events whose passages overlap it, the people and places in those events, and the letters, journey stops and other records that cite the chapter.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  3 inputs, 1 required

  • limitinteger“Results per page.”
  • offsetinteger“Results to skip; use next_offset from the previous page.”
  • referencestringrequired“One Spanish Bible reference: "Hch 16:1", "Hechos 16", "2 Reyes 3", "Gé 2:7, 8", "Hch 13:1–14:28" or a book alone, "Rut".”
• people_in_yearreads or searches

  “Who was alive, ruling or active in a given year, and which reigns, empires and eras covered it.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  3 inputs, 1 required

  • limitinteger“Results per page.”
  • offsetinteger“Results to skip; use next_offset from the previous page.”
  • yearintegerrequired“Signed historical year: -607 is 607 a.e.c.”
• places_nearreads or searches

  “Places in the atlas within a distance of a place or a coordinate, nearest first.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  7 inputs

  • kindstring“Only places of this kind, for example "ciudad", "monte", "rio".”
  • latnumber“Latitude of the origin, -90 to 90.”
  • limitinteger“Results per page.”
  • lonnumber“Longitude of the origin, -180 to 180.”
  • offsetinteger“Results to skip; use next_offset from the previous page.”
  • placestring“Place id from search.”
  • radius_kmnumber“Search radius in km, above 0 and at most 2000.”
• searchon 763 other serversreads or searches

  “Find people, places, events, periods, letters, journeys, archaeological finds, tours, Bible books and Hebrew months in the atlas by name.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  4 inputs, 1 required

  • limitinteger“Results per page.”
  • offsetinteger“Results to skip; use next_offset from the previous page.”
  • querystringrequired“Name to look for, in Spanish, for example "Pablo", "Jerusalén", "Diluvio".”
  • typesarray“Only these record types.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.