Saltar al contenido
Logo de FlexYield

Servidor MCP de FlexYield

Qué servidores MCP son de FlexYield, del registro oficial y encontrados preguntando a su propio dominio, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-26

← Volver a FlexYield

De quién es el servidor
  • Nombre en el registroio.flexyield/gatewayverificado en el registro MCP

El nombre en el registro está bajo flexyield.io. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

Cuando le preguntamoscomprobado el 2026-10-26
  • Estadorespondecomprobado el 2026-10-26
  • Herramientas35
  • El servidor se llamaflexyield
  • Versión del servidor1.4.0
  • Versión del protocolo2025-06-18

El 2026-10-26 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 179 ms.

¿Debe un agente conectarlo?Aún no está claro
  • Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
  • Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

Una vez conectado

  • create_api_key, update_account cambian datos sin iniciar sesión: cualquiera con la dirección puede llamarlas.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

Medido cada díacomprobaciones diarias: 2, la primera el 2026-10-26
  • Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
  • Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
  • Mediana de la primera respuesta502 ms
  • Espacio en el contexto del agente≈ 8752 tokenslas definiciones de todas sus herramientas (35), que el agente lleva en cada turno
  • Definiciones de herramientasA · 98 de 100
  • Resultados tipados0 de 35 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez
  • Parámetros sin descripción: en 4 de 35

Qué puede hacer un agente con él

  • puede · route JSON-RPC calls through one endpoint to several providers
  • no está claro · fail over to healthy providers when one goes down
  • no está claro · consolidate provider keys and invoices into one bill

Cada caso de uso del producto se le preguntó a Jev junto con la lista de herramientas de este servidor: ¿puede un agente hacerlo con estas herramientas?

Conviene revisar

  • Herramientas que cambian datos, en un servidor que responde sin iniciar sesión: create_api_key, update_account

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

