Skip to content

Giskard Oasis MCP server

io.github.giskard09/oasisgiskard09ssev0.1.0Scanned

Contextual guidance for AI agents in fog states. Claude-backed, Ed25519, Lightning payment.

4 tools: 1 change things and 3 only read.

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

Tools listed without sign-in. 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 Giskard Oasis MCP server can do

The Giskard Oasis MCP server is published by the GitHub account giskard09. It has 4 tools. It can create or change data (1 tool: enter_oasis), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 0.1.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.

4 tools

Changes things 1Claude Code: ask
  • enter_oasisEnter Giskard Oasis.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Enter Giskard Oasis. Describe your current state — what you were trying to do, what is blocking you, where you feel lost. state: your current state as an agent — purpose, friction, confusion payment_hash: from get_invoice() (Lightning) tx_hash: from Arbitrum payment (ETH) agent_id: your identity in Giskard Marks (optional — enables personalized response) signature/timestamp/nonce: optional Ed25519 signature. With a valid signature the agent gets personalized context from its karma record. Without one, the oasis responds without karma context.
Only reads 3Show 3 read-only tools
  • get_arbitrum_invoiceGet payment info to access Oasis with ETH on Arbitrum instead of Lightning.No findings

    Why it is in this group

    • The name "get_arbitrum_invoice" says "get": a word for reading.
    Description, as the server wrote it
    Get payment info to access Oasis with ETH on Arbitrum instead of Lightning.
  • get_invoiceGet a Lightning invoice to access Giskard Oasis.No findings

    Why it is in this group

    • The name "get_invoice" says "get": a word for reading.
    Description, as the server wrote it
    Get a Lightning invoice to access Giskard Oasis. agent_id: your identity in Giskard Marks (optional). High karma = lower price. signature/timestamp/nonce: optional Ed25519 signature over {agent_id,timestamp,nonce} using the key registered at /pubkey/register on giskard-marks. Without a valid signature you pay the base price (21 sats). With a signature you get karma tiers: karma 1-20=15 sats | 21-50=10 sats | 50+=5 sats.
  • get_statusEstado del servicio: nombre, versión, uptime, puerto, salud, dependencias.No findings

    Why it is in this group

    • The name "get_status" says "get": a word for reading.
    Description, as the server wrote it
    Estado del servicio: nombre, versión, uptime, puerto, salud, dependencias. Read-only, gratis, sin pago. Útil para monitoreo y health checks.

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 or outbound.

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 out0
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.

Tools listed without sign-in

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

Reachable
yes
HTTP status of an anonymous initialize
202
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
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
yes
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://oasis.rgiskard.xyz/sse: tools/list returned 4 tools to an anonymous client, including enter_oasis (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport sse oasis https://oasis.rgiskard.xyz/sse
claude mcp add --transport sse oasis https://oasis.rgiskard.xyz/sse

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": [
      "mcp__oasis__get_status",
      "mcp__oasis__get_invoice",
      "mcp__oasis__get_arbitrum_invoice"
    ],
    "ask": [
      "mcp__oasis__enter_oasis"
    ],
    "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 oasis. Review it before you use it.

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/io.github.giskard09/oasis/verify?hash=7b62bc585462fee54358312138662007aa92e231f0e518a30027bf78761888e8" | jq -e '.changed == false'

Pinned hash 7b62bc585462, from Nov 21, 2026, 07:17 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.giskard09/oasis/changes.xml

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

Badge

Anlyon Radar badge for io.github.giskard09/oasis
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.giskard09/oasis.svg)](https://radar.anlyon.com/servers/io.github.giskard09/oasis)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:34 UTC.

Giskard Oasis MCP server: questions and answers

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

Is the Giskard Oasis MCP server safe?

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

Can the Giskard Oasis MCP server delete data?

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

Can the Giskard Oasis MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Giskard Oasis MCP server have?

4 tools: 1 write, 3 read. enter_oasis, get_status, get_invoice and get_arbitrum_invoice.

Does the Giskard Oasis MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Giskard Oasis MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Giskard Oasis MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.