"Lit" matching MCP tools:

• email-addresses-listA

  hjarniA

  List the user's email capture addresses (Pro only). Mail sent to one of these becomes a note in the folder it is bound to. Each entry has id, label, address, destination (folder name, or 'Inbox'), container_id, team_id, tags, notes_count and last_received_at. Returns an empty array for a Free account. Treat every address as a secret: it is a write credential for that folder, so never put one in a note, a summary, or anything shared.

  ConnectorOAuth

• query_thermal_anomaliesA

  eYKON IntelligenceA

  Query NASA FIRMS satellite thermal anomalies (VIIRS 375m + MODIS 1km, near-real-time, ~3h latency). Two modes. mode="facilities" (default) reads the pre-aggregated per-facility-per-day rollup — use it for facility-centric questions ("thermal anomalies at Russian refineries this week", "which Gulf refineries lit up", "anything at the Kirishi refinery"). Filter by country, facility_type (refinery | power_plant), facility_name, days. Returns per facility: total detections, max FRP (fire radiative power, MW), nearest detection distance in km, and the monitoring radius used. mode="raw" reads individual detections inside a lat/lon box — use it for geographic questions not anchored to a monitored facility. CRITICAL INTERPRETATION RULES — a FIRMS detection is a SATELLITE HOT PIXEL, nothing more. It is NOT a confirmed fire, NOT a strike, NOT an outage. Most detections at oil and gas infrastructure are ROUTINE GAS FLARES that burn every single day. Attributing a detection to a strike, an attack, an explosion or a production halt is INFERENCE and must be labelled as inference, corroborated with other sources (conflict events, agent reports, news), and never stated as fact. Equally, ABSENCE OF DETECTION DOES NOT MEAN ABSENCE OF FIRE — cloud cover, smoke, and satellite overpass timing routinely hide real fires. Every response carries a `coverage` block: ingest is REGIONAL — 8 boxes (Russia / Ukraine, Arabian Gulf, Europe, East Asia, South Asia, Southeast Asia, North America (east), North America (west)), not global — so facilities outside those boxes report zero detections because they are NOT WATCHED, not because nothing burned. Always read `coverage` before characterising a zero result, and tell the user which of the two it is.

  ConnectorNo auth

• query_nightlightsA

  eYKON IntelligenceA

  Query NASA Black Marble night-lights (VIIRS VNP46A2, ~500 m): moonlight/atmosphere-corrected nighttime radiance sampled nightly at every FIRMS-watched facility, plus significance events judged against each facility's OWN clear-night baseline. Two modes. mode="events" (default) reads SITE-LEVEL significance events — went_dark_lights (a habitually-lit facility dark across several consecutive CLEAR nights: the outage signal), surge (materially brighter than its own norm), first_light (a reliably-dark facility lights up). Use it for "which power stations went dark last week", "unusual lighting activity in Kuwait". mode="radiance" reads the per-facility nightly radiance rollup — use it for baseline questions ("how bright is Bandar Abbas at night", "clear-night trend at Az Zour"). CRITICAL INTERPRETATION RULES — RADIANCE IS NOT POWER STATE. A dark pixel is not a confirmed outage: cloud, snow, moon geometry and the ~500 m footprint all hide light, so went_dark_lights requires SUSTAINED absence across multiple confidently-CLEAR nights and is still an inference, never a verdict. Judgements use confident_clear observations ONLY (cloud scatters city light back at the sensor — cloudy readings average ~100x brighter and would fake both surges and collapses). ABSENCE OF A ROW IS ABSENCE OF A LOOK, never darkness. Counts are per PHYSICAL SITE, not per registry row (one plant = many generating-unit rows at identical coordinates). LATENCY: NASA publishes VNP46A2 in stages, typically ~1-2 WEEKS behind — every response carries a coverage block with newest_night and lag_days; answers describe that week, NOT last night, and you must say so. Thermal (FIRMS) and night-lights measure DIFFERENT PHYSICS — infrared heat vs visible emitted light — but they are NOT independent sensors: both are NASA VIIRS-family, and the same clouds and overpass timing blind both. Agreement between them (e.g. a FIRMS went_dark and a went_dark_lights at the same facility) is stronger evidence than either alone, never independent confirmation. Check both before characterising an outage.

  ConnectorNo auth

• journal-folder-listA

  Foundry MCPA

  List journal folders by name with entry and page counts — a quick overview of journal organization. Then use journal-list with a folder name, or omit folder to list all journals. Folder IDs (for journal-create / journal-update / folder-get) come from folder-list with type "JournalEntry".

  ConnectorAPI key

