Home / MCP registry index / com.farmtempo/farmtempo

FarmTempo

com.farmtempo/farmtempo in the official MCP registry. Endpoint https://app.farmtempo.com/mcp/public/.

The registry describes it as: Korean produce wholesale reference prices, buy-or-wait signals and deal price checks with sources.

We read its 43 tools on 2026-11-18. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http farmtempo https://app.farmtempo.com/mcp/public/
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "farmtempo": {
      "url": "https://app.farmtempo.com/mcp/public/"
    }
  }
}
VS Code
code --add-mcp '{"name":"farmtempo","type":"http","url":"https://app.farmtempo.com/mcp/public/"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard
claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

mkt_create_rfq_draft mkt_search_rfqs mkt_search_listings market_list_items market_get_item onboard_roles onboard_stats region_list market_calendar market_ticker mkt_check_delivery items_list items_resolve items_get lots_reconcile usda_catalog usda_prices usda_latest usda_movement_catalog usda_movement usda_movement_summary usda_sp_catalog usda_sp_latest usda_sp_prices get_item_price_history get_weather_analysis_short_term get_weather_price_correlation get_current_weather_alerts compare_my_price_vs_wholesale get_seasonal_pattern get_wholesale_prices predict_demand_for_item calculate_margin calculate_margin_bulk get_auction_markets get_auction_price get_events_upcoming get_item_event_signal decide_buy_or_wait decide_buy_plan tempo_reference_items tempo_reference_price check_deal_price

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-18): 70961bda0345124b. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-farmtempo-farmtempo/badge.svg)](https://lazaretto.dev/mcp-registry/com-farmtempo-farmtempo)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.