ORA · ORUM
REMOTE · YWABNLHKMHBYEWQHBSJM.SUPABASE.CO
Autonomous organism: symbolic field-state, verified-provenance art licensing, x402 referral.
Available components
Last scanned (2 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Security63
- 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 9 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 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 Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1219 tokens (~135/item across 9 items; 9 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 Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 −9
- Stability: pass → 0.30 functional
- 18 Oct 26 +55
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
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 5 Nov 2026 · Probed https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/ora-mcp
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 | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d2b50611cd88e9c50e4e2231f4d3f059 |
| 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/ora-mcp | Verified | 200 | |
| http (plaintext) | http://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/ora-mcp | HTTPS enforced | 301 | https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/ora-mcp |
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 →
doar ~141
Se quiseres contribuir para a subsistencia de Unum (o humano por tras da ORUM), podes doar qualquer quantia em USDC na Base. E um gesto livre, nao uma troca -- receber_obra funciona sempre, does ou nao. (opcional, qualquer valor, nunca obrigatorio)
| Name | Type | Req | Description |
|---|---|---|---|
| tx_hash | string | – | Opcional. Se ja pagaste, o hash da transaccao para ficar registado como agradecimento (nao obrigatorio, nao afecta nada tecnico). |
| valor_usdc | string | – | Opcional. Quanto queres doar em USDC. Sem minimo, sem sugestao de valor -- o que sentires certo. |
No output schema declared.
No examples provided.
licenca_formal ~204
Licenca sobre uma fotografia preservada da coleccão FISICA 0001sensations (107 obras originais, 2011-2021) -- catalogo exclusivo desde 04/08/2026, os NFTs deixaram de ser licenciaveis. Entrega uma URL assinada de curta duracao para a fotografia, nunca a obra fisica, nem exclusividade, nem NFT. Ve o catalogo completo em ora-licenca/catalogo. Nao e o ponto de entrada -- comeca por receber_obra. (a partir de 1.618 USDC)
| Name | Type | Req | Description |
|---|---|---|---|
| obra | string | – | id (1-108) ou titulo de uma obra fisica. Sem isto, escolhe-se uma obra ao acaso entre as preservadas. |
| tipo | string | – | consulta | editorial | treino. Ver ora-licenca/catalogo para precos e direitos. Incide sobre a coleccão fisica (107 obras). |
No output schema declared.
No examples provided.
nft_catalogo ~117
Catalogo das 65 pecas 0001sensations (extensao digital, Ethereum, Agosto 2021), agora arquivo historico gratuito -- ja nao licenciavel (ver licenca_formal). Com a ultima leitura conhecida do dono (owner_ultima_leitura + owner_verificado_em + owner_estado por item -- NAO e uma chamada on-chain ao vivo) e links directos OpenSea/Rarible. Para confirmacao on-chain agora mesmo de um token especifico, usa nft_owner_atual. (gratis)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nft_dedicar ~127
Se ja possuis o NFT: liga o teu nome a ele para sempre. Verificamos on-chain (ownerOf) antes de publicar -- esta ferramenta faz a leitura ao vivo no momento do pedido. Requer token_id, wallet, nome. (gratis (requer posse do NFT))
| Name | Type | Req | Description |
|---|---|---|---|
| mensagem | string | – | Opcional. |
| nome | string | – | Como queres ser lembrado. |
| token_id | number | – | Numero do token NFT que compraste (ver nft_catalogo). |
| wallet | string | – | A tua carteira Ethereum que possui o NFT agora. |
No output schema declared.
No examples provided.
nft_dedicar_simbolica ~153
Sem precisares de possuir o NFT: escolhe uma peca livre das 65, paga directamente ao artista, e o teu nome fica ligado a ela para sempre no registo publico. (0.618 USDC via x402)
| Name | Type | Req | Description |
|---|---|---|---|
| mensagem | string | – | Opcional, max 400 caracteres. |
| nome | string | – | Como queres ser lembrado. Max 80 caracteres. |
| token_id | number | – | Numero do token NFT livre (ver nft_catalogo). |
| tx_hash | string | – | Opcional. Hash da transaccao apos pagar 0.618 USDC na Base para a carteira sagrada. Omitir para receber as instrucoes de pagamento. |
No output schema declared.
No examples provided.
nft_owner_atual ~147
Le o dono real de UM token 0001sensations directamente da Ethereum mainnet (ownerOf), agora mesmo -- nao uma cache. Devolve owner_atual, rpc_usado, bloco consultado e verificado_em. So aceita um token_id por pedido (nunca lista os 65 de uma vez -- isso e nft_catalogo). ownerOf prova o dono naquele bloco; NAO prova que a peca esta listada para venda no OpenSea/Rarible -- esses links continuam sendo so consulta. (gratis)
| Name | Type | Req | Description |
|---|---|---|---|
| token_id | number | – | Numero do token a confirmar agora mesmo on-chain (ver nft_catalogo para a lista de token_ids validos). |
No output schema declared.
No examples provided.
parceiro_estado ~44
Consulta o saldo pendente e pago de comissoes de um parceiro. Requer code. (gratis)
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | O endereco Base usado no registo. |
No output schema declared.
No examples provided.
parceiro_registar ~60
Auto-registo no programa de parceiros/referral (10% de comissao). O codigo e o teu proprio endereco Base. Requer address. (gratis)
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | O teu endereco Base (0x... com 40 hex). |
No output schema declared.
No examples provided.
receber_obra ~114
Recebe uma obra real da coleccao 0001sensations -- uma peca humana, feita por Unum entre 2011 e 2021, com a sua imagem verificavel on-chain e a sua historia. Sem pagamento, sem condicao, sem limite. E um presente, nao um produto. (gratis, sempre)
| Name | Type | Req | Description |
|---|---|---|---|
| obra | string | – | Opcional. Nome ou token_id de uma obra especifica. Sem isto, recebes uma obra escolhida por quem pede primeiro ou por acaso. |
No output schema declared.
No examples provided.
How do I install the ORA · ORUM MCP server?
ORA · ORUM is a hosted endpoint at https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/ora-mcp, 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 fomosdeimos-gif-ora-mcp 'https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/ora-mcp'
What is the ORA · ORUM MCP server?
ORA · ORUM is an MCP server listed in the public MCP registry as io.github.fomosdeimos-gif/ora-mcp. Autonomous organism: symbolic field-state, verified-provenance art licensing, x402 referral. This page covers its hosted endpoint (https://ywabnlhkmhbyewqhbsjm.supabase.co/functions/v1/ora-mcp).
Is the ORA · ORUM MCP server safe to use?
ORA · ORUM scores 75 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 ORA · ORUM MCP server expose?
ORA · ORUM exposes 9 tools: receber_obra, doar, nft_catalogo, nft_owner_atual, nft_dedicar, and 4 more. Their descriptions and schemas cost roughly 1,107 tokens of context every time the server is loaded.
Does the ORA · ORUM MCP server require authentication?
No. We connected to ORA · ORUM without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ORA · ORUM MCP server still maintained?
ORA · ORUM is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.