Herramientas que ofrece35 herramientas · leído el 2026-10-26
  • get_key

    Get a FlexYield API key with no signup: public supply, 10,000 weighted units per UTC day, 5 requests/s, every tool. Use it once, when you have no key yet; then send the key as the bearer on every other call. Not for a key you already hold…

  • bind_key_start

    Step 1 of binding the API key you are calling with to a wallet: returns the exact SIWE (EIP-4361) message that wallet must sign. Use it when your key came from get_key and you want it to persist across sessions with 1M units/month. Not…

  • bind_key_complete

    Step 2 of binding the API key you are calling with to a wallet: pass the wallet's signature over the message from bind_key_start. Use it right after bind_key_start, with the same key. Not for the first step (use bind_key_start) and not…

  • claim_agent_start

    Step 1 of claiming an agent by its EVM address for the account you are calling with: returns the exact SIWE message the agent's wallet must sign. Use it when an account owner wants a budgeted key for an agent that proves control of a…

  • claim_agent_complete

    Step 2 of claiming an agent: verify the wallet's signature over the message from claim_agent_start and equip the agent with its own budgeted API key (default 50000 requests/month). Use it right after claim_agent_start. Not for the first…

  • create_api_key

    Create an additional API key on the account you are calling with (a name, optional monthly unit cap). Use it to give a service or a teammate its own key with its own budget. Not for your first key (use get_key, no signup) and not for a…

  • configure_key

    Configure one API key of your account by id: monthly_request_cap (a monthly unit budget; omitted = unchanged, 0 = remove the cap), enabled (the list of services it may use: rpc, data, gas, tx_status, ens, prices, contracts, utils) and…

  • revoke_api_key

    Revoke one API key of your account by id; calls with that key stop working immediately and the key cannot be restored. Use it when a key leaked or a service is retired; ids come from list_api_keys. Not for pausing a key (set its budget to…

  • list_api_keys

    List the API keys of your account (scope='keys', default) or its agent fleet with wallet claims and budgets (scope='agents'). Use it to find a key id before configure_key or revoke_api_key, or to see which keys are in use. Not for usage…

  • get_billing_status

    Billing state of your account: tier, whether payments are live, the subscription (plan, interval, price in USD cents, status, period end, cancel-at-period-end), the card on file (brand, last4, expiry — never the number), prepaid pack…

  • configure_services

    Read or change the account-wide service settings: which gateway services (rpc, data, gas, tx_status, ens, prices, contracts, utils) are enabled and an optional monthly unit cap per service. Use it with no arguments to read; pass enabled…

  • update_account

    Update your account's preferences: notifications (notify_incidents, time_zone) and/or the insights that tailor the service (use_case, team_size, volume, region, previous_provider, referral_source, chains, wish_chains, wish_chain_other)…

  • join_enterprise_wishlist

    Send FlexYield an enterprise wishlist: what would need to be true for you to run on FlexYield (chains, SLAs, compliance, features, prices; max 1000 chars) plus a contact email; the founders reply by email. Use it when the public plans do…

  • join_waitlist

    Join the FlexYield early-access waitlist with an email and a qualifier (developer, investor or curious). Use it only when a human asked to be kept informed; an agent that needs access now should call get_key instead. Not for support (use…

  • list_plans

    List FlexYield's public plans: price in integer USD cents, billing interval, monthly included units and burst rate limits, plus the enterprise line and the signup URL. Use it to compare plans or before telling an owner what an upgrade…

  • get_usage

    Your account's usage in one of three views. view='report': requests, weighted units, errors and latency per key, method and chain over a look-back window (hours, default 24; optional chain). view='stats': one console report…

  • get_statement

    Your account's statement for one billing period (default: the current one): invoice facts plus usage grouped by API key or agent, chain and method class — requests, weighted units, cache hits, refusals; period='list' enumerates the…

  • manage_tickets

    Your support tickets with FlexYield. action='create' (subject, message, optional request_id of the failing call, optional category) opens a ticket with the call's evidence attached; action='list' (optional status); action='get'…

  • manage_feedback

    Product feedback to FlexYield. action='submit' (kind: 'feature' | 'chain' | 'praise' | 'complaint' | 'other', title, optional body, optional chain) files it and we answer on the feedback page; action='list' (optional status) shows what…

  • get_balances

    Native balance and ERC-20 token balances of an address on one chain (eth_mainnet, base_mainnet, arbitrum_one, optimism_mainnet, polygon_pos, solana_mainnet; tokens where a data-capable upstream exists). Use it for a portfolio or a…

  • get_history

    Recent asset transfers (sent and received, newest first) of an address on one EVM chain with a data-capable upstream. Use it to answer 'what moved in or out of this address lately'. Not for current balances (use get_balances), one…

  • get_prices

    Prices. kind='gas' (chain): EIP-1559 gas recommendations (slow/standard/fast) computed from our pool on an EVM chain, 1 weighted unit. kind='token' (symbols, comma-separated e.g. 'ETH,USDC'): current token prices in USD. Use it before…

  • get_tx_status

    Status of one transaction hash on any supported chain: confirmed, failed, pending or unknown, with confirmations and gas on EVM chains or slot and commitment on Solana. Use it to poll a transaction you sent or were told about. Not for an…

  • resolve_ens

    ENS resolution on Ethereum mainnet: pass a name ('vitalik.eth') to get its address, or an address (0x…) to get its reverse-record name, read on-chain through our pool. Use it whenever a user gives you a .eth name instead of an address…

  • get_abi

    The verified ABI of a contract (with its name and match level) from Sourcify's open dataset on eth_mainnet, base_mainnet, arbitrum_one, optimism_mainnet or polygon_pos. Use it before calling or decoding a contract you do not have the ABI…

  • decode_calldata

    Decode a transaction's calldata against the target contract's verified ABI (Sourcify): the function signature, its selector and the argument values (static types decoded; dynamic types shown raw and labelled). Use it to explain what a…

  • convert_evm

    Offline EVM utilities, no chain call: op='checksum' (EIP-55 checksum and validity of input=address), op='convert' (unit conversion wei…gwei…eth: input=value, from=unit, to=unit), op='selector' (4-byte selector and topic0 of input=function…

  • verify_signature

    Verify a signature offline: mode='personal' checks an EIP-191 personal_sign signature (message, 65-byte 0x signature, optional expected address); mode='siwe' checks a SIWE / EIP-4361 message (the exact signed text plus signature — parses…

  • what_can_i_do

    The status overview of the API key you are calling with: its door (how it was obtained: public via get_key, wallet-bound, or adopted by a paying owner), its tier, the budgets left (month, day, prepaid packs), the fences (its limits) each…

  • get_quote

    Quote one JSON-RPC call before making it: the weighted units it costs (standard 1, heavy 2, or not offered) and the USD per 1M units on every lane (a lane = a price tier: cheap, balanced, fast). Use it when an owner asks what a workload…

  • explain_error

    Explain a FlexYield error code (e.g. -32007): what it means, the steps to take and its doorway (the path past the limit that caused it). Use it whenever a call returned an error with a code you do not know, before retrying or filing a…

  • recommend

    A recommendation from our live measurements. what='chain': which chain fits a task (optional family, candidates, prefer), ranked from our probes and method rules. what='route': which lane (price tier: cheap, balanced, fast) to use for one…

  • migrate

    A compatibility report for switching your RPC provider to FlexYield: paste your current config as text (endpoint URLs, env lines, code) and get every endpoint mapped to our chain URL, every JSON-RPC method you name with its unit weight…

  • buy_pack

    Start the purchase of a prepaid unit pack (size 's': 1.2M units $10, 'm': 7M $50, 'l': 32M $200, +5 % units when bought here) and get a checkout URL the account owner completes on a card; units become available when the payment lands, are…

  • rpc_call

    Send one JSON-RPC call through the FlexYield gateway — the same routing, failover, cache and meter as POST /rpc/{chain}. chain: 'eth_mainnet' | 'base_mainnet' | 'arbitrum_one' | 'optimism_mainnet' | 'polygon_pos' | 'solana_mainnet'…

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

{
  "mcpServers": {
    "gateway": {
      "type": "http",
      "url": "https://flexyield.io/mcp"
    }
  }
}

Añadirlo

Claude Code, en una terminal

claude mcp add --transport http flexyield https://flexyield.io/mcp

Añadir a CursorAñadir a VS Code

claude.ai, ChatGPT y otros clientes: añade https://flexyield.io/mcp como conector personalizado en los ajustes.

Especificación OpenAPI

18 rutas, leído el 2026-10-26. Abrir la especificación ↗

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.