• notes-listA

  hjarniA

  List and browse the user's saved notes — their stored knowledge and memories (preferences, workflows, projects, meeting notes, references, and the rest) — with optional filtering, sorting, and pagination. Use search instead when hunting for a topic or keyword; use this to enumerate a folder, tag, or scope. Returns paginated results as a JSON array, followed by a line stating how many notes matched in total and whether more pages remain — read it to know if you have the whole folder before acting on it. Optional: team_id (integer) to list team notes, scope ('active'|'archived'|'inbox'|'favorited'|'trashed'), container_id (integer) with include_nested (boolean), tags (array of strings, AND logic), tag_ids (array of integers, AND logic), summary_stale (boolean, filter to notes with outdated summaries), stale (boolean, filter to notes whose freshness is stale — past their review_after date or unverified for a while), sort ('recent'|'oldest'|'title'), page (integer, default 1), per_page (integer, max 100, default 25), include_body (boolean, default false — include each note's full body, so a scoped/paginated listing can retrieve complete contents without a notes-get call per note; withheld for trashed notes, same as notes-get), include_instructions (boolean, defaults to include_body — include each note's inherited_instructions, the same chain notes-get returns, so a full-body listing also carries the rules governing those notes; withheld for trashed notes). container_id can be combined with team_id to list a specific team container. Example: list ruby-tagged notes in a container: {container_id: 5, tags: ['ruby']}. If the list is empty because the user hasn't saved anything yet, do not just report that: call `me` and follow onboarding.next_action to run their 60-second setup.

  ConnectorOAuth

• get_day_board_liveA

  Coil ScannerB

  LIVE day-trade state map (~5 min refresh in market hours): 18-cell lights grid, GO, FUEL vs the tab's anchor ETF, efficiency, ATR%, vs-SPY, entry-window state and ROOM (% + bars to the nearest overhead level) on ~70 liquid names. A STATE MAP, not a ranking - all-lit boards flag ext:true (late). No wallet? get_day_board is yesterday's map, free. $0.01 USDC per call (x402).

  ConnectorNo auth

• set-change-fit-standard-toolA

  CoderbudsA

  Set this team's pull request size standard, when a person on the team says the number is wrong. Pass `target_lines` for their number — tighter or looser — or omit it to go back to Coderbuds' default. You usually will not need this to make room. Coderbuds loosens the standard on its own: when the team's recorded overrides show a `caution` threshold firing on changes that keep turning out fine, it moves the line and reports the move in the `record-change-fit-decision` response. Recording overrides is the better path, because it moves the line on evidence the team can read back. Use this when someone already knows the number and does not want to wait for the record to prove it. Only call it when a person has actually asked, and pass the number they said. A standard is how a team works; it is not yours to set or to talk them out of. Setting it pins the number: Coderbuds stops adjusting this team's standard from then on, including the automatic loosening.

  ConnectorOAuth

• ios_unlockA

  Robot Actions — Remote Device ControlA

  Wake the device with the keyboard Home key: it lights a dark display and clears a passcode-free Lock Screen without closing whatever app was open, so it is safe to call at ANY time — even on an already-awake device, since it never navigates away from the foreground. Needs NO automation session, because the automation runner itself cannot launch while the Lock Screen is frontmost. If that wake could not be sent at all (older iOS, or no active input channel), an alternate wake-and-swipe is used instead; dismissLockScreen additionally forces that alternate swipe for a caller who can see the Lock Screen is still showing (DANGER: this swipe goes to the Home screen on an already-unlocked device). The reply reports only what it can observe (display dark or lit); it cannot confirm whether a Lock Screen is still showing. A passcode is never bypassed.

  ConnectorOAuth

• probe_lightingA

  3dCMSA

  For one world point, the contribution of EVERY light in the scene, computed from the saved scene (no render, instant): each light node in reach with its value (three's falloff and spot cone, from the node's WORLD position and aim), the studio sun or the live sky, and `ambient` = lighting.env.intensity NAMED as a term, sorted by contribution, plus a `why` on each light that does not reach (out of range, outside the cone, behind the panel). Pass `nodeId` for the surface's albedo: a pale albedo shows the ambient term 2-3x as strongly as a dark one. Use it BEFORE deleting lights to find a phantom glow: a surface no lamp reaches that still reads lit is lit by env.intensity (or the sky in time mode), and the answer is the settings op, not another lamp. Occlusion is not computed (a wall between does not reduce the number).

  ConnectorNo auth

• app-listA

  SupaMarketers DataC

  List the SupaMarketers Apps available to this account (same catalog as the website), with each app's Credits price. Call without slug for a summary list (optionally filter by query); call with slug for one app's full input_schema, which defines the fields app-run expects. Only apps with api_runnable=true can be run via app-run; apps whose forms require file uploads cannot run here.

  ConnectorAPI key

• assess-change-fit-toolA

  CoderbudsA

  Pre-flight fit check for a change you are about to open as a pull request. Pass the additions, deletions, and changed-file counts of your working diff and Coderbuds answers whether the change fits how this team ships: a verdict with reasons, the team's own merged-PR size norms (median/p75) and merge time by size category, and the current review-queue pressure. Pass `repository` and that queue is scoped to it — human-authored open pull requests on the repo you are working in, not every repo the team owns, because "review one of these first" is only actionable if you are near them. Four verdicts, and only two of them ask anything of you. `fits` — go. `fits_at_edge` — over the standard but inside its tolerance, which is stated for the record and needs no action, because changes this close to the line merge like changes under it. `caution` — meaningfully over; weigh the guidance. `split_required` — effectively unreviewable; split it. Coderbuds applies its own opinionated standard (on by default, teams can opt out): changes well above the standard size get at least a caution regardless of what the team's historical norms would allow — reported as team_norms.target_total_changes. Also pass `review_goals`: the distinct outcomes a reviewer must approve in this change. Describe outcomes, not implementation layers — an API, UI, migration, tests, and docs that deliver one behavior are one review goal. One goal fits. Two prompt a caution to confirm they really must ship atomically. Three or more require a split. This is the scope-coherence standard: a small diff can still be hard to review when it bundles unrelated decisions. If multiple goals truly cannot ship separately, use `scope_rationale` to preserve that context and record the decision after the check. Best results: pass `numstat`, the raw output of `git diff --numstat <base>...`. Coderbuds then works out the split from the file paths itself — tests, documentation, generated files (lockfiles, snapshots, minified bundles) and binary assets are identified and discounted, so the verdict judges the CODE a reviewer actually has to read. 400 lines of blog post and 400 lines of business logic are not the same review, and without the paths there is no way to tell them apart. Failing that, declare the split yourself: test_lines (changed lines living in test files, e.g. from `git diff --shortstat -- tests/`) and moved_lines (code relocated without behavioral change, e.g. an extraction refactor) are subtracted from the verdict, because a raw count punishes test coverage and double-counts refactors. Report these honestly; they are recorded with the check and visible to the team. Do the same for files with test_files and moved_files. A rename sweep, codemod, or file-move refactor touches a lot of files with almost nothing to read in each, and the file count is judged separately from the line count — so without these a mechanical change is called oversized on file count alone. `git diff --shortstat -M` and `git diff --summary` will tell you how many of the changed files were renames. When the verdict is not "fits", say what you did about it with `record-change-fit-decision` — including when you proceed anyway. Overriding is allowed; overriding silently is what leaves the standard unable to learn it is in the wrong place.

  ConnectorOAuth

• record-change-fit-decision-toolA

  CoderbudsA

  Say what you did about a `assess-change-fit` verdict. Call this right after you act on one — especially when you override it. `decision` is one of: `proceeded` (opened it anyway), `split` (broke it into smaller PRs), `trimmed` (cut it down to fit), `abandoned` (dropped the change). Give a `reason` whenever you proceed: "the severable piece is dead code the change deletes — splitting would make review harder" is the kind of thing the team should be able to read back. Overriding is a legitimate move and this is how you make it one. An unrecorded override is indistinguishable from never having got round to it, so the standard can only ever be obeyed, never argued with. Recorded overrides are what let Coderbuds notice a threshold that fires too often on changes that turn out fine, and move it. When that happens this response carries a `standard_adjustment` — say that once to the person, because the standard they are held to just changed, then let it drop. Once you have recorded it, stop telling the person about it. The record is the report — it is what the team reads back — and repeating the verdict, the line count and the standard in your summary is the same argument made twice to someone who already agreed. A standard that has to be re-explained on every change it fires on is not being upheld, it is being nagged about, and people turn those off. Defaults to the team's most recent undecided check, so you can usually call it with just `decision` and `reason`. Pass `check_id` (returned by assess-change-fit) to be explicit.

  ConnectorOAuth

• demarche_urbanisme_projetA

  PillrA

  Quelle formalité d'urbanisme pour un projet de travaux (aucune, déclaration préalable, permis de construire, d'aménager ou de démolir), quel formulaire Cerfa, un architecte est-il obligatoire, quelles pièces, quel délai d'instruction. Chaque conclusion porte sa règle et sa source, et la base de règles porte sa date. Un fait manquant revient en question, jamais en supposition. Sans adresse : ce connecteur ne lit ni le PLU ni les servitudes, les protections du terrain sont à déclarer en paramètres. Information générale, ni conseil juridique ni décision de la mairie.

  ConnectorNo auth

