Home / MCP registry index / io.github.sean0007/free-agent-tools

Free Agent Tools

io.github.sean0007/free-agent-tools in the official MCP registry. Endpoint https://free-agent-tools.vercel.app/mcp. Source: github.com/sean0007/free-agent-tools.

The registry describes it as: 21 free no-auth tools: pitch roast, Kyushu discount, Japan visa fee, luggage, tax-free.

We read its 34 tools on 2026-10-30. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

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 every week.

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 free-agent-tools https://free-agent-tools.vercel.app/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "free-agent-tools": {
      "url": "https://free-agent-tools.vercel.app/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"free-agent-tools","type":"http","url":"https://free-agent-tools.vercel.app/mcp"}'

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 jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

score_business_idea_moat roast_pitch price_headroom_check thirty_day_cash_check email_list_reactivation_value hotel_ota_commission_calculator saas_self_host_savings list_open_source_saas_alternatives ads_policy_notice_risk_check app_store_wrapper_precheck faceless_youtube_reality_check ai_infrastructure_bottlenecks ai_bottleneck_quiz viral_attention_patterns viral_attention_quiz japan_trip_plan japan_trip_options japan_tax_free_refund_check japan_visa_fee_check japan_luggage_check kyushu_travel_discount_check japan_customs_allowance_check japan_tb_screening_check japan_dual_pricing_check japan_emergency_alert_decode japan_permanent_residency_check japan_international_postage_check japan_reentry_deadline_check japan_overseas_dependents_check japan_parttime_work_check japan_driving_check airbnb_house_rules_check japan_my_number_card_expiry_check japan_hsp_points_check

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-sean0007-free-agent-tools/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-sean0007-free-agent-tools)

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. What we found across the registry.

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