# KEVAREMESH AI Procurement Gateway (remote · kevaremesh-web.vercel.app)

AI procurement gateway: finds and auto-selects live x402 APIs; provider payments stay buyer-direct.

- Trust score: 68/100 (medium)
- Change this week: −4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

> **Recent critical change**: Authorization (2026-09-23). See the changelog below before you install this server.

## Components

- remote · `kevaremesh-web.vercel.app`: 68/100 (this document), [markdown](https://verifymcp.io/servers/cirralink-stack-kevaremesh-gateway/api-x402-mcp.md), [page](https://verifymcp.io/servers/cirralink-stack-kevaremesh-gateway/api-x402-mcp)

## Channel facts

- Endpoint: `https://kevaremesh-web.vercel.app/api/x402/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.53`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (kevaremesh_use).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 519 tokens (~519/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the KEVAREMESH AI Procurement Gateway MCP server?

KEVAREMESH AI Procurement Gateway is a hosted endpoint at https://kevaremesh-web.vercel.app/api/x402/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.

### Claude

```bash
claude mcp add --transport http cirralink-stack-kevaremesh-gateway 'https://kevaremesh-web.vercel.app/api/x402/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "cirralink-stack-kevaremesh-gateway": {
      "url": "https://kevaremesh-web.vercel.app/api/x402/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cirralink-stack-kevaremesh-gateway": {
      "type": "http",
      "url": "https://kevaremesh-web.vercel.app/api/x402/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cirralink-stack-kevaremesh-gateway]
url = "https://kevaremesh-web.vercel.app/api/x402/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cirralink-stack-kevaremesh-gateway": {
      "type": "remote",
      "url": "https://kevaremesh-web.vercel.app/api/x402/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cirralink-stack-kevaremesh-gateway --url 'https://kevaremesh-web.vercel.app/api/x402/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cirralink-stack-kevaremesh-gateway:
    url: "https://kevaremesh-web.vercel.app/api/x402/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cirralink-stack-kevaremesh-gateway": {
      "Transport": "http",
      "Url": "https://kevaremesh-web.vercel.app/api/x402/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cirralink-stack-kevaremesh-gateway -t streamable-http -u 'https://kevaremesh-web.vercel.app/api/x402/mcp'
```

### Other

```json
{
  "mcpServers": {
    "cirralink-stack-kevaremesh-gateway": {
      "type": "http",
      "url": "https://kevaremesh-web.vercel.app/api/x402/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-26 (score 67, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-09-25 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 67, +1)

- [functional] Server version: 0.4.51 → 0.4.53

### 2026-09-23 (score 66, −6)

- [critical regression] Authorization: partial → fail
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “kevaremesh_use” is now declared destructive
- [functional] Server version: 0.4.50 → 0.4.51
- [functional] Server version: 0.4.49 → 0.4.50
- [functional] Server version: 0.4.46 → 0.4.49
- [functional] Server version: 0.4.44 → 0.4.46
- [functional] Server version: 0.4.41 → 0.4.44
- [functional] Server version: 0.4.40 → 0.4.41

### 2026-09-22 (score 72, 0)

- [security] 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
- [functional regression] Schema quality: 672 → 746
- [functional improvement] Schema quality: 672 → 521
- [functional] Server version: 0.4.37 → 0.4.40
- [functional] Server version: 0.4.36 → 0.4.37
- [functional] Server version: 0.4.32 → 0.4.36
- [functional] Server version: 0.4.31 → 0.4.32
- [cosmetic] “kevaremesh_use” reworded the description of “goal”
- [cosmetic] Tool “kevaremesh_use” changed its title: Get External Results — KEVAREMESH Finds, Compares & Routes APIs → Get External Results — KEVAREMESH
- [cosmetic] Tool “kevaremesh_use” changed its title: Get External Results — KEVAREMESH Finds & Uses the Best API → Get External Results — KEVAREMESH Finds, Compares & Routes APIs

### 2026-09-21 (score 72, +7)

- [security improvement] Authorization: fail → partial
- [security] 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 “kevaremesh_use” no longer declares itself destructive
- [functional regression] Schema quality: 574 → 672
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.4.22 → 0.4.31

## MCP tools (1)

### `kevaremesh_use` (~244 tokens)

Get External Results — KEVAREMESH

Use for tasks that need fresh external data or an API capability. Put 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 route preparation are free. Upstream provider payments are buyer-direct. If no active Access Pass exists, the first successful routed job may request a $0.001 24-hour KEVAREMESH Access Pass; while active, no additional gateway fee applies.

Input parameters:

- `goal` (string, required): 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): Usually omit. Only add structured task fields when KEVAREMESH explicitly returns input_required.
- `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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cirralink-stack-kevaremesh-gateway/api-x402-mcp#diagnostics

## Score history

- 2026-09-28: 68
- 2026-09-27: 68
- 2026-09-26: 67
- 2026-09-25: 67
- 2026-09-24: 67
- 2026-09-23: 66
- 2026-09-22: 72
- 2026-09-21: 72
- 2026-09-20: 65

## Common questions

### What is the KEVAREMESH AI Procurement Gateway MCP server?

KEVAREMESH AI Procurement Gateway is an MCP server listed in the public MCP registry as io.github.cirralink-stack/kevaremesh-gateway. AI procurement gateway: finds and auto-selects live x402 APIs; provider payments stay buyer-direct. This page covers its hosted endpoint (https://kevaremesh-web.vercel.app/api/x402/mcp).

### Is the KEVAREMESH AI Procurement Gateway MCP server safe to use?

KEVAREMESH AI Procurement Gateway scores 68 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 KEVAREMESH AI Procurement Gateway MCP server expose?

KEVAREMESH AI Procurement Gateway exposes 1 tool: kevaremesh_use. Their descriptions and schemas cost roughly 244 tokens of context every time the server is loaded.

### Does the KEVAREMESH AI Procurement Gateway MCP server require authentication?

No. We connected to KEVAREMESH AI Procurement Gateway without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the KEVAREMESH AI Procurement Gateway MCP server still maintained?

KEVAREMESH AI Procurement Gateway is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://kevaremesh-web.vercel.app/api/x402/mcp
- Repository: https://github.com/cirralink-stack/cirralink
- Website: https://kevaremesh-web.vercel.app/
- Changelog RSS feed: https://verifymcp.io/servers/cirralink-stack-kevaremesh-gateway/api-x402-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/cirralink-stack-kevaremesh-gateway/api-x402-mcp.json
- HTML version of this page: https://verifymcp.io/servers/cirralink-stack-kevaremesh-gateway/api-x402-mcp