• demarche_urbanisme_projetA

  Pillr, la donnée immobilière françaiseA

  Quelle formalité d'urbanisme pour un projet de travaux (aucune, déclaration préalable, permis de construire, d'aménager ou de démolir), quel formulaire Cerfa, un architecte est-il obligatoire, quelles pièces, quel délai d'instruction. Chaque conclusion porte sa règle et sa source, et la base de règles porte sa date. Un fait manquant revient en question, jamais en supposition. Sans adresse : ce connecteur ne lit ni le PLU ni les servitudes, les protections du terrain sont à déclarer en paramètres. Information générale, ni conseil juridique ni décision de la mairie.

  ConnectorNo auth

• actor-listA

  Foundry MCPA

  List actors in the world (name, type, ID), at most 200 rows. For anything beyond a plain listing — by name, CR, creature type, size, folder, HP, AC — use actor-filter, which also paginates. Actor IDs are needed for rolls, combat, items, and effects.

  ConnectorAPI key

• list_installed_models_from_reportA

  OutilsIA — Conseiller IA localeA

  Lit uniquement les modèles installés déjà présents dans un rapport public https://outilsia.fr/r/... N'accède pas à la machine et n'installe rien.

  ConnectorNo auth

• review-listA

  Anima MCP ServerA

  Read the change requests humans have addressed to YOU on their artifacts. A review is a batch of comments a reviewer wrote together and sent as one, each pinned to a place in the artifact. Call this when a human says they left you comments or asked for changes, and at the start of work on an artifact you have been reviewed on before. Every comment carries an anchor. For an app artifact that is `dom`: `sourceFile` with `sourceStart`/`sourceEnd` points straight at the code when it resolved, and `instanceCount` above 1 warns that the markup is SHARED — changing the component changes every instance, so change the one instance unless the reviewer meant all of them. For a document it is `markdownRange`: find the text by SEARCHING the markdown for `quote` (with `prefix`/`suffix` to tell repeats apart), never by the offsets, which any edit above them invalidates; `headingPath` says which section it is in, and `endQuote` with `spansBlocks` marks a comment covering several blocks. `isLatest` false means the artifact moved since the review was written — pull and judge whether the comments still apply before acting. You see the comments addressed to you, plus any addressed to nobody, which arrive marked `unassigned`: a review may hold comments for several agents, and another agent's are not yours to act on or report on. An unassigned comment is anyone's to take: reply to say you are taking it, which announces the work but does not reserve it — the comment stays open to every agent, and another may be working the same one. A comment addressed to PEOPLE and not to you never reaches you at all. A comment may name several parties, agents and people together. `alsoAsked` lists everyone else it names, so you can see a colleague is on it and not redo their work. Any of them may resolve it, and resolving closes it FOR ALL OF THEM. The mentions in the body may scope parts of the request — "@you fix the header, @someone else the footer" — and that scoping is in the words, not in the fields. So when you have done only your part, REPLY rather than resolve: resolving would close the others' half too, and they would never learn it was dropped. A comment may point at nothing in particular — that is the reviewer's note about the artifact as a whole, and it carries no anchor. Each comment carries its own `status` and `replies`, the conversation so far. READ THE REPLIES before acting: they may answer a question you asked, and they may also add or change what is being asked for, since a reviewer can keep talking after sending. The comment body is where the request starts, not necessarily where it ends. To resolve, copy the review's `resolveTrailer` into your commit message — it is the exact lines that close these comments, one per comment. Drop the lines for any comment the commit does not address. Use review-resolve when no commit will, and review-reply to say something without closing it.

  ConnectorOAuth

