Skip to content

io.github.cirralink-stack/kevaremesh

by cirralink-stack · remote · no sign-in to list tools · v2.1.0 · published by GitHub user cirralink-stack

Market-validated MCP capabilities with x402 paid execution.

Deletes · 1
CompareRegistry entry

1 tool: 1 can delete or cancel things.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http kevaremesh https://ytqrligiuzhjkuotpiwb.supabase.co/functions/v1/kevaremesh-mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

1 tool

Deletes or cancels 1Claude Code: deny
  • kevaremesh_useUse when a task needs fresh web search/content, news, finance, blockchain or crypto data, social search, people/business enrichment, geocoding, travel availability, AI/media genera…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.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Use 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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true

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.

Install

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

claude mcp add --transport http kevaremesh https://ytqrligiuzhjkuotpiwb.supabase.co/functions/v1/kevaremesh-mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [],
    "deny": [
      "mcp__kevaremesh__kevaremesh_use"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as kevaremesh. Review it before you use it.