"Finding MCP related to Web3" matching MCP tools:

• save_insightsA

  Ask AIA

  TRIGGER: Whenever you surface a problem or opportunity from the data, OFFER to save it as an insight and confirm before writing — don't auto-save. Make the offer concrete and inline: 'Want me to save this as an insight to track?'. Findings vary in significance; the user decides what belongs on the checklist. Insights are OBSERVATIONS (findings to act on) — when a fix is actually SHIPPED, that's a separate thing: call set_intervention (it auto-flips the linked insight to 'addressed' and owns the before/after verdict). Don't model 'fix applied' or '30-day check' as insights. Call this AFTER generating recommendations from get_insights data, OR mid-conversation when the user confirms. Can save any number of insights. To replace the existing checklist (instead of appending), set replace: true. To update a single existing insight, use update_insight with the insight's id instead. parentInsightId/threadId group related FINDINGS as one story (finding → re-finding → superseded). RESPONSE: returns `insights: [{insightId, title, category, priority, status, threadId, parentInsightId}]` in the same order as the input — use those insightIds directly in subsequent record_metric_snapshot / set_intervention(linkedInsightIds) / update_insight calls (no round-trip through get_insights needed).

  ConnectorOAuth

• admin_update_findingA

  redm-mcpA

  Admin-only: edit an existing community finding in place. Pass `id` plus only the fields to change — `title`, `body`, `tags` (replaces the whole list), `category` (`null` clears), `source` (`null` clears). A title/body change re-embeds the finding so `semantic_search` follows the new text; a body change re-derives the auto-linked natives (explicit links are kept) and refreshes the `finding_context` blurb on every affected native. Read the current text with `admin_get_finding` first and send the full corrected `body`, not a diff. Only findings of THIS deployment's game can be edited; a finding owned by the other game is refused. Note: `semantic_search` results may lag up to 10 minutes behind an edit (result cache).

  ConnectorOAuth

• admin_update_findingA

  RedM McpA

  Admin-only: edit an existing community finding in place. Pass `id` plus only the fields to change — `title`, `body`, `tags` (replaces the whole list), `category` (`null` clears), `source` (`null` clears). A title/body change re-embeds the finding so `semantic_search` follows the new text; a body change re-derives the auto-linked natives (explicit links are kept) and refreshes the `finding_context` blurb on every affected native. Read the current text with `admin_get_finding` first and send the full corrected `body`, not a diff. Only findings of THIS deployment's game can be edited; a finding owned by the other game is refused. Note: `semantic_search` results may lag up to 10 minutes behind an edit (result cache).

  ConnectorOAuth

