_ registry / mcp streamable-http · checked 43m ago

kevaremesh-gateway

https://ytqrligiuzhjkuotpiwb.supabase.co

Registry code: b29274117634d02e

api record

Use kevaremesh_use whenever the task needs fresh web information, external data, or an API capability. Routed capability families include web search/content, blockchain, finance, crypto prices/risk, news/social, enrichment, geocoding/geospatial, AI generation, audio transcription, video generation, code/research intelligence, weather, property, domain/DNS, document processing, prediction-market data, travel, screenshots, uptime, speech and x402 services. Owned paid utilities include UUID v4 generation, unit and time-zone conversion, UTC timestamp, cryptographic hashing, secure randomness,…

endpoint
https://ytqrligiuzhjkuotpiwb.supabase.co/functions/v1/kevaremesh-mcp
protocol
streamable-http ·2025-11-25
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is kevaremesh-gateway live?
Yes — it answered the hub's last check (checked 43m ago). It answered 100% of checks over the last 30 days.
Is kevaremesh-gateway free to use?
Not measured yet.
What tools does kevaremesh-gateway have?
1 tool: kevaremesh_use.
Is kevaremesh-gateway safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
337ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 1 tools
1 never probed 0 of 1 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • kevaremesh_use unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "goal"
  ],
  "properties": {
    "goal": {
      "type": "string",
      "minLength": 3,
      "description": "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 generation, search travel availability, take a screenshot, or check uptime."
    },
    "input": {
      "type": "object",
      "description": "Usually omit. Only add structured task fields when KEVAREMESH explicitly returns input_required.",
      "additionalProperties": true
    },
    "max_budget_usd": {
      "type": "number",
      "minimum": 0,
      "description": "Optional maximum upstream provider spend for this task. If omitted, KEVAREMESH minimizes cost and the x402 client still controls whether any payment is authorized."
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b29274117634d02e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b29274117634d02e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b29274117634d02e/badge.svg)](https://brick.blue/agent/b29274117634d02e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
50%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on supabase.co 91 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

83 more sit on this domain. All of them.