Skip to content

PearlGraph MCP server

com.pearl100.api/pearl-hundredapi.pearl100.comstreamable-httpv0.6.0Scanned

Open, source-backed Uganda tourism data: parks, fees, road routes, trips, lodges, districts.

1 tool: 1 do something that can't be undone.

Tools: 0 delete, 1 irreversible, 0 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • 1 finding

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the PearlGraph MCP server can do

The PearlGraph MCP server is published by api.pearl100.com, a domain the MCP Registry verified. It has 1 tool. It can do things that cannot be undone, such as sending, paying or publishing (pearlgraph), but cannot delete data. None of its tools only reads.

1 tool can send data out of your system (pearlgraph).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its tools changed once since Anlyon Radar first saw them.

Last scanned Oct 31, 2026, version 0.6.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

1 tool

Can't be undone 1Claude Code: ask
  • pearlgraphSingle entry point to all PearlGraph Uganda tourism data.Can send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "pearlgraph" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Single entry point to all PearlGraph Uganda tourism data. Pick an `action`: map (audience, month) - unified map, entry rules and source catalogue; attractions (query, region, category) - parks, sites, hours, activities, durations; fees (feeIds) - UWA tariffs, including the low season permit rates for April, May and November; route (from, to, month) - road km and drive time; plan (start, stops | days, month) - build or check an itinerary by drive time, opening hours and activity length; lodges (near, tier, district, type, query) - stays, `near` = attraction id within 90 min drive; districts (query, region); essentials (audience: foreign|local); seasons (region) - seasons and operators; permits (attractionId) - permit capacity per sector and access rules; transport (query) - airstrips, flights, ferries; search (query, kind: attraction|district|stay) - meaning-based search over free text, e.g. 'see apes in rainforest'; graph (query = id or name, depth 1-2, predicate) - knowledge-graph links: inDistrict, inRegion, isA, offers, pricedBy, anchoredAt, roadTo. Ids come from earlier results (e.g. kampala, bwindi-rushaga).

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 21, 2026, 19:23 UTC, unchanged since Nov 14, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
525
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 525.

Posture changes

  1. Nov 14, 2026
    • HTTP status of an anonymous initialize: 200 to 525
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "pearlgraph" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 525; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 525
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
  2. Tools1 changed.~1 changedView diff
    • Changed:pearlgraphCan't be undonedescriptioninputSchema

Install

Pinned to version 0.6.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http pearl-hundred https://api.pearl100.com/mcp
claude mcp add --transport http pearl-hundred https://api.pearl100.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__pearl-hundred__pearlgraph"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pearl-hundred. Review it before you use it.

Capability tags behind 1 rule
  • mcp__pearl-hundred__pearlgraph outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.pearl100.api/pearl-hundred/verify?hash=8cfe4418028c9952e45ff08fc11afe19652882297b01aa38720d026f44f44083" | jq -e '.changed == false'

Pinned hash 8cfe4418028c, from Oct 31, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.pearl100.api/pearl-hundred/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.pearl100.api/pearl-hundred
[![Anlyon Radar](https://radar.anlyon.com/badge/com.pearl100.api/pearl-hundred.svg)](https://radar.anlyon.com/servers/com.pearl100.api/pearl-hundred)

Source: MCP Registry. Synced Oct 31, 2026, 19:17 UTC.

PearlGraph MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the PearlGraph MCP server safe?

No scan can promise that. What its definitions show: 1 tool, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the PearlGraph MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the PearlGraph MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: pearlgraph.

What tools does the PearlGraph MCP server have?

1 tool: 1 irreversible. pearlgraph.

Does the PearlGraph MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the PearlGraph MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): pearlgraph.

Has the PearlGraph MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 31, 2026. Every change is on this page and in its Atom feed.