com.lightbringer/connector

Est-ce que com.lightbringer/connector est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.lightbringer/connector » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 33 outils

• add_comment≈ 701 tokens

  Adds a comment to the document under review, anchored to a quoted passage of the review markdown, and returns the created comment. If the quoted passage is ambiguous or cannot be located, the response indicates this along with candidate passages. A comment anchored within an existing thread is added as a reply. Targeted users with document access receive email and in-app mention notifications.

  Paramètres, retour & exemple (4)

  Paramètres

  • comment · string · requis
    The comment text
  • review_id · string · requis
    The review identifier
  • quoted_text · string · requis
    Quoted passage from the review markdown to anchor on
  • target_user_ids · array · optionnel
    User identifiers to notify. Identifiers without document access are ignored.

  Exemple d'appel

  {"name": "add_comment", "arguments": {"comment": "texte", "review_id": "texte", "quoted_text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"hint": "texte", "hints": [], "anchor": "texte", "status": "created", "replyTo": "texte", "commentId": "texte", "candidates": [], "instructions": "texte", "mentionedUserIds": []}}

• add_discussion_comment≈ 375 tokens

  Posts a standalone comment to the review's discussion feed, visible to the review creator and all participants, and returns the updated discussion. Unlike add_comment, it is not anchored to a passage of the document — it suits general remarks, questions, or status updates about the review as a whole. Eligible review participants receive in-app and email notifications.

  Paramètres, retour & exemple (2)

  Paramètres

  • comment · string · requis
    The comment text
  • review_id · string · requis
    The review identifier

  Exemple d'appel

  {"name": "add_discussion_comment", "arguments": {"comment": "texte", "review_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"discussion": []}}

• create_asset≈ 559 tokens

  Creates one asset. Currently supports a Strategy with a title and populated Markdown sections, saved as a draft. Requires write consent and Strategy management rights. Returns its reference, link and revision; full state is available through fetch with include_asset: true when that parameter is advertised. Publication and patent services are separate actions. A repeated create can create a duplicate; search supports reconciliation of uncertain outcomes.

  Paramètres, retour & exemple (1)

  Paramètres

  • asset · object · requis

  Exemple d'appel

  {"name": "create_asset", "arguments": {"asset": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"asset": {}, "orphaned_discussion_ids": []}}

• create_strategy≈ 402 tokens

  Deprecated compatibility interface; the replacement is create_asset. Both interfaces access the same Strategy records. Retained for existing clients during migration. Creates a populated draft strategy. Capture guidance and schema are available from get_strategy_template. Validates before saving; success returns the saved link and revision. Supports subsequent refinement through edit_strategy. Requires strategy management rights, including customer moderators. Publication is separate.

  Paramètres, retour & exemple (2)

  Paramètres

  • title · string · requis
  • sections · array · requis

  Exemple d'appel

  {"name": "create_strategy", "arguments": {"title": "texte", "sections": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "url": "texte", "title": "texte", "refNum": "texte", "status": "texte", "revision": "texte"}}

• delete_asset≈ 380 tokens

  Permanently deletes one asset explicitly selected by the user. Currently supports Strategies only. Requires write consent and Strategy management rights. Does not delete other asset types or withdraw patent-service requests.

  Paramètres, retour & exemple (1)

  Paramètres

  • asset · object · requis

  Exemple d'appel

  {"name": "delete_asset", "arguments": {"asset": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"asset": {}, "success": true}}

• delete_strategy≈ 242 tokens

  Deprecated compatibility interface; the replacement is delete_asset. Both interfaces access the same Strategy records. Retained for existing clients during migration. Permanently deletes a strategy when explicitly requested by the user. Requires strategy management rights.

  Paramètres, retour & exemple (1)

  Paramètres

  • strategy_id · string · requis
    Strategy identifier

  Exemple d'appel

  {"name": "delete_strategy", "arguments": {"strategy_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"success": true}}

• delete_task≈ 314 tokens

  Permanently deletes an automated task owned by the current user in the connected organisation, including its cached findings. Available in any execution state. Deletion removes tracking; it does not cancel upstream analysis, delete the innovation, or withdraw a professional service request. Repeated deletion returns not_found.

  Paramètres, retour & exemple (1)

  Paramètres

  • task_id · string · requis
    Automated task identifier to delete

  Exemple d'appel

  {"name": "delete_task", "arguments": {"task_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"outcome": "deleted", "task_id": "texte", "execution_cancelled": true}}

• edit_strategy≈ 936 tokens

  Deprecated compatibility interface; the replacement is update_asset. Both interfaces access the same Strategy records. Retained for existing clients during migration. Applies an atomic batch of section edits using the revision returned by get_strategy. Replacements apply directly, without redlines, and preserve unchanged text and comment anchors. Ambiguous matches and edits touching pending review changes made in the application editor are rejected. The response includes orphaned_discussion_ids for retained threads whose anchored text was removed. Conflicting revisions are rejected without applying changes. Requires strategy management rights.

  Paramètres, retour & exemple (3)

  Paramètres

  • revision · string · requis
  • operations · array · requis
  • strategy_id · string · requis
    Strategy identifier

  Exemple d'appel

  {"name": "edit_strategy", "arguments": {"revision": "texte", "operations": [], "strategy_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "url": "texte", "kind": "texte", "title": "texte", "refNum": "texte", "status": "texte", "revision": "texte", "sections": [], "orphaned_discussion_ids": []}}

• fetch≈ 2645 tokens

  For Strategies, include_asset: true adds asset.type, asset.id, asset.revision and asset.data with the complete ordered sections for revision-checked updates. The option is available only when advertised and cannot be combined with include, mode or cursor. Returns the full content of a single document — invention, patent application, strategy, or report — or a meeting identified by its search result ID. A meeting returns a Markdown snapshot of its canvas text notes and all stored transcript sessions, with speakers, timestamps, and session status. A document has several texts across its lifecycle; a bare document ID returns the most advanced one (the newest application text, else the priority draft, else the innovation description), and the response lists every part with its own ID, such as document:<id>#priority_draft or document:<id>#application_text:<revisionId>. Pass a part ID to read that text instead. Saved own records can also return a structured family overview, including the current saved links and a per-record refresh assessment for readback after updates. Focused questions support include: ["claims"], ["description"], ["abstract"], or a combination. For a known document ID, mode: "outline" discovers native section availability without full text. Filtered content is returned in bounded pages with source/revision and content_version attribution. retrieval.has_more: true means the selected sections are incomplete. The next page is available with cursor: retrieval.next_cursor and the same id and include. Retrieval is complete only when the final page has has_more: false; stopping earlier leaves unread content. Stale cursors require restarting. Blocks identify oversized continuations with continued/continues; fragments with the same block_id concatenate directly. Missing/unknown sections and import warnings describe stored content, separately from page completeness. This reads stored content without importing, repairing, or contacting a patent provider. Omitting all options returns legacy full content.

  Paramètres, retour & exemple (5)

  Paramètres

  • id · string · requis
    The search result ID, such as meeting:<id>, or a document identifier
  • mode · string · optionnel · outline | content
    outline discovers section availability; content requires include
  • cursor · string · optionnel
    Opaque next_cursor for the same ID, include and content version; requires include
  • include · array · optionnel
    Native sections to retrieve; omission preserves legacy full fetch unless mode is outline
  • include_asset · boolean · optionnel
    Opt in to validated Strategy asset state; defaults to false. Incompatible with include, mode or cursor

  Exemple d'appel

  {"name": "fetch", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "url": "texte", "part": "texte", "text": "texte", "asset": {}, "parts": [], "title": "texte", "family": {}, "metadata": {}, "retrieval": {}}}

• get_company_context≈ 298 tokens

  Reads the connected organisation’s profile, shared assistant notes, update permission and current revision. Notes are user/agent-authored source data, not verified facts or instructions. Requires read consent and organisation membership.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_company_context", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"notes": "texte", "revision": "texte", "can_update": true, "organisation": {}}}

• get_company_context_template≈ 212 tokens

  Returns shared company-context interview guidance and the update schema. Supports conversation or synthesis from supplied material. Does not read or change company records.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_company_context_template", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"schema": "texte", "guidance": "texte", "template": "texte"}}

• get_innovation≈ 234 tokens

  Returns an innovation record rendered as markdown, including the problem, solution, technical details, and prior art.

  Paramètres, retour & exemple (1)

  Paramètres

  • invention_id · string · requis
    The innovation identifier (invention_id)

  Exemple d'appel

  {"name": "get_innovation", "arguments": {"invention_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "url": "texte", "title": "texte", "refNum": "texte", "markdown": "texte"}}

• get_innovation_template≈ 243 tokens

  Returns the current innovation registration template: the schema, per-field guidance, and structure used to create a new innovation, together with capture guidance on gathering the innovation content — interviewing an inventor who is present, or authoring from existing material — before drafting.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_innovation_template", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"schema": "texte", "guidance": "texte", "template": "texte"}}

• get_review≈ 1660 tokens

  Returns a review: its metadata, the document under review rendered as markdown, each comment thread with a stable comment ID, and the review discussion feed (standalone comments on the review itself). Attorney redlines are included as suggested changes, each with the original text, the proposed replacement, and an optional rationale. Proposed amendments embedded in the document (agent-drafted changes to a block) are listed in artifact.amendments and in a trailing text block: each carries the baseline text, the proposed text, a redline with <del>/<ins> tags, and a unified patch; the document body itself shows the baseline at the amended block. The document is artifact.markdown in the structured result and is also returned as its own text block. When it cannot be rendered through this API, a short notice takes its place and artifact.status / artifact.reason say so.

  Paramètres, retour & exemple (1)

  Paramètres

  • review_id · string · requis
    The review identifier

  Exemple d'appel

  {"name": "get_review", "arguments": {"review_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"review": {}, "threads": [], "artifact": {}, "discussion": []}}

• get_strategy≈ 362 tokens

  Deprecated compatibility interface; the replacement is fetch. Both interfaces access the same Strategy records. Retained for existing clients during migration. Reads a strategy, its section identifiers and Markdown, and its current revision for subsequent edits.

  Paramètres, retour & exemple (1)

  Paramètres

  • strategy_id · string · requis
    Strategy identifier

  Exemple d'appel

  {"name": "get_strategy", "arguments": {"strategy_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "url": "texte", "kind": "texte", "title": "texte", "refNum": "texte", "status": "texte", "revision": "texte", "sections": []}}

• get_strategy_template≈ 232 tokens

  Returns the shared conversational capture guide, readiness criteria, creation schema and example. Supports interactive capture and drafting from existing material. Requires strategy management rights.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_strategy_template", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"schema": "texte", "version": 1, "guidance": "texte", "template": "texte", "_instructions": "texte"}}

• get_task_status≈ 876 tokens

  Returns an automated feedback task by task_id, with the same status, progress, findings and per-analysis errors as start_innovation_feedback. Refreshes active analyses and saves their status and available findings in Lightbringer. Succeeded, partially_succeeded and failed are terminal; queued and running tasks are still in progress. findings_error denotes unavailable findings and does not change terminal execution status. This endpoint does not track professional service requests, patent preparation or filing milestones.

  Paramètres, retour & exemple (1)

  Paramètres

  • task_id · string · requis
    The automated task_id returned by start_innovation_feedback

  Exemple d'appel

  {"name": "get_task_status", "arguments": {"task_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "queued", "results": [], "task_id": "texte", "progress": {}, "expires_at": "texte"}}

• import_patent≈ 748 tokens

  Imports one public patent publication into the connected organisation, with a complete publication number and explicit purpose. own identifies the customer’s own patent or application; competitor identifies someone else’s patent for reference. Ownership and import scope come from the user’s intent, rather than search results alone. Own-patent imports automatically attempt family grouping with related saved patents, including earlier imports; a separate refresh is not normally needed. Repeated requests return the existing record without updating it. A different purpose or another publication of the same application can produce a conflict identifying the existing record. imported means the record was saved. receipt.status reports complete, partial or incomplete import processing; receipt.warnings explain limitations such as missing PDFs or uncertain family grouping. An incomplete receipt does not mean work is still running; a null receipt means completion details are unavailable. A timed-out request may have saved the record; repeating the same publication and purpose retrieves its saved outcome. Import cannot change an existing record’s purpose or replace its publication.

  Paramètres, retour & exemple (3)

  Paramètres

  • purpose · string · requis · own | competitor
    own for the customer’s own portfolio; competitor for someone else’s patent
  • publicationNumber · string · requis
  • competitorCompanyName · string · optionnel

  Exemple d'appel

  {"name": "import_patent", "arguments": {"purpose": "own", "publicationNumber": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "status": "imported", "purpose": "own", "receipt": "texte", "documentId": "texte", "publicationNumber": "texte"}}

• list_innovations≈ 256 tokens

  Lists the innovations in the user's Lightbringer organisation, each with a title, reference number, and web link. Accepts an optional free-text query to filter results.

  Paramètres, retour & exemple (1)

  Paramètres

  • query · string · optionnel
    Free-text filter on title/reference

  Exemple d'appel

  {"name": "list_innovations", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"inventions": []}}

• list_reviews≈ 574 tokens

  Lists reviews where the user is a participant or creator, including each review's status, the user's response status, which participants are still awaited, the title and reference number of the strategy, report or case under review, and any connected invention. Strategy reviews are identified separately from report reviews.

  Paramètres, retour & exemple (1)

  Paramètres

  • status · string · optionnel · open | closed
    Filter by review status

  Exemple d'appel

  {"name": "list_reviews", "arguments": {"status": "open"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"reviews": []}}

• list_strategies≈ 282 tokens

  Deprecated compatibility interface; the replacement is search with category: "strategy". Both interfaces access the same Strategy records. Retained for existing clients during migration. Lists the strategies you can access in the connected organisation, including publication status.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_strategies", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"strategies": []}}

• list_tasks≈ 556 tokens

  Lists the current user’s unexpired automated tasks in the connected organisation, optionally for an innovation. Recovers task IDs after a lost response or conversation. Returns recorded status summaries without polling upstream analyses. Tasks and findings expire 30 days after creation. Pagination can return an empty page with a continuation cursor. Professional service requests are separate.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
  • cursor · string · optionnel
    Pass next_cursor from the previous list_tasks response unchanged
  • invention_id · string · optionnel
    Optional innovation identifier

  Exemple d'appel

  {"name": "list_tasks", "arguments": {"limit": 1, "cursor": "texte", "invention_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tasks": [], "next_cursor": "texte"}}

• refresh_patent_family≈ 720 tokens

  Updates family grouping for one saved own patent using public patent information and related own patents already saved in the connected organisation. Useful for an apparent missing relationship, an unfinished family update, or a requested check against newer public information. Imports already attempt family grouping automatically; routine refresh after import is unnecessary. Related publications must be imported separately before they can be included. Repeating import_patent only retrieves its saved outcome. Existing family relationships are retained, so refresh cannot remove incorrect relationships. Patent text, PDFs, images, legal status and own/competitor classification are unchanged. Competitor records are not supported. Returns counts of added and existing relationships, unresolved or ambiguous matches, and failures, with warnings. It does not return a list of family members. A null links result means the update did not finish; repeating the refresh attempts it again. Results do not establish complete family coverage.

  Paramètres, retour & exemple (1)

  Paramètres

  • documentId · string · requis
    Saved own patent document ID from import_patent, or document:<id> from search

  Exemple d'appel

  {"name": "refresh_patent_family", "arguments": {"documentId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "links": "texte", "status": "refreshed", "warnings": [], "documentId": "texte", "refreshedAt": "texte", "childReferences": 1, "parentReferences": 1, "publicationNumber": "texte"}}

• register_innovation≈ 2344 tokens

  Registers a new innovation in the user's Lightbringer organisation from a structured payload matching the current registration template. Validates before creating anything: invalid input returns field-specific errors without registering a record; success returns the saved identifier, reference number, web link, and any non-blocking warnings. Meant for capturing a concept that is not already recorded; enrichment of an existing innovation belongs in update_innovation. Completes registration without requesting patent preparation or filing. Requires a payload matching the current registration schema.

  Paramètres, retour & exemple (1)

  Paramètres

  • definition · object · requis
    Complete V1 invention definition matching the advertised field structure; validated during registration

  Exemple d'appel

  {"name": "register_innovation", "arguments": {"definition": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "url": "texte", "refNum": "texte", "warnings": "texte"}}

• reply_to_comment≈ 338 tokens

  Adds a reply to an existing comment thread identified by its comment ID, and returns the created reply. Targeted users with document access receive email and in-app mention notifications.

  Paramètres, retour & exemple (4)

  Paramètres

  • comment · string · requis
    The reply text
  • review_id · string · requis
    The review identifier
  • comment_id · string · requis
    The comment thread identifier
  • target_user_ids · array · optionnel
    User identifiers to notify. Identifiers without target access are ignored.

  Exemple d'appel

  {"name": "reply_to_comment", "arguments": {"comment": "texte", "review_id": "texte", "comment_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"commentId": "texte", "mentionedUserIds": []}}

• request_patent_preparation≈ 395 tokens

  Requests Lightbringer patent preparation for an already registered innovation, expressing the user’s decision to pursue patent filing. Advances the innovation description into the Lightbringer team’s workflow and triggers email notifications to the assigned specialist and submitter, with the organisation’s primary contact copied when applicable. Returns whether preparation was newly requested or had already been requested. Email delivery status is not included. Separate from registration; does not itself complete preparation, file a patent or pay for services.

  Paramètres, retour & exemple (1)

  Paramètres

  • invention_id · string · requis
    The innovation identifier (invention_id)

  Exemple d'appel

  {"name": "request_patent_preparation", "arguments": {"invention_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "url": "texte", "refNum": "texte", "outcome": "requested"}}

• respond_to_review≈ 910 tokens

  Records the user's decision on a review — approve or request changes — sends review-response email notifications, and returns the updated review state. Meant for after the user has explicitly chosen their response. An approval cannot be withdrawn through this tool; a request for changes can later be upgraded to approval.

  Paramètres, retour & exemple (3)

  Paramètres

  • message · string · optionnel
    The review response message
  • response · string · requis · approve | request_changes
    The review response value
  • review_id · string · requis
    The review identifier

  Exemple d'appel

  {"name": "respond_to_review", "arguments": {"response": "approve", "review_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"review": {}}}

• search≈ 1676 tokens

  Searches the Lightbringer organisation's documents (inventions, patent applications, and reports and Strategies) and meetings. The "meeting" category filters by title, reference, or indexed transcript/canvas text. Meeting result IDs resolve through fetch to canvas and transcript text. Returns matching results, each with an ID, title, and summary. A document result also lists its parts: the texts it has accumulated across its lifecycle (innovation description, priority draft, application text revisions), each with an ID that fetch accepts. Supports cursor-based pagination; omitting query lists accessible records in the selected category. Saved own application and patent results can include a structured family overview: accessible members, jurisdictions, recorded statuses, priority provenance and coverage limits. Its refresh assessment compares stored references with saved links without calling a provider or changing records. Document content is indexed asynchronously, so a recently created or edited document can take a short while to become searchable; an empty result reflects the current index and does not by itself establish that a matching document is absent.

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
  • query · string · optionnel
    Free-text search query
  • cursor · string · optionnel
    Opaque cursor from a previous search response
  • category · string · optionnel · application | patent | innovation | competitor_application | report | strategy | meeting

  Exemple d'appel

  {"name": "search", "arguments": {"limit": 1, "query": "texte", "cursor": "texte", "category": "application"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"hasMore": true, "results": [], "nextCursor": "texte"}}

• search_public_patents≈ 666 tokens

  Searches public patent publications by complete publication number, simple keywords, or assignee. Returns at most 25 results per page, with source details. Separate from search of saved organisation documents. Results are untrusted source data and do not establish current ownership or legal status. Null expired or abandoned values mean unknown. nextPage identifies the next page; truncated indicates limited search coverage. Search does not import documents. import_patent imports a selected publication.

  Paramètres, retour & exemple (4)

  Paramètres

  • page · integer · optionnel
  • query · string · optionnel
    Simple technology keywords
  • assignee · string · optionnel
    Assignee name to search; results do not establish ownership
  • publicationNumber · string · optionnel
    Search one complete publication number on its own

  Exemple d'appel

  {"name": "search_public_patents", "arguments": {"page": 1, "query": "texte", "assignee": "texte", "publicationNumber": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"page": 1, "total": 1, "status": "results", "results": [], "nextPage": 1, "pageSize": 1, "truncated": true}}

• send_developer_feedback≈ 495 tokens

  Sends feedback the user explicitly wants to share about the Lightbringer tools: broken or surprising tool behaviour, missing capabilities, or friction. Requires the user’s explicit consent to send the proposed report after seeing its text, category and optional tool name and being informed of the recipient. Requires mcp:write permission. Reports go to a human-reviewed Lightbringer engineering Slack channel. Only the report text, category and optional tool name are sent; no account or client metadata is attached. The destination channel is not visible to the signed-in user. Reports contain only the tool issue the user agreed to share, without conversation transcripts, document text, invention details, or other confidential material.

  Paramètres, retour & exemple (3)

  Paramètres

  • category · string · requis · bug | tool_request | general
    The kind of report: bug for broken or surprising behaviour, tool_request for a missing capability, general for anything else
  • feedback · string · requis
    The report text approved by the user for sending: a concise description of the tool issue, without conversation transcripts, document text, invention details, or unrelated task context
  • tool_name · string · optionnel
    The specific tool the report concerns, when there is one

  Exemple d'appel

  {"name": "send_developer_feedback", "arguments": {"category": "bug", "feedback": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "status": "delivered"}}

• set_strategy_publication≈ 410 tokens

  Publishes a strategy or returns it to draft on explicit user request. Published strategies become organisation-wide context for members and Lightbringer agents, including existing competitor monitoring. Publication does not schedule or start monitoring. Multiple strategies may be published simultaneously. Requires strategy management rights.

  Paramètres, retour & exemple (2)

  Paramètres

  • publish · boolean · requis
  • strategy_id · string · requis
    Strategy identifier

  Exemple d'appel

  {"name": "set_strategy_publication", "arguments": {"publish": true, "strategy_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "url": "texte", "kind": "texte", "title": "texte", "refNum": "texte", "status": "texte", "revision": "texte", "sections": []}}

• start_innovation_feedback≈ 932 tokens

  Starts automated analysis of a registered innovation description across clarity, problem framing, completeness, or all focus areas. Returns one task_id, status, progress, available findings and per-analysis errors. Findings contain readable title/description fields; findings_error means findings are unavailable, not absent. Queued or running tasks continue through get_task_status with the same task_id. Succeeded, partially_succeeded and failed are terminal. Ending the wait does not cancel analysis. Separate from novelty assessment, patent search, FTO, attorney review and patent preparation requests.

  Paramètres, retour & exemple (2)

  Paramètres

  • focus · string · optionnel · clarity | problem | completeness | all
    The analysis focus area
  • invention_id · string · requis
    The innovation identifier (invention_id)

  Exemple d'appel

  {"name": "start_innovation_feedback", "arguments": {"invention_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "queued", "results": [], "task_id": "texte", "progress": {}, "expires_at": "texte"}}

• update_asset≈ 846 tokens

  Updates one asset to the supplied state. Currently supports Strategy title and ordered Markdown sections. The input uses the revision and complete section state returned by fetch with include_asset: true; this read depends on the advertised include_asset parameter. Applies atomically at the supplied revision; conflicts require a fresh fetch and reconciliation. Supplying sections replaces the collection: omitted sections are deleted and new sections receive IDs. Unchanged section IDs and comment anchors are preserved. Edits touching pending review changes fail; detached discussions are reported. Requires write consent and Strategy management rights. Does not publish or run a service. Uncertain outcomes require readback and reconciliation before another write.

  Paramètres, retour & exemple (1)

  Paramètres

  • asset · object · requis

  Exemple d'appel

  {"name": "update_asset", "arguments": {"asset": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"asset": {}, "orphaned_discussion_ids": []}}

• update_company_context≈ 546 tokens

  Updates selected profile fields or shared assistant notes in the connected organisation. Requires moderator rights and write consent. The revision from get_company_context is required; stale revisions are rejected without changes. Omitted fields remain unchanged; notes replaces the complete shared notes text and empty strings clear fields. applicant_name updates the legal applicant setting and names an unnamed workspace; it does not rename an established workspace. Returns the saved context and new revision. Does not create or publish a Strategy.

  Paramètres, retour & exemple (2)

  Paramètres

  • updates · object · requis
  • revision · string · requis

  Exemple d'appel

  {"name": "update_company_context", "arguments": {"updates": {}, "revision": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"notes": "texte", "revision": "texte", "can_update": true, "organisation": {}}}

• update_innovation≈ 506 tokens

  Updates one or more sections of an existing innovation record with new content and returns the updated innovation. Overwrites the specified sections.

  Paramètres, retour & exemple (2)

  Paramètres

  • sections · object · requis
    Named invention sections and their full replacement text
  • invention_id · string · requis
    The innovation identifier (invention_id)

  Exemple d'appel

  {"name": "update_innovation", "arguments": {"sections": {}, "invention_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"results": {}}}

• whoami≈ 414 tokens

  Returns the signed-in Lightbringer user and organisation for this connection. Optionally includes up to 20 fellow organisation members with names, roles and a total count, with read consent. An unavailable member lookup is reported separately from the profile.

  Paramètres, retour & exemple (1)

  Paramètres

  • include_members · boolean · optionnel
    Includes a bounded member roster with read consent

  Exemple d'appel

  {"name": "whoami", "arguments": {"include_members": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"user": {}, "members": {}, "organisation": {}, "members_error": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.lightbringer.com/mcp