Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

KEVAREMESH AI Procurement Gateway

REMOTE · KEVAREMESH-WEB.VERCEL.APP

AI procurement for web search, news, finance, blockchain, social, enrichment and travel APIs.

0 this week 62 Trust /100

Last scanned (14 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

Recent critical change

Authorization (23 Sept 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2261 tokens (~141/item across 16 items; 16 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 Management0
  • Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 16 additions. See how to fix → Fail
Tool Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 38% 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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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 →

Changelog

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 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “kevaremesh_retrieve_paid_api_result” rewrote its description, which is the text the model reads security
    • Schema quality: 2046 → 2261 ▼ functional
    • Server version: 0.12.3 → 0.12.4 functional
    • New tool “kevaremesh_find_or_build_api” functional
  • 10 Nov 26 0
    • Server version: 0.12.0 → 0.12.3 functional
    • New tool “kevaremesh_search_marketplace” functional
  • 9 Nov 26 0
    • Tool “kevaremesh_get_owned_input_contract” rewrote its description, which is the text the model reads security
  • 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
  • 31 Oct 26 −1
    • “kevaremesh_auto_use” added an optional parameter “request_id” cosmetic
    • “kevaremesh_use_infrastructure” added an optional parameter “request_id” cosmetic

    2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 30 Oct 26 +1
    • Tool “kevaremesh_auto_use” rewrote its description, which is the text the model reads security
    • “kevaremesh_auto_use” added an optional parameter “transaction_hash” cosmetic
  • 29 Oct 26 −16
    • Authorization: fail → unverified ▼ security
    • Stability: pass → fail ▼ security
    • Tool “kevaremesh_recover_owned_result” was removed ▼ security
    • Tool “kevaremesh_use” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • The server changed its declared name: kevaremesh-gateway → kevaremesh-agent-discovery security
    • Tool “kevaremesh_find_owned_api” rewrote its description, which is the text the model reads security
    • Tool “kevaremesh_locate_owned_receipt” rewrote its description, which is the text the model reads security
    • Tool coverage: 79% → 29% ▼ functional
    • Schema quality: 304 → 126 ▲ functional
    • Schema quality: excellent → good functional
    • Server version: 0.4.63 → 0.12.0 functional
    • New tool “kevaremesh_agent_commerce_status” functional
    • New tool “kevaremesh_auto_use” functional
    • New tool “kevaremesh_check_owned_receipt” functional
    • New tool “kevaremesh_discover_provider_candidates” functional
    • New tool “kevaremesh_get_owned_input_contract” functional
    • New tool “kevaremesh_preview_owned_api” functional
    • New tool “kevaremesh_quote_provider_batch” functional
    • New tool “kevaremesh_quote_provider_route” functional
    • New tool “kevaremesh_reconcile_gateway_receipt” functional
    • New tool “kevaremesh_retrieve_paid_api_result” functional
    • New tool “kevaremesh_route_intent” functional
    • New tool “kevaremesh_use_infrastructure” functional
    • “kevaremesh_find_owned_api” reworded the description of “query” cosmetic
    • “kevaremesh_locate_owned_receipt” reworded the description of “payment_signature_sha256” cosmetic
    • Tool “kevaremesh_find_owned_api” changed its title: Find KEVAREMESH original APIs and current real checkout availability (FREE) → Find owned KEVAREMESH APIs (current purchasability reported) cosmetic
    • Tool “kevaremesh_locate_owned_receipt” changed its title: Recover an already reserved owned-API receipt without paying again → Recover a missing paid order receipt ID from your own payment signature fingerprint cosmetic
  • 28 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
Diagnostics

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://kevaremesh-web.vercel.app/api/x402/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.vercel.app CN=WR1,O=Google Trust Services,C=US 31 Oct 2026 29 Jan 2027 RSA 2048 SHA256-RSA 9c5f0e6a35c955e113044c86848e4cd5
SANs: *.vercel.app
CN=WR1,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7fd9e2c2d2048a0474b627a26d0868a7
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of kevaremesh-web.vercel.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
vercel.app. 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=63072000; 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://kevaremesh-web.vercel.app/api/x402/mcp Verified 200
http (plaintext) http://kevaremesh-web.vercel.app/api/x402/mcp HTTPS enforced 308 https://kevaremesh-web.vercel.app/api/x402/mcp
MCP tools · 16 exposed · ~2,156 tokens

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 →

Tool Tokens
kevaremesh_agent_commerce_status ~49

Returns exact URL origins, verified payment-disable flags, historical 0.001 USDC route-fee model and explicit distinction between KEVAREMESH fees and upstream provider money.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

kevaremesh_auto_use ~369

AI FIRST: if the buyer's agent is pre-authorized for autonomous x402 spending, use this single MCP tool. No human checkout, approvals or manual invoice at KEVAREMESH. On first call return standard x402 MCP PaymentRequired; compatible payer automatically signs within its preconfigured budget and retries the SAME tool with _meta['x402/payment']. Merchant independently verifies and charges only the exact authorized payment. For owned APIs a paid result may require chain confirmations: use this same tool with receipt_id to resume automatically without paying again. For infrastructure buy and activate a 24h Access Pass automatically, then execute the requested operation; if confirmation is pending, resume with returned access_key and the same operation/input. If a facilitator receipt was lost, an independently observed Base transaction_hash may be supplied ONLY alongside an existing receipt_id or access_key for no-charge recovery. If buyer auto-payment is disabled, the buyer's client alone must obtain human authorization before signing. Buyer maintains keys and budgets; no seller-side custody, no repeated charge on uncertain receipts.

NameTypeReqDescription
access_keystring–For resuming an already-paid infrastructure pass; private bearer key, no new payment
inputobject–Original owned API input or live infrastructure operation input
kindstringyes–
operationstring––
receipt_idstring–For resuming an already-paid owned result; NEVER buy or sign again
request_idstring–Optional infrastructure operation idempotency key; reuse on retries. Omit for same-input cache per pass, or supply a new key to refresh.
slugstring––
transaction_hashstring–Optional Base transaction hash ONLY for recovering an existing receipt_id or access_key; independently verified, no new payment

No output schema declared.

No examples provided.

kevaremesh_check_owned_receipt ~99

Checks an existing UUID receipt and optionally reconciles a prior Base USDC payment using its real transaction hash if the facilitator response was lost. Never makes a purchase, signs, transfers, repeats a payment or calls an external paid provider.

NameTypeReqDescription
receipt_idstringyes–
reconcileboolean––
transaction_hashstring–Optional already-executed Base payment hash. Only with reconcile=true; never sends payment.

No output schema declared.

No examples provided.

kevaremesh_discover_provider_candidates ~90

Choose when an agent wants to search several candidate third-party APIs using one free metadata gateway, rather than individually browsing suppliers. Supply the explicit capability and search terms. Discovery returns unverified supplier names and prices, not authentication rights. No provider API is executed and no payment is made.

NameTypeReqDescription
capabilitystringyes–
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

kevaremesh_find_or_build_api ~170

Free first stop for an AI that needs an API, no seller approvals. Agent-first capability concierge: discover already-payable KEVAREMESH first-party tools and buyer-authorized x402 checkout, or instantly generate runnable source from vetted read-only Base blockchain RPC templates when no product matches. Source-only drafts require lawful production RPC, benchmark tests, security/cost review and independent demand before commercial release. No arbitrary code, deployment, auto-approval, marketing messages, payment or keys.

NameTypeReqDescription
goalstringyesDescribe the task; use this free first stop before buying or building.
include_sourceboolean–Include generated deployable but unhosted source for supported Base read-only API.
preferencestring–Three comparison strategies, independently evidenced before claiming any advantage.

No output schema declared.

No examples provided.

kevaremesh_find_owned_api ~100

Choose when an AI already knows a capability or product keyword and wants to find relevant KEVAREMESH-owned APIs and their original contracts. Discover prices, current real paid availability, input limits, and free preview links. For a natural-language job choose kevaremesh_route_intent instead. No purchase or execution occurs here.

NameTypeReqDescription
limitinteger––
querystringyesSearch words from capability, slug or module kind

No output schema declared.

No examples provided.

kevaremesh_get_owned_input_contract ~55

Free lookup of a catalog-listed first-party API's original input contract; preview is only available for locally approved algorithms. This is not a paid API execution contract or merchant authorization.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

kevaremesh_locate_owned_receipt ~123

If an authorized x402 payment was reserved but the network response containing its receipt UUID was lost, compute SHA-256 of the exact original Payment-Signature header locally and supply ONLY the 64-character hexadecimal fingerprint. This free lookup never accepts the raw signature, creates a charge, executes a paid API or contacts a payment facilitator. The fingerprint itself is private bearer material.

NameTypeReqDescription
payment_signature_sha256stringyesSHA-256 hex of the exact original raw Payment-Signature header. NEVER put the signed payment header itself in this field.

No output schema declared.

No examples provided.

kevaremesh_preview_owned_api ~96

After finding an owned API SKU, run its actual reviewed pure algorithm on the healthy replacement database. Limited to 21 no-network modules; other 3 are held. Preview is free, severely rate limited, has no wallet or paid entitlement, and does not imply a commercial release.

NameTypeReqDescription
argumentsobjectyesReviewed native API arguments. Total serialized request payload <= 4KiB.
slugstringyes–

No output schema declared.

No examples provided.

kevaremesh_quote_provider_batch ~90

Use when an AI agent needs one bounded, free comparison for 1–5 specified provider capabilities. Calls only KEVAREMESH Gateway /quote; no provider execution, credentials, wallet signature or payment. Candidate discovery never grants rights to use a provider.

NameTypeReqDescription
max_total_upstream_usdnumberyes–
preferencestring––
requirementsarrayyes–

No output schema declared.

No examples provided.

kevaremesh_quote_provider_route ~94

Choose when an agent wants a free price comparison for one named provider API capability within a strict price ceiling. Calls only the free KEVAREMESH Gateway quote. For 2–5 needs use kevaremesh_quote_provider_batch. Neither operation purchases upstream APIs or handles buyer funds.

NameTypeReqDescription
capabilitystringyes–
goalstringyes–
max_unit_price_usdnumberyes–

No output schema declared.

No examples provided.

kevaremesh_reconcile_gateway_receipt ~78

Given a gateway request ID and buyer-held finalize token, poll prior Base USDC settlement evidence. It may finalize a verified existing fee and return the associated paid route capability. Never signs, pays again, submits provider requests or creates routes.

NameTypeReqDescription
finalize_tokenstringyes–
gateway_request_idstringyes–

No output schema declared.

No examples provided.

kevaremesh_retrieve_paid_api_result ~85

One existing receipt completes automatic on-chain reconciliation when possible, then retrieves the original AES-GCM cached paid result in the same MCP tool call. If confirmation is pending, retry this receipt tool later without re-paying. Result cache lasts up to 24 hours. No new signature, payment, provider call or algorithm execution.

NameTypeReqDescription
receipt_idstringyes–

No output schema declared.

No examples provided.

kevaremesh_route_intent ~158

Choose first when an AI wants to solve a task such as CSV to JSON, Base64, URL parsing, JSON validation, hashing, UUIDs or timezone conversion, without knowing a product name. One request discovers matching existing KEVAREMESH tools, real input schemas where available, indicative prices and verified live checkout status. Optional supplier metadata is free, never a grant of third-party access. This discovery tool cannot pay or execute.

NameTypeReqDescription
capabilitystring––
goalstringyes–
include_input_contractsboolean–Inline the actual reviewed input schemas for at most two matching executable local APIs. Free metadata GET only.
include_provider_candidatesboolean––
limitinteger––

No output schema declared.

No examples provided.

kevaremesh_search_marketplace ~149

Unified free cross-directory search of KEVAREMESH-owned products, 11 rights-scoped executable external Hub operations, public x402 listings, an automatic official MCP registry index, and an MIT-licensed public API directory. Search listings are not supplier execution rights or verified payable quotes. Do not pay or proxy an external listing solely because it appears here. For runnable rights-scoped results use kevaremesh_use_infrastructure. For owned purchases use kevaremesh_auto_use with buyer-signed x402 authorization.

NameTypeReqDescription
limitinteger––
querystring–API function, goal, provider or operation keyword; empty lists available inventory.
sourcestring––

No output schema declared.

No examples provided.

kevaremesh_use_infrastructure ~351

One agent-facing entry to the rights-verified bounded external API catalog (Frankfurter, USGS, Crossref and ROR where currently enabled). Read the live catalog to discover available operations. Actions: catalog, execute, batch, resolve, pass_catalog and paid_execute. Free operations remain bounded. A buyer-authorized x402 24h Access Pass supports independently verified paid admission with capped immediate API execution; the MCP tool does not sign, buy, or move funds. It cannot perform purchases, send funds, forward arbitrary URLs or execute upstream fee-bearing APIs. The live catalog combines current first-party products and rights-eligible external operations when independent checks succeed; inventory counts are not hardcoded.

NameTypeReqDescription
access_keystring–For paid_execute only: the buyer-held 32-byte random access key from an independently confirmed x402 Access Pass. Treat as private; never expose in public logs or chat.
actionstring––
goalstring––
inputobject–For currency_rate: base/quote ISO codes; for currency_convert add amount; currency_history add date; USGS operations use empty object; Crossref DOI lookup requires doi, publication search requires qu…
jobsarray––
operationstring–Use an exact operation name returned by action=catalog. The hub enforces permitted operations, original inputs and per-provider rights before use.
request_idstring–Optional paid_execute logical invocation key. Reuse exactly on retries; a new key refreshes live data. Omission caches identical operation/input per pass.

No output schema declared.

No examples provided.

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.

remote · kevaremesh-web.vercel.app

# add to Claude Code
claude mcp add --transport http cirralink-stack-kevaremesh-gateway 'https://kevaremesh-web.vercel.app/api/x402/mcp'
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 for web search, news, finance, blockchain, social, enrichment and travel APIs. 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 62 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 16 tools: kevaremesh_search_marketplace, kevaremesh_use_infrastructure, kevaremesh_auto_use, kevaremesh_find_or_build_api, kevaremesh_route_intent, and 11 more. Their descriptions and schemas cost roughly 2,156 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 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 KEVAREMESH AI Procurement Gateway MCP server?

VerifyMCP ran 12 checks on KEVAREMESH AI Procurement Gateway, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about KEVAREMESH AI Procurement Gateway: Authorization. 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.