Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Lightbringer

REMOTE · MCP.LIGHTBRINGER.COM · SCANNED SEP 22

Capture, analyze, validate, and submit inventions, and collaborate on patent reviews.

−4 this week 81 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security92
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2663 tokens (~133/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability check failed: schema churn in the 20 days we've observed: 9 tool removals, 0 breaking changes, 0 auth/transport breaks, 11 additions. See how to fix → Fail
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Install

How do I install the Lightbringer MCP server?

Lightbringer is a hosted endpoint at https://mcp.lightbringer.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.lightbringer.com

# add to Claude Code
claude mcp add --transport http com-lightbringer-connector 'https://mcp.lightbringer.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-lightbringer-connector": {
      "url": "https://mcp.lightbringer.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-lightbringer-connector": {
      "type": "http",
      "url": "https://mcp.lightbringer.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-lightbringer-connector]
url = "https://mcp.lightbringer.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-lightbringer-connector": {
      "type": "remote",
      "url": "https://mcp.lightbringer.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-lightbringer-connector --url 'https://mcp.lightbringer.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-lightbringer-connector:
    url: "https://mcp.lightbringer.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-lightbringer-connector": {
      "Transport": "http",
      "Url": "https://mcp.lightbringer.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-lightbringer-connector -t streamable-http -u 'https://mcp.lightbringer.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-lightbringer-connector": {
      "type": "http",
      "url": "https://mcp.lightbringer.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Sept 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 21 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 20 Sept 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 19 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 18 Sept 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 17 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 16 Sept 26 −7
    • Stability: 0.43 → fail security
    • Schema quality: 114 → 133 functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 15 Sept 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Sept 2026 · Probed https://mcp.lightbringer.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.lightbringer.com CN=WR3,O=Google Trust Services,C=US 14 Aug 2026 12 Nov 2026 RSA 2048 SHA256-RSA 32189f030195dae812dc55f223291750
SANs: mcp.lightbringer.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.lightbringer.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
lightbringer.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer error="invalid_token", error_description="A Bearer access token is required", resource_metadata="https://mcp.lightbringer.com/.well-known/oauth-protected-resource"

Bearer error="invalid_token", error_description="A Bearer access token is required", resource_metadata="https://mcp.lightbringer.com/.well-known/oauth-protected-resource"

Protected resource metadata

Document https://mcp.lightbringer.com/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.lightbringer.com
Authorisation server https://app.lightbringer.com

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.lightbringer.com/mcp Verified 200
http (plaintext) http://mcp.lightbringer.com/mcp HTTPS enforced
MCP tools · 20 exposed · ~2,099 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_comment ~140

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.

NameTypeReqDescription
commentstringyesThe comment text
quoted_textstringyesQuoted passage from the review markdown to anchor on
review_idstringyesThe review identifier
target_user_idsarrayUser identifiers to notify. Identifiers without document access are ignored.
NameTypeReqDescription
anchor
candidatesarray
commentIdstring
hintstring
hintsarray
instructionsstring
mentionedUserIdsarray
replyTostring
statusstringyes

No examples provided.

add_discussion_comment ~99

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.

NameTypeReqDescription
commentstringyesThe comment text
review_idstringyesThe review identifier
NameTypeReqDescription
discussionarrayyes

No examples provided.

delete_task ~78

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.

NameTypeReqDescription
task_idstringyesAutomated task identifier to delete
NameTypeReqDescription
execution_cancelledbooleanyesTracking deletion does not cancel upstream execution.
outcomestringyes
task_idstringyes

No examples provided.

fetch ~116

Returns the full content of a single document — invention, patent application, strategy, or report — identified by its ID. 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.

NameTypeReqDescription
idstringyesThe document identifier
NameTypeReqDescription
idstringyes
metadataobject
partstring
partsarray
textstringyes
titlestringyes
urlstringyes

No examples provided.

get_innovation ~45

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

NameTypeReqDescription
invention_idstringyesThe innovation identifier (invention_id)
NameTypeReqDescription
idstringyes
markdownstringyes
refNumstring|null
titlestringyes
urlstringyes

No examples provided.

get_innovation_template ~60

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
guidancePer-field authoring guidance
schemaMachine-readable invention definition structure
templateDraft template content

No examples provided.

get_review ~192

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.

NameTypeReqDescription
review_idstringyesThe review identifier
NameTypeReqDescription
artifactobjectyes
discussionarrayyes
reviewobjectyes
threadsarrayyes

No examples provided.

get_task_status ~118

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.

NameTypeReqDescription
task_idstringyesThe automated task_id returned by start_innovation_feedback
NameTypeReqDescription
expires_atstringTask expiry in ISO 8601 format: 30 days after creation. Reads do not extend retention.
progressobjectyes
resultsarrayyes
statusstringyes
task_idstringyesThe automated task identifier; shared by start and status responses

No examples provided.

list_innovations ~57

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.

NameTypeReqDescription
querystringFree-text filter on title/reference
NameTypeReqDescription
inventionsarrayyes

No examples provided.

list_reviews ~74

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 report or case under review, and, for report reviews, the invention the report is connected to.

NameTypeReqDescription
statusstringFilter by review status
NameTypeReqDescription
reviewsarrayyes

No examples provided.

list_tasks ~109

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.

NameTypeReqDescription
cursorstringPass next_cursor from the previous list_tasks response unchanged
invention_idstringOptional innovation identifier
limitinteger
NameTypeReqDescription
next_cursoryesOpaque continuation cursor; pass unchanged to list_tasks, even when the page is empty.
tasksarrayyes

No examples provided.

register_innovation ~129

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.

NameTypeReqDescription
definitionobjectyesComplete V1 invention definition matching the advertised field structure; validated during registration
NameTypeReqDescription
idstringyes
refNumstring|null
urlstringyes
warningsNon-blocking notices about the saved innovation; registration succeeded despite these warnings

No examples provided.

reply_to_comment ~97

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.

NameTypeReqDescription
commentstringyesThe reply text
comment_idstringyesThe comment thread identifier
review_idstringyesThe review identifier
target_user_idsarrayUser identifiers to notify. Identifiers without target access are ignored.
NameTypeReqDescription
commentIdstringyes
mentionedUserIdsarray

No examples provided.

request_patent_preparation ~108

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 inventor. 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.

NameTypeReqDescription
invention_idstringyesThe innovation identifier (invention_id)
NameTypeReqDescription
idstringyes
outcomestringyesWhether patent preparation was newly requested or was already requested; neither confirms completion or filing
refNumstring|null
urlstringyes

No examples provided.

respond_to_review ~100

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.

NameTypeReqDescription
messagestringThe review response message
responsestringyesThe review response value
review_idstringyesThe review identifier
NameTypeReqDescription
reviewobjectyes

No examples provided.

search ~161

Searches the Lightbringer organisation's documents (inventions, patent applications, and reports). 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. 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.

NameTypeReqDescription
categorystring
cursorstringOpaque cursor from a previous search response
limitinteger
querystringFree-text search query
NameTypeReqDescription
hasMoreboolean
nextCursorstring|null
resultsarrayyes

No examples provided.

send_developer_feedback ~186

Sends a report about the Lightbringer tools themselves to the engineering team: broken or surprising tool behaviour, missing capabilities, or friction encountered while working. Reports are sent to a human-reviewed engineering Slack channel, together with user, organisation, and connected-client identifiers and organisation name when available, and are not visible to the signed-in user. A good report stays high-level — the goal, the approach, the obstacle — and leaves out document text, invention details, and other confidential material.

NameTypeReqDescription
categorystringyesThe kind of report: bug for broken or surprising behaviour, tool_request for a missing capability, general for anything else
feedbackstringyesWhat was being attempted, how, and what got in the way — high-level, without document text or invention details
tool_namestringThe specific tool the report concerns, when there is one
NameTypeReqDescription
notestringyes
statusstringyes

No examples provided.

start_innovation_feedback ~144

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.

NameTypeReqDescription
focusstringThe analysis focus area
invention_idstringyesThe innovation identifier (invention_id)
NameTypeReqDescription
expires_atstringTask expiry in ISO 8601 format: 30 days after creation. Reads do not extend retention.
progressobjectyes
resultsarrayyes
statusstringyes
task_idstringyesThe automated task identifier; shared by start and status responses

No examples provided.

update_innovation ~64

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

NameTypeReqDescription
invention_idstringyesThe innovation identifier (invention_id)
sectionsobjectyesNamed invention sections and their full replacement text
NameTypeReqDescription
resultsobjectyes

No examples provided.

whoami ~22

Returns the signed-in Lightbringer user and organisation for this connection.

Input schema present but exposes no named parameters.

NameTypeReqDescription
organisationobjectyes
userobjectyes

No examples provided.

Common questions

What is the Lightbringer MCP server?

Lightbringer is an MCP server listed in the public MCP registry as com.lightbringer/connector. Capture, analyze, validate, and submit inventions, and collaborate on patent reviews. This page covers its hosted endpoint (https://mcp.lightbringer.com/mcp).

Is the Lightbringer MCP server safe to use?

Lightbringer scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Lightbringer MCP server expose?

Lightbringer exposes 20 tools: whoami, list_innovations, get_innovation, update_innovation, request_patent_preparation, and 15 more. Their descriptions and schemas cost roughly 2,099 tokens of context every time the server is loaded.

Does the Lightbringer MCP server require authentication?

Yes. Lightbringer asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Lightbringer MCP server still maintained?

Lightbringer is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.