Giskard Oasis
REMOTE · OASIS.RGISKARD.XYZ · SCANNED AUG 3
Contextual guidance for AI agents in fog states. Claude-backed, Ed25519, Lightning payment.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability49
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 411 tokens (~102/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (75% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · oasis.rgiskard.xyz
claude mcp add --transport http giskard09-oasis https://oasis.rgiskard.xyz/sse
[mcp_servers.giskard09-oasis] url = "https://oasis.rgiskard.xyz/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"giskard09-oasis": {
"type": "remote",
"url": "https://oasis.rgiskard.xyz/sse",
"enabled": true
}
}
} openclaw mcp add giskard09-oasis --url https://oasis.rgiskard.xyz/sse --transport streamable-http
mcp_servers:
giskard09-oasis:
url: "https://oasis.rgiskard.xyz/sse" {
"mcpServers": {
"giskard09-oasis": {
"type": "http",
"url": "https://oasis.rgiskard.xyz/sse"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +24
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 22
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://oasis.rgiskard.xyz/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rgiskard.xyz | CN=YE1,O=Let's Encrypt,C=US | 26 Jul 2026 | 24 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6d05006d650dfbdb7edbda6cdbe6fc902e5 |
| SANs: *.rgiskard.xyz, rgiskard.xyz | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of oasis.rgiskard.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| rgiskard.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 405 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://oasis.rgiskard.xyz/sse | Verified | 200 | |
| http (plaintext) | http://oasis.rgiskard.xyz/sse | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
enter_oasis ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | — | — |
| nonce | string | — | — |
| payment_hash | string | — | — |
| signature | string | — | — |
| state | string | yes | — |
| timestamp | integer | — | — |
| tx_hash | string | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_arbitrum_invoice ~27
Get payment info to access Oasis with ETH on Arbitrum instead of Lightning.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_invoice ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | — | — |
| nonce | string | — | — |
| signature | string | — | — |
| timestamp | integer | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_status ~43
Estado del servicio: nombre, versión, uptime, puerto, salud, dependencias. Read-only, gratis, sin pago. Útil para monitoreo y health checks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.