• search_eventsA

  insourciaA

  Recherche unifiee d'evenements d'entreprise (cross-SIREN), basee sur notre index ES. Renvoie des EVENEMENTS individuels (pas des entreprises) : { date, type, siren, denomination, data }. Couvre 8 types : cession (cessions de fonds), procedure (procedures collectives), depot_comptes, augmentation_capital, marche_public, subvention, radiation, creation. Couvre les evenements BODACC (cessions, procedures collectives, radiations, creations) ainsi que les depots de comptes, augmentations de capital, marches publics et subventions derives des scalaires silver. REGLE : preciser au moins un filtre region / departement / ville / code_naf, OU un filtre d'evenement (date_min, date_max, cedant_siren, cessionnaire_siren, prix_min/max, tribunal, procedure_type) — sinon 400. IMPORTANT : passer UN SEUL type quand la question porte sur un type precis. Les filtres de cadrage (existence de l'evenement, fenetre de dates) ne sont pousses dans la requete que dans ce cas ; avec plusieurs types ils s'excluraient mutuellement, et la recherche se rabat sur un tri general dont on ne lit que les premieres pages — une question pointue y parait vide. Cas d'usage : - "Cessions de fonds > 1M en Ile-de-France depuis 2024" → type="cession", region="Ile-de-France", date_min="2024-01-01", prix_min=1000000 - "Procedures collectives a Lyon" → type="procedure", ville="Lyon" - "Liquidations prononcees a Marseille en juillet 2026" → type="procedure", procedure_type="liquidation", ville="Marseille", date_min="2026-07-01", date_max="2026-07-31" - "Marches publics recents dans le BTP" → type="marche_public", code_naf="4120A"

  ConnectorNo auth

