postal_code_lookup — tollbooth MCP Tool
postal_code_lookup
(postal code lookup) is one of 104 tools on the
tollbooth
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call postal_code_lookup from your client
- Claude Code tollbooth postal_code_lookup run in your project directory
- Claude Desktop tollbooth postal_code_lookup ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor tollbooth postal_code_lookup ~/.cursor/mcp.json
- VS Code tollbooth postal_code_lookup .vscode/mcp.json
- Zed tollbooth postal_code_lookup ~/.config/zed/settings.json
- Windsurf tollbooth postal_code_lookup ~/.codeium/windsurf/mcp_config.json
- Cline tollbooth postal_code_lookup ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI tollbooth postal_code_lookup ~/.gemini/settings.json
- Grok tollbooth postal_code_lookup .mcp.json (in your project root)
- ChatGPT tollbooth postal_code_lookup Settings → Connectors → Advanced → Developer mode
- Claude.ai tollbooth postal_code_lookup Settings → Connectors → Add custom connector
- LangChain tollbooth postal_code_lookup pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http tollbooth https://agenttoll.dev/mcpOther tools on this server
- ping
- scrape
- detect_stack
- extract_contacts
- score_lead
- check_agent_policy
- find_agent_resource
- validate_agent_manifest
- enrich_lead
- x402_market_radar
- x402_rank_audit
- mcp_safety_brief
- x402_seller_readiness_audit
- mcp_approval_pack
- insider_cluster_brief
- gov_contract_fit_brief
- regulatory_impact_brief
- polymarket_event_scan
- polymarket_market_scan
- cross_platform_arb_scan
- agent_threat_intel
- mcp_supply_chain_iocs
- agent_trifecta_score
- agent_security_policies
- geo_pulse
- flight_intel
- research_pack
- scenario_verdict
- weather_bias
- supply_stress
- regulatory_pulse
- attention_momentum
- sec_8k_velocity
- fred_surprises
- treasury_dts
- openrouter_models
- github_trending
- hn_frontpage
- usgs_quake
- openaq_air
- court_opinions
- court_docket
- federal_register
- patents_search
- regulations_search
- search_papers
- search_arxiv
- search_pubmed
- clinical_trials
- search_openalex
- drug_recalls
- adverse_events
- product_recalls
- vehicle_recalls
- drug_labels
- wildfires
- weather_alerts
- tide_data
- space_weather
- water_levels
- federal_spending
- national_debt
- federal_grants
- nonprofit_filings
- economic_indicators
- lobbying_records
- edgar_filings
- insider_trades
- token_stock_quote
- fred_series
- combinatorial_arb
- orderbook_imbalance
- smart_money
- cve_search
- company_registry
- reddit_search
- github_repo_intel
- currency_rates
- business_days
- judges_search
- trademarks_search
- disease_outbreaks
- food_safety
- federal_contracts
- paper_details
- citation_graph
- gen_video_intel
- model_settings_lookup
- space_weather_kp
- weather_forecast_grid
- weather_current_global
- aurora_forecast
- marine_conditions
- air_quality_index
- ip_geolocation
- timezone_current
- airport_status
- dns_records_lookup
- isbn_book_lookup
- crypto_price_simple
- btc_address_balance
- btc_mempool_fees
- food_recall_check
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.