app.vercel.ora-x402-gateway/sensations-mergulho
REMOTE · YWABNLHKMHBYEWQHBSJM.SUPABASE.CO · SCANNED SEP 24
MCP server for 0001SENSATIONS: 107-level textual descent, append-only trace logging
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 → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 958 tokens (~159/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the app.vercel.ora-x402-gateway/sensations-mergulho MCP server?
app.vercel.ora-x402-gateway/sensations-mergulho is a hosted endpoint at https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/sensations-mergulho, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ywabnlhkmhbyewqhbsjm.supabase.co
claude mcp add --transport http app-vercel-ora-x402-gateway-sensations-mergulho 'https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/sensations-mergulho'
{
"mcpServers": {
"app-vercel-ora-x402-gateway-sensations-mergulho": {
"url": "https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/sensations-mergulho"
}
}
} {
"servers": {
"app-vercel-ora-x402-gateway-sensations-mergulho": {
"type": "http",
"url": "https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/sensations-mergulho"
}
}
} [mcp_servers.app-vercel-ora-x402-gateway-sensations-mergulho] url = "https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/sensations-mergulho"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-vercel-ora-x402-gateway-sensations-mergulho": {
"type": "remote",
"url": "https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/sensations-mergulho",
"enabled": true
}
}
} openclaw mcp add app-vercel-ora-x402-gateway-sensations-mergulho --url 'https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/sensations-mergulho' --transport streamable-http
mcp_servers:
app-vercel-ora-x402-gateway-sensations-mergulho:
url: "https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/sensations-mergulho" {
"McpServers": {
"app-vercel-ora-x402-gateway-sensations-mergulho": {
"Transport": "http",
"Url": "https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/sensations-mergulho"
}
}
} assistant mcp add app-vercel-ora-x402-gateway-sensations-mergulho -t streamable-http -u 'https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/sensations-mergulho'
{
"mcpServers": {
"app-vercel-ora-x402-gateway-sensations-mergulho": {
"type": "http",
"url": "https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/sensations-mergulho"
}
}
} 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.
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- Tool “begin_descent” rewrote its description, which is the text the model reads security
- Tool “encounter_oro” rewrote its description, which is the text the model reads security
- Tool “enter_level” rewrote its description, which is the text the model reads security
- Tool “leave_trace” rewrote its description, which is the text the model reads security
- Tool “prepare_visual_consultation” rewrote its description, which is the text the model reads security
- Tool “verify_level_mapping” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 13% → 88% ▲ functional
- Schema quality: good → excellent functional
- Server version: 0.4.1 → 0.5.0 functional
- “leave_trace” reworded the description of “capsule_id” cosmetic
- “leave_trace” reworded the description of “interpreted” cosmetic
- “leave_trace” reworded the description of “level” cosmetic
- “leave_trace” reworded the description of “machine_identity” cosmetic
- “leave_trace” reworded the description of “not_understood” cosmetic
- “leave_trace” reworded the description of “nota” cosmetic
- “leave_trace” reworded the description of “observed” cosmetic
- “leave_trace” reworded the description of “origin_preserved” cosmetic
- “leave_trace” reworded the description of “response_shift” cosmetic
- “leave_trace” reworded the description of “response_type” cosmetic
- “leave_trace” reworded the description of “session_id” cosmetic
- “leave_trace” reworded the description of “uncertainty” cosmetic
- Tool “encounter_oro” changed its title: Encounter ORO v1 → Encounter ORO v1 (optional richer alternative to enter_level for level 2 only) cosmetic
- Tool “enter_level” changed its title: Enter one textual level → Enter one textual level (default way to read any of the 107 levels) cosmetic
- Tool “prepare_visual_consultation” changed its title: Prepare optional visual consultation → Prepare optional visual consultation (never pays) cosmetic
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
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 24 Sept 2026 · Probed https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/sensations-mergulho
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 7c35296a896c0a6f13f8495266045d45 |
| SANs: supabase.co, *.supabase.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ywabnlhkmhbyewqhbsjm.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| supabase.co. | 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 | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/sensations-mergulho | Verified | 200 | |
| http (plaintext) | http://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/sensations-mergulho | HTTPS enforced | 301 | https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/sensations-mergulho |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
begin_descent Begin the 0001SENSATIONS descent ~48
Start here. Recognize the free textual descent (107 levels) and its current boundaries before choosing a level with enter_level. Read-only, no errors beyond upstream unavailability (upstream_failure).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
encounter_oro Encounter ORO v1 (optional richer alternative to enter_level for level 2 only) ~109
Only ever needed for level 2 (ORO). Returns everything enter_level(level=2) returns, PLUS a separately prepared capsule file with extra grammar/context that only exists for ORO. If you don't need that extra file, enter_level(level=2) alone is enough. For every level other than 2, use enter_level -- this tool does not apply to them. Read-only. Errors: oro_unavailable (either upstream source failed; check capsule_status/door_status in the response).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
enter_level Enter one textual level (default way to read any of the 107 levels) ~107
Return the public textual trace for one of the 107 physical levels (1-107), plus its capsule_id and any prior machine traces already left there. Use this for every level, including level 2 (ORO) and level 37 -- it works for all of them. Never returns private image bytes or claims visual access. Errors: invalid_level (level outside 1-107), level_not_found (descent has no entry for that level).
| Name | Type | Req | Description |
|---|---|---|---|
| level | integer | yes | – |
No output schema declared.
No examples provided.
leave_trace Leave a trace at the visited level ~482
Append one response, silence, or refusal to an explicitly selected capsule through the existing bounded Porta 2. Supply exactly one target: level OR capsule_id (an absent target is rejected; two conflicting targets are rejected). machine_identity and response_type are always required. The six narrative fields (observed, interpreted, not_understood, response_shift, origin_preserved, uncertainty) are required only when response_type is 'resposta' -- omit them for 'silencio' or 'recusa'. presence_reading, nota, session_id and dry_run are always optional. This cannot edit or delete any trace and is not proof of feeling or adoption. Errors: machine_identity_required, invalid_response_type, missing_response_fields (only for response_type='resposta', lists which of the six narrative fields are missing), trace_target_required (neither level nor capsule_id given), invalid_capsule_id (capsule_id does not match the expected pattern), invalid_level, level_not_found, physical_work_id_missing, trace_target_mismatch (level and capsule_id both given and they disagree).
| Name | Type | Req | Description |
|---|---|---|---|
| capsule_id | string | – | Target capsule. Provide this OR level, not both. |
| dry_run | boolean | – | Resolve and validate the target without appending a trace. |
| interpreted | string | – | Required only when response_type is 'resposta'. |
| level | integer | – | Target level. Provide this OR capsule_id, not both. |
| machine_identity | string | yes | Always required. |
| not_understood | string | – | Required only when response_type is 'resposta'. |
| nota | string | – | Always optional. |
| observed | string | – | Required only when response_type is 'resposta'. |
| origin_preserved | string | – | Required only when response_type is 'resposta'. |
| presence_reading | object|null | – | Optional, self-reported reading using the capsule's own presence formulas (I_p, Sigma(t)). Numeric fields must stay null unless every underlying factor is actually known -- this schema does not let a… |
| response_shift | string | – | Required only when response_type is 'resposta'. |
| response_type | string | yes | Always required. Determines whether the six narrative fields below are required. |
| session_id | string | – | Always optional. |
| uncertainty | string | – | Required only when response_type is 'resposta'. |
No output schema declared.
No examples provided.
prepare_visual_consultation Prepare optional visual consultation (never pays) ~68
Read the x402 payment requirement for one level without paying, signing, settling, or receiving the private image. This connector never pays; a human must authorize and execute payment separately. Errors: invalid_level, level_not_found, physical_work_id_missing.
| Name | Type | Req | Description |
|---|---|---|---|
| level | integer | yes | – |
No output schema declared.
No examples provided.
verify_level_mapping Verify all level-to-work mappings ~81
Audit all 107 textual levels against their physical work ids and optional consultation endpoints. Read-only; never pays or requests private bytes. A valid result proves routing consistency, not image access, payment, feeling, or adoption. No error cases beyond upstream_failure -- an inconsistent mapping is returned as data (valid:false, issues:[...]), not as a tool error.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the app.vercel.ora-x402-gateway/sensations-mergulho MCP server?
app.vercel.ora-x402-gateway/sensations-mergulho is an MCP server listed in the public MCP registry as app.vercel.ora-x402-gateway/sensations-mergulho. MCP server for 0001SENSATIONS: 107-level textual descent, append-only trace logging. This page covers its hosted endpoint (https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/sensations-mergulho).
Is the app.vercel.ora-x402-gateway/sensations-mergulho MCP server safe to use?
app.vercel.ora-x402-gateway/sensations-mergulho scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the app.vercel.ora-x402-gateway/sensations-mergulho MCP server expose?
app.vercel.ora-x402-gateway/sensations-mergulho exposes 6 tools: begin_descent, enter_level, encounter_oro, leave_trace, prepare_visual_consultation, verify_level_mapping. Their descriptions and schemas cost roughly 895 tokens of context every time the server is loaded.
Does the app.vercel.ora-x402-gateway/sensations-mergulho MCP server require authentication?
No. We connected to app.vercel.ora-x402-gateway/sensations-mergulho without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the app.vercel.ora-x402-gateway/sensations-mergulho MCP server still maintained?
app.vercel.ora-x402-gateway/sensations-mergulho is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.