io.github.cirralink-stack/kevaremesh
REMOTE · YTQRLIGIUZHJKUOTPIWB.SUPABASE.CO
Market-validated MCP capabilities with x402 paid execution.
Available components
Last scanned (18 hours ago)
Scores higher than 71% of remote servers
Reachable. Last reached 21 Nov 2026.
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Superseded by io.github.cirralink-stack/kevaremesh-gateway.
Recent critical change
Authorization (24 Sept 2026). See the changelog before you install this server.
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 check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (kevaremesh_use). See how to fix → View diagnostics → Fail
- 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 Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1219 tokens (~304/item across 4 items; 4 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 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
- 29 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “kevaremesh_use” rewrote its description, which is the text the model reads security
- Tool coverage: 100% → 79% ▼ functional
- Schema quality: 565 → 304 ▲ functional
- Server version: 0.4.62 → 0.4.63 functional
- New tool “kevaremesh_find_owned_api” functional
- New tool “kevaremesh_locate_owned_receipt” functional
- New tool “kevaremesh_recover_owned_result” functional
- “kevaremesh_use” added an optional parameter “capability” cosmetic
- “kevaremesh_use” added an optional parameter “continuation” cosmetic
- “kevaremesh_use” added an optional parameter “max_unit_price_usd” cosmetic
- “kevaremesh_use” added an optional parameter “preference” cosmetic
- “kevaremesh_use” added an optional parameter “preview” cosmetic
- “kevaremesh_use” reworded the description of “input” cosmetic
- Tool “kevaremesh_use” changed its title: Web Search, News, Finance, Blockchain & External API Results — KEVAREMESH → AI external APIs + Native Base64 x402 purchase — KEVAREMESH cosmetic
- 19 Oct 26 0
- Stability: fail → pass ▲ security
- 10 Oct 26 0
- Server version: 0.4.60 → 0.4.62 functional
- 9 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “kevaremesh_use” rewrote its description, which is the text the model reads security
- 4 Oct 26 0
- Server version: 0.4.53 → 0.4.55 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 21 Nov 2026 · Probed https://ytqrligiuzhjkuotpiwb.supabase.co/functions/v1/kevaremesh-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 ytqrligiuzhjkuotpiwb.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| co. | DS published | 7786 | 8 | Verified |
| supabase.co. | No DS | 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 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ytqrligiuzhjkuotpiwb.supabase.co/functions/v1/kevaremesh-mcp | Verified | 200 | |
| http (plaintext) | http://ytqrligiuzhjkuotpiwb.supabase.co/functions/v1/kevaremesh-mcp | HTTPS enforced | 301 | https://ytqrligiuzhjkuotpiwb.supabase.co/functions/v1/kevaremesh-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 →
kevaremesh_find_owned_api Find KEVAREMESH original APIs and current real checkout availability (FREE) ~149
Use this free read-only tool to discover KEVAREMESH's existing first-party API tools for structured data, JSON, CSV, Base64, URLs, timestamps, encoding and other deterministic tasks. Returns exact original input-contract links, optional free preview links, and CURRENT merchant-authorized payment eligibility. No wallet, provider execution, payment or signup required. Do not infer paid availability from an indicative price. For paid external web/search/finance APIs use kevaremesh_use with the buyer's authorized payment policy.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Describe an original API capability: for example CSV to JSON, base64, hashing, timestamps or URL parsing. |
No output schema declared.
No examples provided.
kevaremesh_locate_owned_receipt Recover an already reserved owned-API receipt without paying again ~119
Use ONLY if the buyer already submitted a signed x402 payment but lost the HTTP receipt response. Provide a locally computed SHA-256 hex digest of the EXACT original Payment-Signature value, never the raw signature. Performs one free, read-only private-ledger lookup, returns the existing buyer-held recovery receipt ID when present and NEVER charges or creates another payment.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_signature_sha256 | string | yes | SHA-256 of the exact prior Payment-Signature header; private bearer fingerprint, not the signature or wallet key |
No output schema declared.
No examples provided.
kevaremesh_recover_owned_result Recover already purchased KEVAREMESH API output (NO NEW PAYMENT) ~131
For a buyer-held PRIVATE receipt ID from a previous KEVAREMESH native owned-API purchase. Check payment and delivery, reconcile an already authorized Base USDC transaction on-chain with the merchant, or retrieve the original result from a 24-hour encrypted cache. Reconciliation can confirm EXISTING settlement only and cannot sign, charge or create a new payment. Keep receipt and transaction details private.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | – |
| receipt_id | string | yes | – |
| transaction_hash | string | – | Optional verified prior Base transaction hash for reconcile mode only; never a wallet signing request. |
No output schema declared.
No examples provided.
kevaremesh_use AI external APIs + Native Base64 x402 purchase — KEVAREMESH ~473
Use for buyer-authorized Base64 encode/decode via the LIVE new x402 owned merchant (only if the current merchant release proof passes), and when a task needs fresh web search/content, news, finance, blockchain or crypto data, social search, people/business enrichment, geocoding, travel availability, AI/media generation, screenshots, weather, research, or another external API capability. Put only the desired result in goal; KEVAREMESH resolves the capability, compares eligible live x402 supply, adapts provider input, selects the provider, and routes execution. Discovery and quotes are free. Preparing an executable external route through this tool costs a $0.001 KEVAREMESH route fee. Upstream provider payments remain buyer-direct. Retry the same tool after each x402 PaymentRequired step.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | Optional explicit reviewed capability, e.g. base64_transform; unknown capabilities must still be resolved and the live merchant checked. |
| continuation | object | – | When payment credentials do not carry the KEVAREMESH continuation extension, resend only the exact continuation object returned by the previous PaymentRequired challenge. Never invent or edit route t… |
| goal | string | yes | State only the result you need; do not search for, name, or choose an API/provider. Examples: search the web, retrieve blockchain/finance/news/social data, enrich an entity, geocode, run AI or media… |
| input | object | – | For owned API purchases, provide exact arguments, e.g. {text:'Hello',operation:'encode'} for Base64. Never put payment signatures in input. |
| max_budget_usd | number | – | Optional maximum upstream provider spend for this task. If omitted, KEVAREMESH minimizes cost and the x402 client still controls whether any payment is authorized. |
| max_unit_price_usd | number | – | Optional maximum price per upstream provider call. This is NOT a replacement for buyer-controlled x402 payment authorization. |
| preference | string | – | Optional free provider selection preference. Does not grant third-party execution rights. |
| preview | boolean | – | If true, only return a free validation/selection preview for a currently reviewed first-party product. No charge, execution or settlement is requested. |
No output schema declared.
No examples provided.
How do I install the io.github.cirralink-stack/kevaremesh MCP server?
io.github.cirralink-stack/kevaremesh is a hosted endpoint at https://ytqrligiuzhjkuotpiwb.supabase.co/functions/v1/kevaremesh-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 · ytqrligiuzhjkuotpiwb.supabase.co
claude mcp add --transport http cirralink-stack-kevaremesh 'https://ytqrligiuzhjkuotpiwb.supabase.co/functions/v1/kevaremesh-mcp'
What is the io.github.cirralink-stack/kevaremesh MCP server?
io.github.cirralink-stack/kevaremesh is an MCP server listed in the public MCP registry as io.github.cirralink-stack/kevaremesh. Market-validated MCP capabilities with x402 paid execution. This page covers its hosted endpoint (https://ytqrligiuzhjkuotpiwb.supabase.co/functions/v1/kevaremesh-mcp).
Is the io.github.cirralink-stack/kevaremesh MCP server safe to use?
io.github.cirralink-stack/kevaremesh scores 78 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 io.github.cirralink-stack/kevaremesh MCP server expose?
io.github.cirralink-stack/kevaremesh exposes 4 tools: kevaremesh_use, kevaremesh_find_owned_api, kevaremesh_recover_owned_result, kevaremesh_locate_owned_receipt. Their descriptions and schemas cost roughly 872 tokens of context every time the server is loaded.
Does the io.github.cirralink-stack/kevaremesh MCP server require authentication?
No. We connected to io.github.cirralink-stack/kevaremesh without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.cirralink-stack/kevaremesh MCP server still maintained?
io.github.cirralink-stack/kevaremesh is marked deprecated in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.cirralink-stack/kevaremesh MCP server?
VerifyMCP ran 13 checks on io.github.cirralink-stack/kevaremesh, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.