← flexyield.io

INDIVIDUAL MCP TOOL

manage_feedback

Product feedback to FlexYield.

flexyield.ionone authenticationAvailability not checked

LIVE ENDPOINT

https://flexyield.io/mcp

No auth detected

Connect to this endpoint to inspect the live schema for manage_feedback and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

flexyield.io

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.flexyield]
url = "https://flexyield.io/mcp"
enabled = true
Claude Code

.mcp.json

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

Settings → Connectors → Add custom connector

Name: flexyield
Remote MCP URL: https://flexyield.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "flexyield": {
      "url": "https://flexyield.io/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "flexyield": {
      "type": "http",
      "url": "https://flexyield.io/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "flexyield",
  "transport": "streamable-http",
  "url": "https://flexyield.io/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • get_key — Get a FlexYield API key with no signup: public supply, 10,000 weighted units per UTC day, 5 requests/s, every tool.
  • 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.
  • 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.
  • 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.
  • 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).
  • create_api_key — Create an additional API key on the account you are calling with (a name, optional monthly unit cap).
  • 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 caps ({service_key: units} per service).
  • 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.