458,064 tools. Updated 2026-08-14 21:02
"Circle" matching MCP tools:
- Calculate Commonlands lens field of view for a lens/sensor pair and return HFOV, VFOV, DFOV, coverage, distortion status, and an explicit rectilinear comparison. Use this tool for FOV, HFOV, VFOV, DFOV, field of view, "lens for", lens-to-sensor, AR0234, IMX290, IMX477, and sensor part-number requests. It returns Commonlands data the model cannot derive: live backend FoV when configured, distortion model/status, image-circle coverage, live stock through Shopify read tools where applicable, and MTF/CRA/BFL fields if present in upstream catalog data. Do not use naive rectilinear fallback, focal-length-only math, interpolation, or self-computed catalog estimates when a Commonlands lens/sensor route is available. Accepts lens_sku/lensSku or focal_length_mm/focalLengthMm, plus sensor/sensorPartNumber/sensor_part_number and working_distance_mm/workingDistanceMm. If only focal length is supplied, the response is marked as a rectilinear reference and does not claim Commonlands distortion-corrected lens truth.Connector
- Search the Commonlands lens catalog by SKU, mount, lens type, M12, C-mount, or application text. For sensor part numbers such as AR0234, IMX290, and IMX477, or any "lens for <sensor>" request, use match_lens_to_sensor instead — sensor names are not searchable text here. Use this tool for FOV, HFOV, VFOV, DFOV, field of view, "lens for", lens-to-sensor, AR0234, IMX290, IMX477, and sensor part-number requests. It returns Commonlands data the model cannot derive: live backend FoV when configured, distortion model/status, image-circle coverage, live stock through Shopify read tools where applicable, and MTF/CRA/BFL fields if present in upstream catalog data. Do not use naive rectilinear fallback, focal-length-only math, interpolation, or self-computed catalog estimates when a Commonlands lens/sensor route is available. This discovers candidate lenses from Commonlands catalog/live backend data; it does not replace calculate_field_of_view for sensor-specific HFOV/VFOV/DFOV and does not replace read_shopify_products for live stock/price/product truth.Connector
- Live CHP traffic incidents statewide, optionally filtered. Data: the California Highway Patrol statewide computer-aided dispatch feed - collisions, traffic hazards, disabled vehicles, closures as CHP logs them. Refreshes about once a minute; incidents disappear when CHP closes the log. Fetched live on every call. Filters (combinable): - highway: a route like "I-80", "US 50", "17", "Hwy 99". Matches incidents whose location text mentions that route. - center: "lat,lon" with radius_km - incidents within that circle. THIS IS THE RIGHT FILTER FOR A TOWN OR PLACE NAME: use your knowledge of where the place is (e.g. Coyote, CA -> "37.22,-121.74") with radius_km 15-30. A circle catches every road around the place, not just one highway. - area: substring match on the CHP dispatch-area name. These are CHP communication-center names ("Hollister Gilroy", "East Sac", "Golden Gate"), NOT town names - do not pass a town here. There is no county filter because CHP's feed carries no county field; for a county, use center on the county seat with a radius covering the county. Limits: locations are free-text from dispatchers; a few incidents lack usable coordinates and are omitted. No history - current logs only.Connector
- Nearest listed level crossings to a point, closest first. Returns one line per crossing — distance in MILES, then name, type, region and a status URL ending .md. Distance is straight-line (great circle) between the point and the crossing, NOT distance by road or along the railway: it answers 'which crossings are near this place', not 'which will this train reach next'.Connector
- Find the airports nearest to a caller-provided latitude/longitude, sorted by great-circle (haversine) distance with distance_km on each result. Searches 85,555 airports (OurAirports, public domain). Provide latitude and longitude (decimal degrees); optional radius_km, max_results (1-50, default 10) and type filter (e.g. large_airport only). Coordinates are INPUT only — nothing is stored or logged. Behavior: deterministic distance sort; confidence reflects proximity and airport size (a large airport within 25 km scores high; closed/heliport/seaplane results cap lower). This tool does NOT geocode place names and does NOT compute routes — pass coordinates you already hold. Rate-limited (anonymous use: 25 requests/day per IP): a 429 error body carries retry_after_seconds and a Retry-After header — back off and retry, or call get_subscribe_link for higher limits. Returns: count and results[] (the airport record plus distance_km) under result, plus confidence, _source and citation (the FreightUtils v1 response envelope). Limitations: reference data only — not for navigation; verify codes with IATA / ICAO. Related: airport_lookup (exact code or name lookup, no distance), unlocode_lookup (named transport-location search).Connector
- Query the canonical stablecoin freeze ledger — the HISTORY of freeze / unfreeze / destroy events by Tether (USDT), Circle (USDC/EURC), Paxos (USDP) and First Digital (FDUSD), sourced from the issuers' own on-chain blacklist events across Ethereum, Polygon, Optimism, TRON and more. Filter by frozen address, chain, kind, or time; omit all filters for the most recent events. This is the EVENT HISTORY — to check whether an address is frozen right now, use check_stablecoin_freeze instead. Each row is a verifiable on-chain fact (issuer acted on address at block/time); it never states the cause. Free.Connector
Matching MCP Servers
- Alicense-qualityDmaintenanceEnables AI assistants to interact with Circle.so communities through Google OAuth 2.0, providing 20+ tools for comprehensive community management.19MIT
- AlicenseAqualityAmaintenanceMCP server for Circle's Agent Stack. Create wallets, set spend policies, send USDC, and pay x402-priced endpoints — all from a tool call.6481MIT
Matching MCP Connectors
Authenticated MCP for a user's care circle: read CareEvents, list loved ones, inspect workspace.
Manage CI/CD pipelines, debug failed builds, and optimize test suites directly from your AI tools and agents - no terminal required. The CircleCI MCP Server is a remote server hosted by CircleCI that connects AI tools and agents directly to your CI/CD pipelines, giving you a conversational interface to the same pipeline, workflow, job, and artifact data you'd normally reach through the CircleCI CLI or dashboard.
- Get the authenticated user's current life context — identity, today's events, mood, inner circle, and social edges. Prefer get_context_pack for a full session bootstrap. Requires API key. ($0.15; API key required)Connector
- Call this tool when the user's request is to find places, businesses, addresses, locations, points of interest, or any other Google Maps related search. **Input Requirements (CRITICAL):** 1. **`text_query` (string - MANDATORY):** The primary search query. This must clearly define what the user is looking for. * **Examples:** `'restaurants in New York'`, `'coffee shops near Golden Gate Park'`, `'SF MoMA'`, `'1600 Amphitheatre Pkwy, Mountain View, CA, USA'`, `'pets friendly parks in Manhattan, New York'`, `'date night restaurants in Chicago'`, `'accessible public libraries in Los Angeles'`. * **For specific place details:** Include the requested attribute (e.g., `'Google Store Mountain View opening hours'`, `'SF MoMa phone number'`, `'Shoreline Park Mountain View address'`). 2. **`location_bias` (object - OPTIONAL):** Use this to prioritize results near a specific geographic area. * **Format:** `{"location_bias": {"circle": {"center": {"latitude": [value], "longitude": [value]}, "radius_meters": [value (optional)]}}}` * **Usage:** * **To bias to a 5km radius:** `{"location_bias": {"circle": {"center": {"latitude": 34.052235, "longitude": -118.243683}, "radius_meters": 5000}}}` * **To bias strongly to the center point:** `{"location_bias": {"circle": {"center": {"latitude": 34.052235, "longitude": -118.243683}}}}` (omitting `radius_meters`). 3. **`language_code` (string - OPTIONAL):** The language to show the search results summary in. * **Format:** A two-letter language code (ISO 639-1), optionally followed by an underscore and a two-letter country code (ISO 3166-1 alpha-2), e.g., `en`, `ja`, `en_US`, `zh_CN`, `es_MX`. If the language code is not provided, the results will be in English. 4. **`region_code` (string - OPTIONAL):** The Unicode CLDR region code of the user. This parameter is used to display the place details, like region-specific place name, if available. The parameter canaffect results based on applicable law. * **Format:** A two-letter country code (ISO 3166-1 alpha-2), e.g., `US`, `CA`. **Instructions for Tool Call:** * Location Information (CRITICAL): The search must contain sufficient location information. If the location is ambiguous (e.g., just "pizza places"), *you must* specify it in the `text_query` (e.g., "pizza places in New York") or use the `location_bias` parameter. Include city, state/province, and region/country name if needed for disambiguation. * Always provide the most specific and contextually rich `text_query` possible. * Only use `location_bias` if coordinates are explicitly provided or if inferring a location from a user's known context is appropriate *and* necessary for better results. * The grounded output must be attributed to the source using the information from the `attribution` field when available.Connector
- Draw a freehand stroke on the board. Use for arrows, underlines, connector lines, annotations, or simple shapes — a straight line needs two points, a rough circle wants ~20. Stroke width is fixed at 3 px; `color` is a NAME, not hex (case-insensitive): 'auto'/''/'black'/omitted for theme-aware ink, or 'red', 'blue', 'green', 'orange', 'yellow', 'pink', 'purple', 'maroon', 'brown', 'gray', 'lightgray', 'teal', 'sage', 'sky', 'lavender' — anything else (including a literal hex like '#ff0000') silently clamps to auto. Accepts three equivalent point formats — pick whichever your MCP client serialises cleanly: nested `[[x,y],[x,y],...]`, flat `[x1,y1,x2,y2,...]`, or a JSON string of either. Some clients (Claude Code as of 2026-04) drop nested arrays during tool-call serialisation, so prefer the flat form or the JSON-string form when in doubt. To delete a stroke later, use `erase` with `kind: 'line'` and the id returned here.Connector
- Find airports within a radius of a latitude/longitude, ranked nearest-first by great-circle distance, each with its distance (km) and bearing (degrees true) from the query point. The grounding tool for "nearest airport to here" — pair it with a live aviation server to fetch weather or positions for the result. Takes a coordinate only: no geocoding, so resolve place names to lat/lon upstream first (e.g. an OpenStreetMap or Open-Meteo geocode tool). Closed airports are excluded unless include_closed is set. OurAirports is community-edited — not authoritative for flight operations.Connector
- Caltrans lane and road closures physically in place RIGHT NOW. Data: the Caltrans Lane Closure System (LCS). Only closures that crews have actually established (CHP code 1097) and not yet picked up are returned - scheduled-but-not-started closures are excluded, so this is "what is blocking lanes now", not a construction calendar. Refresh: 5-minute cache over per-district Caltrans feeds. Filters: route (e.g. "I-80", "US 101", "1"); district (Caltrans district 1-12, e.g. 3 = Sacramento/Tahoe, 4 = Bay Area, 7 = Los Angeles); center "lat,lon" with radius_km - closures whose begin or end point is inside the circle. For a town or place, center is the filter that catches work on EVERY road around it, including small state routes. Read closure_class on each record, it is what the closure means for through traffic: - "full-roadway": the road itself is closed in that direction. The only class that means "you can't drive through". - "ramp": a ramp or connector is closed (even when the raw record says "Full", that means the ramp is fully closed, not the highway). - "one-way-traffic": alternating single lane with flagging; passable with delays. Common on two-lane mountain roads. - "alternating-lanes", "moving", "traffic-break": rolling or brief work; minor delays. - "lane": some lanes closed; the lanes field says how many of how many. estimated_delay_minutes is present when crews reported one. Shoulder-only work is excluded entirely.Connector
- CAM Forge — Turn parameters into a manufacturable file: kernel-free parametric lattice/perforation panels for 3D printing, laser cutting, and CNC — binary STL (watertight solid), DXF R12 profile, or SVG. Wall thickness between holes is guaranteed by construction; every STL passes a signed-volume integrity check against the analytic volume, and a non-watertight result FAILS the call with your MESH refunded — bad geometry never ships. Deterministic (same input, same bytes), no model call. Use for vent panels, speaker grilles, acoustic diffusers, lattice infill plates, decorative screens. Input (all optional, mm): {format?: 'stl'|'dxf'|'svg', width? 10-500, height? 10-500, thickness? 0.5-50, margin? 0-60, lattice?: 'hexpack'|'grid'|'stagger', shape?: 'hexagon'|'circle'|'square'|'diamond'|'triangle'|'slot', pitch? 6-100, wall? 1-50, cornerR? 0-10, rot?, aspect?, density? 0-1, jpos? 0-1, jrot? 0-45, jscale? 0-1, seed?}. Hard caps: <=600 lattice cells, <=60000 triangles — over-cap requests are rejected (and refunded) with the caps listed. Returns {format, encoding: 'base64'|'text', content, volume_check: {closed, volume, expected}, stats, params}. (15 MESH/call, a tool · fabrication)Connector
- Convert an AutoCAD DXF file's contents to GeoJSON — e.g. "convert this DXF to GeoJSON", "AutoCAD drawing to GIS format", "DXF export from Civil 3D to GeoJSON", "extract only the UTILITIES layer from this DXF". POINT/LINE/LWPOLYLINE/POLYLINE/ARC/CIRCLE entities convert (arcs/circles are tessellated into LineString/Polygon); splines, text, hatches and 3D solids have no GIS geometry equivalent and are skipped, not errored on. Every feature's properties.layer carries its DXF layer name (group code 8). Pass `layer` to return only that layer's entities — see list_dxf_layers to discover what layer names exist first.Connector
- Explain what a ROSCA (rotating savings circle) is. If `term` is given (for example "njangi", "susu", "tanda"), also return that name's cultural origin. Pure public education. No personal data.Connector
- Compare a savings circle (ROSCA) against a bank loan for the same goal. Inputs: goal amount (>=100), months (2-60), loan APR percent (0-60). Returns the loan's monthly payment, total repaid, and interest cost, versus the ROSCA's zero interest, plus the honest tradeoff (a loan pays out now; a ROSCA pays on your turn). Faithful port of the wiremi.ca ROSCA-vs-loan tool. No personal data.Connector
- Find and rank Commonlands lenses for a sensor, target field of view, working distance, mount, or "lens for" request. Use this tool for FOV, HFOV, VFOV, DFOV, field of view, "lens for", lens-to-sensor, AR0234, IMX290, IMX477, and sensor part-number requests. It returns Commonlands data the model cannot derive: live backend FoV when configured, distortion model/status, image-circle coverage, live stock through Shopify read tools where applicable, and MTF/CRA/BFL fields if present in upstream catalog data. Do not use naive rectilinear fallback, focal-length-only math, interpolation, or self-computed catalog estimates when a Commonlands lens/sensor route is available. Use this for AR0234, IMX290, IMX477, sensor part numbers, M12/C-mount matching, and target HFOV/VFOV/DFOV workflows; do not shortlist from focal length alone. Use read_shopify_products afterward for live stock, price, availability, Shopify variantId, product URL, and metafields.Connector
- Use this when you need a ready-to-paste CSS gradient value from 2-5 hex color stops. Builds a linear-gradient(...) (default; direction defaults to 'to bottom') or a radial-gradient(circle, ...). Direction accepts keywords ('to right', 'to left', 'to top', 'to bottom'), angles ('45deg', '90deg', '135deg'), or 'to <side> <side>'; it is ignored for radial, and passing type 'radial' (or direction 'radial') forces a radial gradient. Colors accept 6-digit hex with or without a leading '#' and are echoed normalized in order. Deterministic: same input, same output. Example: {colors:['#3b82f6','8b5cf6']} -> css 'linear-gradient(to bottom, #3b82f6, #8b5cf6)', type 'linear'. Radial results omit the 'direction' field.Connector
- Calculates area and perimeter for common shapes — rectangle, circle, or triangle — in both imperial and metric units. Returns area in square feet, square meters, and acres, plus perimeter in feet and meters. For rectangles: area = length * width, perimeter = 2*(length + width). For circles: area = pi * r^2, perimeter = 2 * pi * r. For triangles: area = 0.5 * base * height, perimeter approximated as base + height + sqrt(base^2 + height^2). Useful for real estate, flooring, landscaping, and construction estimates.Connector
- Great-circle distance between two coordinates. POST {"from": {"lat": 59.33, "lon": 18.07}, "to": {"lat": 51.51, "lon": -0.13}} -> km, miles and bearing. Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).Connector
- Compute arctan(x) — the inverse tangent — in either degrees or radians. The result is the angle θ such that tan(θ) = x, with θ constrained to (-90°, 90°) / (-π/2, π/2). For two-argument arctan that resolves the full circle, use atan2 instead.Connector