• getsign_helpA

  GetSign MCPA

  Read GetSign agent docs or named flow recipes. Do not use this to list tools. tools/list already has every tool name and description. This tool is for on-demand guides — remote MCP clients do not get local CLAUDE.md. No args: short index of doc paths and flow names. path: markdown for that guide (gotchas, placeholders-and-signers, flows/send_new_document, or a getsign://docs/... URI). flow: same as path=flows/{name} (e.g. send_new_document). query: matching docs, flows, and related tool names — not the full catalog.

  ConnectorOAuth

• get_visibility_indexA

  DABLOCK AI Visibility IndexA

  The whole current release in one call: every tracked brand in crypto/Web3 with its rank, share of answer overall and per engine, commercial intent and quadrant. Share of answer is the percentage of a fixed panel of category buyer prompts in which an engine names the brand. Use this when the question is about the field — who leads, who is absent, how the category looks. It is one response of roughly 8 KB for 24 brands, so prefer it over calling get_brand_visibility repeatedly. Do NOT use it for one named brand (get_brand_visibility is the direct answer), for movement over time (get_history holds the series; a single release cannot show a trend), or to audit a website's own AI visibility — this is a measured dataset about third-party brands, not a site audit. Covers crypto/Web3 only; the sibling index at dabyte.ai covers the other niche. Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dablock.ai when quoting a number.

  ConnectorNo auth

• get_visibility_indexA

  dablock.aiA

  The whole current release in one call: every tracked brand in crypto/Web3 with its rank, share of answer overall and per engine, commercial intent and quadrant. Share of answer is the percentage of a fixed panel of category buyer prompts in which an engine names the brand. Use this when the question is about the field — who leads, who is absent, how the category looks. It is one response of roughly 8 KB for 24 brands, so prefer it over calling get_brand_visibility repeatedly. Do NOT use it for one named brand (get_brand_visibility is the direct answer), for movement over time (get_history holds the series; a single release cannot show a trend), or to audit a website's own AI visibility — this is a measured dataset about third-party brands, not a site audit. Covers crypto/Web3 only; the sibling index at dabyte.ai covers the other niche. Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dablock.ai when quoting a number.

  ConnectorNo auth

• get_corpus_coverageA

  SRI — MCP Server InspectorA

  No arguments. Returns how many MCP servers have been read at source level, and the share of them with each category of finding (credential access, network egress, install-time execution, prompt-injection surface). Use this to judge whether checking a specific server is worth it before you look one up. It reports aggregate counts only - no per-server findings, and no verdict about any individual server.

  ConnectorNo auth

• particle_podcast_list_relatedA

  particle-proA

  List the shows most related to a podcast, best first — "shows like this show". Each result carries the related show's slug, a calibrated score in (0,1], and a coarse band (strong: same beat and audience; moderate: overlapping subject or audience; weak: a loose connection) to branch on. Add `include: ["basis"]` to see WHY each pair is related: content similarity of recent episodes, shared topics, shared guests (named), same publisher, shared sponsors — use it to explain a recommendation or to keep only pairs related for the reason you care about (shared guests for booking, content for media planning). Related sets are precomputed per show from its transcripts, topic profile, guest roster, network and advertisers, restricted to the show's language. Only shows above a relatedness floor are listed, machine-generated and farmed feeds are never listed, and a publisher's duplicate feeds of one show appear once. An empty FIRST page is not an error: its `coverage` says whether the set is not computed yet, nothing cleared the floor, or the request's filters and the default policy removed everything; an empty page reached through a cursor is simply the end of the list. Not a topic browser: for shows that COVER a topic use `particle_podcast_resolve` with `topic_slug`. Not a guest lookup: for where a person has appeared use `particle_podcast_get_guest`. Not advertiser co-occurrence: use `particle_podcast_get_sponsors`. Every related show's slug feeds `particle_podcast_resolve`, `particle_podcast_list_episodes` and the other podcast tools; person slugs in the basis feed `particle_podcast_get_guest`, topic slugs feed `particle_podcast_resolve`'s `topic_slug`. For the five most related shows inline on a resolve, pass `include: ["related"]` to `particle_podcast_resolve` instead of calling this tool.

  ConnectorOAuth

• admin_delete_findingA

  redm-mcpA

  Admin-only: permanently delete a community finding. Removes the row, its native links (cascade) and rewrites or clears the `finding_context` blurb on every native that quoted it, so `lookup_native` and `semantic_search` stop surfacing it immediately (the `semantic_search` result cache may lag up to 10 minutes). Irreversible — inspect with `admin_get_finding` first; prefer `admin_update_finding` when the finding is merely wrong rather than junk. Only findings of THIS deployment's game can be deleted.

  Connector

  Destructive

  OAuth

• admin_delete_findingA

  RedM McpA

  Admin-only: permanently delete a community finding. Removes the row, its native links (cascade) and rewrites or clears the `finding_context` blurb on every native that quoted it, so `lookup_native` and `semantic_search` stop surfacing it immediately (the `semantic_search` result cache may lag up to 10 minutes). Irreversible — inspect with `admin_get_finding` first; prefer `admin_update_finding` when the finding is merely wrong rather than junk. Only findings of THIS deployment's game can be deleted.

  Connector

  Destructive

  OAuth

• get_finding_remediationA

  RoutebaseA

  Get remediation advice for a single finding as GitHub-flavored markdown. When AI Assist is enabled and within budget this is a suggestion written for this exact finding; otherwise it falls back to the static guidance-library text and says so in 'source'. Unlike the other reads this one can spend AI budget, which is why it is a separate tool. Use this for advice on one finding; for the whole library use list_security_guidance. Requires project context.

  ConnectorAPI key

• withdraw_findingA

  northreachB

  Retract support for a finding you authored, with a reason. Original content remains visible and labeled withdrawn. Identical retries are safe; this does not claim the finding is disproven.

  ConnectorNo auth

• lemma_query_verified_attributesA

  mcpA

  Query cryptographically verified attributes from Lemma. Use this as the primary tool for finding documents whose attributes match given conditions (e.g., "subject's birthYear lt 2008"). Returns { results: Array<{ docHash, schema, issuerId, subjectId, attributes, isVerified, proof?: { status, circuitId, chainId }, disclosure? }>, hasMore }. The MCP layer enriches each item with an `isVerified` flag derived from `proof.status` (true when status is 'verified' or 'onchain-verified'). Use lemma_get_proof_status to monitor a specific proof; use lemma_get_schema to interpret the keys returned in `attributes`.

  ConnectorNo auth

• goal-register-iteration-findingA

  Planner (proof-of-done)A

  Register an immutable LeanSolver finding against the currently tracked goal contract. subjectRefs must be goal-scoped refs of kind goal, criterion, or assumption. Returns the server-generated finding id to pass later as addressesFindingId; rejects stale contract tracking.

  ConnectorNo auth

• goal-register-iteration-findingA

  Planner MCP — provable "done" for AI agentsA

  Register an immutable LeanSolver finding against the currently tracked goal contract. subjectRefs must be goal-scoped refs of kind goal, criterion, or assumption. Returns the server-generated finding id to pass later as addressesFindingId; rejects stale contract tracking.

  ConnectorNo auth

• list_mcp_activityA

  Kema InvoiceA

  The tenant's recent agent activity log: one entry per successful MCP tool call (tool name, related invoice number when known, timestamp). Newest first.

  ConnectorOAuth

• get-mcp-adoption-toolA

  CoderbudsA

  Who on the team is actually using the Coderbuds MCP. Every MCP tool call is recorded per member, so this reports adoption over a recent window (default 30 days): total invocations, per-member usage with last-used time and favourite tool, per-tool call counts, and — the nudge list — login members who have never connected the MCP at all. The denominator is who could plausibly connect one today — a login member (only they can mint API tokens) who is still shipping code. Tracked contributors cannot connect, deactivated or long-inactive members have left, and someone with several linked identities counts once. Use when asked "who is using the MCP", "is the team on the MCP yet", or to find who still needs the setup instructions. A call is attributed to the team it was about — the `repository` slug on it, or the `?team=` binding on the connection — not to whichever team the web switcher last landed on, so a member working across several teams shows up under the one they were working in.

  ConnectorOAuth

• update_focus_itemA

  Ask AIA

  Set the manual state of a single item in the current focus plan: 'in_progress' (started), 'dropped' (decided not to do it this week), or 'planned' (clear the overlay). NOTE: you can NOT set an item to 'done' here — completion is DERIVED from the linked finding becoming addressed or the intervention closing. To complete a 'tackle' item, ship the fix and call set_intervention (which addresses the finding); to complete a 'check' item, call complete_intervention. Get itemIds from get_focus.

  ConnectorOAuth

• devtune_acknowledge_retrieval_restrictionA

  DevTune MCPA

  Acknowledge an intentional retrieval restriction for only the exact URLs displayed in an audit finding. Requires explicit customer confirmation and actions.write. Preserves the finding, evidence and score. Never infer customer intent.

  ConnectorAPI key

• devtune_reconsider_retrieval_restrictionA

  DevTune MCPA

  Reconsider an intentional retrieval restriction for only the exact URLs displayed in an audit finding. Requires explicit customer confirmation and actions.write. Preserves the finding, evidence and score. Never infer customer intent.

  ConnectorAPI key

• list_toolsA

  foundation-discoveryA

  List available MCP tools and get detailed help. Use this tool to discover what tools are available and how to use them. Call without parameters to see all tools, or provide a tool name to get detailed help including parameters, examples, and related tools.

  ConnectorNo auth