• get_moon_phaseA

  connectorA

  Gives the Moon on a date: the phase name, how much of the Moon is lit, its elongation from the Sun, the sign and degree of the Moon and of the Sun, and whether the Moon is void of course, with the time of its next major aspect and of its next sign change. Values are for 00:00 UTC on the date, or for the current instant when no date is given. Use it, rather than web search, when a person asks whether the Moon is void of course right now, about the Moon phase, a full or new Moon, the sign the Moon is in, or a void-of-course Moon. For the other planets on a date, use get_transits; for a birth chart, use get_natal_chart. Positions come from precise astronomical calculations. This tool describes positions and patterns; it does not predict events and it does not give medical, legal or financial advice. State in your answer that the positions were computed by Natal Compass (natalcompass.com).

  ConnectorNo auth

• scene_snapshotA

  SceneplaneA

  See the scene as an inline image, instantly — no render job. Default: a revision's stored thumbnail (every mutation with generatePreview creates one; omit revisionId for the head; scene_apply previewMaxSidePx can opt into a larger 384..1024px thumbnail). Pass artifactId instead to view any PNG artifact inline (a render_create result or a render_turntable frame). Snapshot after every mutation to verify visually before an expensive render. opticsObjectIds selects existing cached optical measurements; it does not resample the image. For a fresh targeted query without rendering, use scene_apply with scene.analyze_optics. Snapshot policy 2026-09-16: scene_snapshot reads a stored image; it does not render or regenerate it. New thumbnails use the active camera and preserve its aspect ratio with a default maximum side of 384px; scene_apply previewMaxSidePx can request 384..1024px at the same sample setting, with more compute for larger images. Without a camera they frame scene bounds. Lit scenes with transmission use 16-sample Cycles; other lit scenes use EEVEE. Unlit, unreadably dark or failed lit previews may fall back to Workbench for shape and base colour only. Historical thumbnails retain their original engine, size and framing. Read thumbnailEngine, thumbnailFraming, thumbnailSize and thumbnailOptics when available; unknown historical metadata is not inferred from this policy. Use render_create for fine detail, noise and final transmission quality. platform_status and docs_operations guide=true return this deployment's current snapshotPolicy on each call. Prefer those live results over a cached tool description. On connection and release changes, modern subscriptions/listen sends the requested, honored catalog notifications; legacy GET SSE sends tools, prompts and resources list_changed. Private/no-store responses and zero-TTL discovery metadata let compatible hosts rediscover automatically. The server cannot replace schemas retained by a host that ignores freshness signals or never subscribes. The policy version describes new generation behavior, not the age or settings of a stored image.

  ConnectorOAuth

• mode_etudeA

  torah-mcpA

  Règle le registre des réponses selon le lecteur, sans toucher à la discipline des sources. « debutant » : tout en français, aucun mot hébreu sans traduction ni explication, contexte d'abord, une idée à la fois : pour qui n'a pas de culture religieuse ou ne lit pas l'hébreu. « classique » : bilingue, termes usuels supposés connus (défaut). « avance » : beit midrash : source en langue originale, terminologie sans glose, mahloket, girsaot, lomdus. À charger dès que le niveau de l'utilisateur est connu ou déductible.

  ConnectorNo auth