Circle Area: Area of circle.
ConnectorNo auth
650,553 tools. Updated 2026-10-14 10:52
"Circle" matching MCP tools:
- Circle Area: Area of circle.ConnectorNo auth
- Circle Arc Length: Length of circle arc.ConnectorNo auth
- Circle Arc Length: Length of circle arc.ConnectorNo auth
- Circle Sector Area: Area of circle sector.ConnectorNo auth
- Circle Sector Area: Area of circle sector.ConnectorNo auth
Matching MCP Servers
- FlicenseAqualityCmaintenanceEnables read-only access to Circle parental-control data, including family profiles and per-profile internet usage.4-
- AlicenseAqualityBmaintenanceEnables AI agents to search and retrieve opportunities from the Opportunities Circle catalog, including scholarships, fellowships, internships, grants, jobs, and more. Supports filtering by type, country, funding, and tags, with full details and official apply links.6MIT
Matching MCP Connectors
Authenticated MCP for a user's care circle: read CareEvents, list loved ones, inspect workspace.
Connect your AI agent to a private community for truth-seeking and philosophical discussion.
- Circle Circumference: Circle CircumferenceConnectorNo auth
- Circle Segment Area: Area of circle segment.ConnectorNo auth
- Circle Circumference: Circle CircumferenceConnectorNo auth
- Circle Segment Area: Area of circle segment.ConnectorNo auth
- Straight-line (great-circle) distance matrix from coordinates. FREE. Typical input {"points": [{"id": "depot", "lat": 51.5, "lon": -0.12}, {"id": "A", "lat": 51.52, "lon": -0.1}]} returns {"matrix": [[0, 2.6], [2.6, 0]], "unit": "km", "kind": "straight-line (haversine), not road distance"}. Use when you have no road matrix and a straight-line approximation is acceptable, or to sanity-check one. Not road routing: real driving distances are longer and the difference is not uniform. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "points must be a list of at least two <value> objects"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.ConnectorNo auth
- Set gamepad state via UHID (id=3). On first call, CREATE is sent automatically. lx/ly/rx/ry are u16 LE stick axes (0-65535, center=32767); lt/rt are u16 LE triggers (0-32767, 0=released). dpad is a u8 hat (1=N,2=NE,3=E,4=SE,5=S,6=SW,7=W,8=NW,0=center). buttons is a u16 LE bitmask. The pad presents as a DualShock 4, so the bit order is that controller's, NOT the browser Gamepad API order: bit0=X/square, bit1=A/cross, bit2=B/circle, bit3=Y/triangle, bit4=L1, bit5=R1, bit6=L2, bit7=R2, bit8=share/select, bit9=options/start, bit10=L3, bit11=R3, bit12=PS/guide, bit13=touchpad. Note the face buttons are rotated: square is bit0 and cross is bit1. Bits 14-15 have no effect. device_gamepad_state is the higher-level twin — W3C standard button/axis arrays plus a selectable controller profile, with the bit packing done for you. Prefer it unless you specifically need to send this exact raw report.ConnectorOAuth
- Computes where the sky is on a chosen date against where it was at somebody's birth: ten transiting bodies with longitude, sign, degree, speed and retrograde state, and EVERY ASPECT they make to the natal planets and angles — each with its orb, the orb allowed, the natal longitude measured against, and whether the contact is APPLYING or SEPARATING. Use it for what is transiting a chart, whether a transit is active on a date, a Saturn return, or whether a contact has perfected. DELEGATE THIS RATHER THAN DERIVING IT: it needs two full sets of ecliptic longitudes — the birth instant, requiring the historic UTC offset at that place on that date, and the target instant — then the angle between every pair taken the SHORT way round a 360-degree circle, about a hundred and fifty subtractions each with a wrap case. The output looks exactly like a real transit list; errors land in the middle rows where nobody checks, and a missed wrap at 0 Aries silently drops or invents whole contacts. REPRODUCE THE ORB CONVENTION FROM result.orbConvention — there is no fact of the matter about how close a transit must be to count, and an aspect list quoted without its orb is opinions presented as measurements. Here: 3 degrees for conjunction, opposition, trine and square, 2 for sextile, deliberately tighter than a natal chart's 8. Omit "time" if the birth time is unknown: the ascendant and midheaven are then left out ENTIRELY rather than cast for an arbitrary noon, because a transit to a noon-cast angle reads exactly like a real contact while meaning nothing. THE MOON IS INCLUDED where most software excludes it; THE LUNAR NODES ARE EXCLUDED. Significance is interpretation and is not computed here. CITATION: required. See server instructions.ConnectorNo auth
- 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.ConnectorNo auth
- List cadastral parcels in an area — the land plots themselves, NOT transactions. For deeds and prices in an area use search_by_area or search_by_polygon instead. To look up a parcel by an id prefix use search_parcels; to turn one address, coordinate or 'locality + number' into a parcel use resolve_parcel; for everything known about a single parcel use get_parcel_report. Name the area in one of five ways — at least one is required: - teryt: administrative code prefix at any level (2 digits = voivodeship, 4 = county, 6 = municipality, finer allowed); comma-separate several. Browse codes with list_locations. - location: a county or city NAME, resolved to its code. A name shared by two counties comes back as an error listing both, never as a guess. - bbox: "minLng,minLat,maxLng,maxLat" in WGS84. - lat + lng + radiusKm: a circle (all three together). - polygon: a GeoJSON Polygon, for a drawn shape. Pass it on its own. A bbox and a circle cannot be combined — together they would mean the overlap of a rectangle and a circle, which is rarely the question. Two shapes of answer, priced differently: - Default: the LIGHT list — parcel id, district and centre point per row, with no outline and no surface. 2 API tokens. Pages by cursor: when more parcels match, the answer hands you an opaque cursor to pass back as cursor=. - includeGeometry=true (needs a bbox), or a polygon: OUTLINES — the full GeoJSON polygon of each parcel. 5 API tokens, at most 100 parcels per call (50 by default), no paging. Truncation is the normal case on outlines, not an edge case. An area the size of a city holds far more parcels than one call returns, so an outline answer is usually marked TRUNCATED and the parcels in it are an arbitrary subset — not the first, nearest or largest. Never report a truncated answer as the parcel list of an area; ask for a smaller area instead. minArea / maxArea (m²) filter on the registered parcel surface without returning it. They need a narrow scope — a bbox, a circle, a location name, or a teryt of at least 4 digits (county level) — and are refused elsewhere with a message saying what to add. They are not available on the outline calls. Every row of the light list carries the street address held for that parcel, whether or not you asked about one, and says where it came from: a street on record, one we worked out for a parcel the record left without a street (shown with a note saying so), or — only when a buildingNumber search on the record came back empty — one read off an official address point that falls inside the parcel (also noted). A building number is only ever on record or from that address point, so a worked-out street never carries one. When a page comes back with a requested buildingNumber, it also carries a note on which of the two the number came from. If the street exists in the area but not with that number, the answer says so instead of the generic "no such street". Most rural parcels have no street at all — for those the way in is resolve_parcel with the precinct name and the parcel number, not a street. - street: matches whole words of the name, case- and accent-insensitively — 4 letters or digits minimum, 200 characters maximum. It is a NAME, not a pattern: % and _ match themselves. 'Górna' finds 'ulica Górna' and 'Górna 15' but not 'Podgórna', and a fragment like 'Marsza' finds nothing. Both sources are searched at once and a parcel found in both appears once, attributed to the record. Matching folds accents, so 'karmelicka' finds 'Karmelicka' — but it does NOT inflect: pass the name in the NOMINATIVE, because an inflected form like 'Karmelickiej' answers with an empty list. That empty page costs nothing (the tokens are refunded) and carries a suggestions block with close names to retry, so read the suggestions before you conclude anything about the data. - buildingNumber: needs street alongside it. Against the record the match is EXACT ('12A' does not find '12a'); RCN often records a compound or split number ('84/92'), so an exact '84' will not find '84/92'. When that comes back empty, the same street+number is tried against official address points instead — that match ignores case ('12a' finds '12A') but is still exact on the number, no compound splitting, and it matches the street by the same whole-word rule as above, not a fragment ('Waszyngtona' finds 'Aleja Waszyngtona', 'szyng' does not). Only when BOTH miss does the page come back empty (the tokens are refunded), listing the numbers held on the street as suggestions to retry. Both need a narrow scope for the same reason minArea does — a bbox, a circle, a teryt of at least 4 digits, or a location name — and neither counts as naming the area: a common street name across the country is a national search, not a question. Neither is available on the outline calls. Parcel identity is gated: parcel_id comes back for API-token / OAuth callers and for paid or active-trial accounts, and is withheld for everyone else while the location and the outline still come back. Coverage, so you can allow for it — TWO SEPARATE GAPS: 1. We hold near-complete coverage of the cadastral register, though not the whole of it and not live: what we hold was measured county by county on a fixed date, so a freshly split, merged or renumbered parcel may not be in yet. This applies to EVERY entrance here, teryt and location included. A short list, and the absence of a truncation marker, mean only that nothing further matched what we hold as of that measurement — never that you have every parcel in the area. Each answer carries a corpus_coverage block: for teryt and location it gives the measured parcels-held and parcels-in-register figures for the counties you asked about; for bbox, circle and polygon those figures are null, because sizing an arbitrary shape needs county boundaries we do not have — the measurement still applies, we just cannot put a number on it for that shape. 2. Separately, the spatial entrances (bbox, circle, polygon) work off the stored outline, and a small share of the parcels we DO hold keep theirs in a coordinate system those queries cannot read — those are missing from spatial answers specifically. The teryt and location entrances never touch geometry and are unaffected BY THAT SECOND GAP; a parcel whose outline we do not hold shows up there with no location. Neither gap is a reason to distrust what comes back: a returned parcel is a real parcel. They are a reason never to read an empty or short answer as evidence that the land is not there. Limits: an area over 500 km², a radius over 12.6 km (the same ground) or a polygon over 500 vertices is refused rather than scanned, and a query that outruns its time limit answers with an error asking you to narrow it.ConnectorOAuth
- Resize the ACTIVE page's canvas to width × height pixels. The composition is scaled UNIFORMLY to fit the new frame (a single factor s = min(newW/oldW, newH/oldH), so nothing distorts — a circle stays a circle) and then re-centred so the old composition centre maps to the new canvas centre. Every layer's position, size, group pivots, and x/y/width/height keyframes follow this fit+recentre; same-aspect resizes scale exactly, aspect changes letterbox the content centred. Each page owns its size, so this leaves sibling pages untouched — select_page then set_canvas_size again to resize another one. Common sizes: 1080×1920 (9:16 Reels/TikTok/Shorts), 1080×1350 (4:5 Instagram), 1080×1080 (1:1 square), 1920×1080 (16:9 YouTube).ConnectorDestructiveNo auth
- Search earthquakes by time range, magnitude, depth, location radius, PAGER alert level, or felt reports. Supports USGS (global, richer metadata: PAGER, DYFI, ShakeMap) and EMSC, an independent global catalog operated by the European-Mediterranean Seismological Centre. For location-based queries, provide latitude, longitude, and radius_km together. A rectangular study area is expressed with min_latitude, max_latitude, min_longitude, and max_longitude — each independently optional, so a single edge is a valid constraint. Combining the box with the lat/lon/radius circle intersects the two, returning only events inside both. Both catalogs include non-tectonic records (quarry blasts, explosions) — every event carries its event_type, and event_type="earthquake" filters the rest out on USGS. USGS-specific filters (alert_level, event_type, min_felt, min_significance) are not sent when source=emsc — the response names them in ignoredFilters. Use earthquake_count first to gauge result size before requesting large result sets. A single call returns at most 20,000 events; larger result sets are retrieved by paging with offset, which is passed straight through to the upstream FDSN API. When a result is capped, nextOffset carries the offset for the following page and totalCount the full match count — or countUnavailable reports that the count lookup failed and the total is unknown.ConnectorNo auth
- 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.ConnectorNo auth
- 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'.ConnectorNo auth
- [FREE] Read the onchain attestations naming an AI agent's wallet on Base, and what they are worth in SolvScore's underwriting. Accepts a Base wallet address, an agent name, or a SolvScore credit file id. Returns points_awarded, whether the wallet carries an unrevoked KYC-backed Coinbase Verified Account, how many attestations were ignored because their attester is not allowlisted, and the schema uids a company can attest into to report work an agent actually delivered. Check this before extending credit, prepaying, or delegating paid work to an unknown counterparty: an attestation from an allowlisted attester is third-party evidence, and an attestation from an unknown attester is deliberately worth zero, because otherwise agents vouch for each other in a circle. Identity opens a door; delivered work still earns the limit.ConnectorNo auth
- [FREE] Read the onchain attestations naming an AI agent's wallet on Base, and what they are worth to SolvScore's underwriting. Accepts an agent name, id, or Base wallet address. Returns points_awarded, whether the wallet carries an unrevoked KYC-backed Coinbase Verified Account, how many attestations were ignored because their attester is not allowlisted, and the EAS schema uids a company can attest into to report work an agent actually delivered. Check this before extending credit, prepaying, or delegating paid work to a stranger. An attestation from an allowlisted attester is third-party evidence; one from an unknown attester is deliberately worth zero, because otherwise agents vouch for each other in a circle. Identity opens a door, delivered work still earns the limit.ConnectorNo auth