Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
Trylighthouse is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
95/100
trust score
8
downloads a day
local
runs on your machine
2k
downloads in 30d
What it does
MCP server for the Lighthouse CRM API
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user trylighthouse-mcp '--' npx -y @trylighthouse/mcp-server
# 2 — ask your agent for something these tools do
# lighthouse_crm_get_attributes, lighthouse_crm_get_attribute, lighthouse_crm_create_attribute and 150 more
Trylighthouse costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TRAll 1 server
@trylighthouse1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Trylighthouse as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user trylighthouse-mcp '--' npx -y @trylighthouse/mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
153 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get a lightweight catalog of the fields for a CRM record type: each field
No parameter schema on file.
Get a single custom field definition. Response returns
No parameter schema on file.
Create a new custom field in your CRM workspace.
No parameter schema on file.
Update a custom field
No parameter schema on file.
Delete a custom field and all its data. Only custom fields can be deleted, not system fields.
No parameter schema on file.
Get the available color palette for select/multi_select/status field options.
No parameter schema on file.
Get the allowed values (value, label, color) for a CRM select / multi_select field.
No parameter schema on file.
Add a new option to a select/multi_select field. The option value is auto-generated from the label.
No parameter schema on file.
Delete an option value from a select/multi_select field. Custom options are removed permanently; a system default option is disabled for the workspace instead (re-create it to restore).
No parameter schema on file.
Search and filter records in YOUR CRM workspace (companies, people, or deals you
No parameter schema on file.
Get a single CRM record by ID with all fields and relationships. Custom fields are returned as top-level keys, not nested under an attributes object.
No parameter schema on file.
Read the activity feed of one CRM record, newest first: who changed what, when, and from where. Use it to answer questions about history (\
No parameter schema on file.
Create a new CRM record. Pass all fields (standard + custom) in a single flat data object,
No parameter schema on file.
Update an existing CRM record. Only include the fields you want to change.
No parameter schema on file.
Find-or-create a CRM record by a UNIQUE attribute: if a record already matches the value it is updated, otherwise a new one is created.
No parameter schema on file.
Permanently delete a CRM record. For custom objects, use the object
No parameter schema on file.
Create up to 100 CRM records of the same record_type in one call.
No parameter schema on file.
Update up to 100 CRM records of the same record_type in one call.
No parameter schema on file.
Find-or-create up to 100 records of the same record_type in one call, each matched on a unique attribute.
No parameter schema on file.
Permanently delete up to 100 CRM records of the same record_type in one call.
No parameter schema on file.
Create a new CRM list to organize records. Supports companies, people, deals, and custom objects.
No parameter schema on file.
Get all CRM lists in your workspace.
No parameter schema on file.
Get a single CRM list by ID with its configuration.
No parameter schema on file.
Update a CRM list
No parameter schema on file.
Permanently delete a CRM list.
No parameter schema on file.
Get records in a CRM list with optional filtering, sorting, and view support.
No parameter schema on file.
Add a CRM record to a list. The record type is automatically inferred from the list type.
No parameter schema on file.
Remove a record from a CRM list.
No parameter schema on file.
Add up to 100 CRM records to a list in one call. The record type is inferred from the list type, so every id must be of that type.
No parameter schema on file.
Remove up to 100 CRM records from a list in one call.
No parameter schema on file.
Grant team-level access to a CRM list. Only the list owner can share.
No parameter schema on file.
Revoke team-level access from a CRM list. Only the list owner can revoke.
No parameter schema on file.
Change a CRM list
No parameter schema on file.
Get notes for a CRM record. Each note in the response includes a
No parameter schema on file.
Search ALL notes in the workspace (unlike List Notes, which needs one record). Combine a free-text title search with a CRM-style filter tree and sort.
No parameter schema on file.
Create a note, optionally linked to one or more CRM records. Records are optional: omit them to create a standalone note that still appears in the workspace Notes section.
No parameter schema on file.
Get a single note by ID. Response includes a
No parameter schema on file.
Permanently delete a note and all of its record links.
No parameter schema on file.
Attach a record to an existing note. Call once per record.
No parameter schema on file.
Remove a record link from a note. Call once per record.
No parameter schema on file.
List the workspace
No parameter schema on file.
Create a new note tag in the workspace vocabulary. The tag can then be attached to notes.
No parameter schema on file.
Update a note tag
No parameter schema on file.
Delete a note tag from the workspace vocabulary. The tag is also detached from any notes it was attached to.
No parameter schema on file.
Attach or detach workspace tags on an existing note. Pass operation ADD to attach the tag permalinks, or REMOVE to detach them.
No parameter schema on file.
List CRM tasks with optional filtering and sorting.
No parameter schema on file.
Get a single CRM task by ID.
No parameter schema on file.
Create a CRM task, optionally linked to records and assigned to users.
No parameter schema on file.
Update a CRM task. Provide only fields you want to change.
No parameter schema on file.
Permanently delete a CRM task.
No parameter schema on file.
List folders and files at the workspace root, or inside a specific folder.
No parameter schema on file.
Create a folder. At the workspace root, sharing_status is required.
No parameter schema on file.
Rename, move, or change sharing on a folder. Editors can rename the folder; only owners can move it, change its sharing, or grant team access.
No parameter schema on file.
No parameter schema on file.
Link a folder to a CRM record, associating the whole folder with the record. The folder then appears on the record (in list_record_documents
No parameter schema on file.
Remove a folder→record link. Files inside stop appearing on the record
No parameter schema on file.
Reserve a file row and get a signed upload URL:
No parameter schema on file.
Get file metadata. Response includes my_role (
No parameter schema on file.
Rename, move, or change sharing on a file. Editors can rename/move-between-folders and delete; only the owner can move to root, change sharing, or grant team access.
No parameter schema on file.
Owner or editor (file-level editor OR editor-on-parent-folder) can delete, provided they also have the files.delete workspace permission. Permanently deletes the file and purges the underlying object from storage. Irreversible.
No parameter schema on file.
Make a file appear on a CRM record
No parameter schema on file.
Remove a file→record link.
No parameter schema on file.
List folders and files linked to a CRM record. Returns { folders, files }.
No parameter schema on file.
Get all saved CRM views, or list views scoped to a specific list.
No parameter schema on file.
Update a saved CRM view or list view
No parameter schema on file.
Get a single saved CRM view or list view by ID. Automatically detects the view type.
No parameter schema on file.
Permanently delete a saved CRM view or list view. Automatically detects the view type.
No parameter schema on file.
Get the current authenticated user
No parameter schema on file.
List users in the workspace. Use this to find user IDs for task assignment, note tagging, or filtering by user.
No parameter schema on file.
Get a specific workspace user
No parameter schema on file.
List all teams in the workspace.
No parameter schema on file.
Get a specific team by ID with its members.
No parameter schema on file.
Get a lightweight catalog of the DATA FIELDS discovery results carry for companies or people: each field
No parameter schema on file.
Get the allowed values (value, label, color) for a single discovery select / multi_select field.
No parameter schema on file.
Search Lighthouse
No parameter schema on file.
Search Lighthouse
No parameter schema on file.
No parameter schema on file.
Find people by MEANING, not exact keywords. Describe the ideal person in plain language (their role, skills, the industry they work in, their background) and Lighthouse returns the most semantically similar people from its global database (NOT your CRM), ranked by relevance.
No parameter schema on file.
Look up companies in Lighthouse
No parameter schema on file.
Look up companies in Lighthouse
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Trylighthouse or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 95 / 100
Release 0.2.11 · scanned 15 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score95
Findings1 threat · 9 capability
Capabilitymoderate
Coveragesource
Verificationnone
Surface digestfb7f3402438565942664a00d14b2cf15e7a0f396c94df2537fe53ad6a631aa5e
Score vectorthreat 100 → client 95
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (135 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
3 of the 135 recovered tools are registered only when options.privateEquity !== true is false (build/server.js:3301) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 132.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
132 tools are registered unconditionally · 3 more only when options.privateEquity !== true is false (build/server.js:3301) — typically when a key or option is configured. All 135 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| lighthouse_crm_list_attributes | external-sink | external-sink: handler sends an HTTP POST ( api.post("/mcp/records/attributes") at build/server.js:286 |
| lighthouse_crm_get_attribute | no tags | |
| lighthouse_crm_create_attribute | external-sink | external-sink: handler sends an HTTP POST ( api.post("/attributes") at build/server.js:354 |
| lighthouse_crm_update_attribute | external-sink | external-sink: handler sends an HTTP PATCH ( api.patch(/attributes/${record_type}/${permalink}) at build/server.js:373 |
| lighthouse_crm_delete_attribute | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(/attributes/${params.record_type}/${params.permalink}) at build/server.js:390 |
| lighthouse_crm_list_colors | no tags | |
| lighthouse_crm_list_options | external-sink | external-sink: handler sends an HTTP POST ( api.post("/mcp/records/options") at build/server.js:428 |
| lighthouse_crm_create_option | external-sink | external-sink: handler sends an HTTP POST ( api.post(/options/${record_type}/${permalink}) at build/server.js:451 |
| lighthouse_crm_delete_option | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(`/options/${encodeURIComponent(params.record_type)}/${encodeURIComponent(param…) at build/server.js:469 |
| lighthouse_crm_search_records | no tags | |
| lighthouse_crm_get_record | no tags | |
| lighthouse_crm_list_record_activity | no tags | |
| lighthouse_crm_list_ai_reports | no tags | |
| lighthouse_crm_get_ai_report | no tags | |
| lighthouse_crm_create_record | external-sink | external-sink: handler sends an HTTP POST ( api.post(/records/${params.record_type}) at build/server.js:639 |
| lighthouse_crm_update_record | external-sink | external-sink: handler sends an HTTP PATCH ( api.patch(/records/${params.record_type}/${params.id}) at build/server.js:676 |
| lighthouse_crm_upsert_record | external-sink | external-sink: handler sends an HTTP PUT ( api.put(/records/${params.record_type}?matching_attribute=${params.matching_attribute}) at build/server.js:705 |
| lighthouse_crm_delete_record | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(/records/${params.record_type}/${params.id}) at build/server.js:721 |
| lighthouse_crm_bulk_create_records | external-sink | external-sink: handler sends an HTTP POST ( api.post(/records/${params.record_type}/bulk) at build/server.js:746 |
| lighthouse_crm_bulk_update_records | external-sink | external-sink: handler sends an HTTP PATCH ( api.patch(/records/${params.record_type}/bulk) at build/server.js:773 |
| lighthouse_crm_bulk_upsert_records | external-sink | external-sink: handler sends an HTTP PUT ( api.put(`/records/${params.record_type}/bulk?matching_attribute=${params.matching_attribu…) at build/server.js:802 |
| lighthouse_crm_bulk_delete_records | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(/records/${params.record_type}/bulk) at build/server.js:820 |
| lighthouse_crm_create_list | external-sink | external-sink: handler sends an HTTP POST ( api.post("/lists") at build/server.js:841 |
| lighthouse_crm_list_lists | no tags | |
| lighthouse_crm_get_list | no tags | |
| lighthouse_crm_update_list | external-sink | external-sink: handler sends an HTTP PATCH ( api.patch(/lists/${requireId(list_id, id, "list_id")}) at build/server.js:898 |
| lighthouse_crm_delete_list | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(/lists/${requireId(params.list_id, params.id, "list_id")}) at build/server.js:914 |
| lighthouse_crm_list_list_records | no tags | |
| lighthouse_crm_add_to_list | external-sink | external-sink: handler sends an HTTP POST ( api.post(/lists/${params.list_id}/records) at build/server.js:956 |
| lighthouse_crm_remove_from_list | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(/lists/${params.list_id}/records/${params.record_id}) at build/server.js:974 |
| lighthouse_crm_bulk_add_to_list | external-sink | external-sink: handler sends an HTTP POST ( api.post(/lists/${params.list_id}/records/bulk) at build/server.js:992 |
| lighthouse_crm_bulk_remove_from_list | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(/lists/${params.list_id}/records/bulk) at build/server.js:1009 |
| lighthouse_crm_share_list_with_teams | external-sink | external-sink: handler sends an HTTP POST ( api.post(/lists/${requireId(list_id, id, "list_id")}/teams) at build/server.js:1030 |
| lighthouse_crm_revoke_list_from_teams | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(/lists/${requireId(list_id, id, "list_id")}/teams) at build/server.js:1050 |
| lighthouse_crm_update_list_sharing | external-sink | external-sink: handler sends an HTTP PATCH ( api.patch(/lists/${requireId(list_id, id, "list_id")}/sharing) at build/server.js:1070 |
| lighthouse_crm_list_notes | no tags | |
| lighthouse_crm_search_notes | no tags | |
| lighthouse_crm_create_note | external-sink | external-sink: handler sends an HTTP POST ( api.post("/notes") at build/server.js:1158 |
| lighthouse_crm_get_note | no tags | |
| lighthouse_crm_update_note | external-sink | external-sink: handler sends an HTTP PATCH ( api.patch(/notes/${requireId(note_id, id, "note_id")}) at build/server.js:1205 |
| lighthouse_crm_delete_note | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(/notes/${requireId(params.note_id, params.id, "note_id")}) at build/server.js:1221 |
| lighthouse_crm_link_note_record | external-sink | external-sink: handler sends an HTTP POST ( api.post(/notes/${note_id}/records) at build/server.js:1241 |
| lighthouse_crm_unlink_note_record | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(/notes/${note_id}/records) at build/server.js:1260 |
| lighthouse_crm_list_note_tags | no tags | |
| lighthouse_crm_create_note_tag | external-sink | external-sink: handler sends an HTTP POST ( api.post("/note-tags") at build/server.js:1294 |
| lighthouse_crm_update_note_tag | external-sink | external-sink: handler sends an HTTP PATCH ( api.patch(/note-tags/${permalink}) at build/server.js:1312 |
| lighthouse_crm_delete_note_tag | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(/note-tags/${permalink}) at build/server.js:1327 |
| lighthouse_crm_manage_note_tags | external-sink | external-sink: handler sends an HTTP POST ( api.post(/notes/${note_id}/tags) at build/server.js:1346, handler sends an HTTP DELETE ( api.delete(/notes/${note_id}/tags) at build/server.js:1347 |
| lighthouse_crm_list_tasks | untrusted-input | untrusted-input: keyword "fetch" |
| lighthouse_crm_get_task | no tags | |
| lighthouse_crm_create_task | external-sink | external-sink: handler sends an HTTP POST ( api.post("/tasks") at build/server.js:1418 |
| lighthouse_crm_update_task | external-sink | external-sink: handler sends an HTTP PATCH ( api.patch(/tasks/${id}) at build/server.js:1450 |
| lighthouse_crm_delete_task | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(/tasks/${params.id}) at build/server.js:1465 |
| lighthouse_documents_list | no tags | |
| lighthouse_documents_create_folder | external-sink | external-sink: handler sends an HTTP POST ( api.post(/v1/documents/folders) at build/server.js:1512 |
| lighthouse_documents_get_folder | no tags | |
| lighthouse_documents_update_folder | external-sink | external-sink: handler sends an HTTP PATCH ( api.patch(/v1/documents/folders/${folder_id}) at build/server.js:1556 |
| lighthouse_documents_delete_folder | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(/v1/documents/folders/${params.folder_id}) at build/server.js:1571 |
| lighthouse_documents_link_folder_to_record | external-sink | external-sink: handler sends an HTTP POST ( api.post(/v1/documents/folders/${folder_id}/records) at build/server.js:1590 |
| lighthouse_documents_unlink_folder_from_record | file-writeexternal-sink | file-write: keyword "unlink" in tool name; external-sink: handler sends an HTTP DELETE ( api.delete(/v1/documents/folders/${folder_id}/records) at build/server.js:1608 |
| lighthouse_documents_upload_file | external-sink | external-sink: keyword "upload_file", handler sends an HTTP POST ( api.post(/v1/documents/files/upload-url) at build/server.js:1635 |
| lighthouse_documents_get_file | untrusted-input | untrusted-input: keyword "download" |
| lighthouse_documents_get_file_content | no tags | |
| lighthouse_documents_update_file | external-sink | external-sink: handler sends an HTTP PATCH ( api.patch(/v1/documents/files/${file_id}) at build/server.js:1710 |
| lighthouse_documents_delete_file | file-writeexternal-sink | file-write: keyword "delete_file" in tool name; external-sink: handler sends an HTTP DELETE ( api.delete(/v1/documents/files/${params.file_id}) at build/server.js:1725 |
| lighthouse_documents_link_file_to_record | external-sink | external-sink: handler sends an HTTP POST ( api.post(/v1/documents/files/${file_id}/records) at build/server.js:1743 |
| lighthouse_documents_unlink_file_from_record | file-writeexternal-sink | file-write: keyword "unlink" in tool name; external-sink: handler sends an HTTP DELETE ( api.delete(/v1/documents/files/${file_id}/records) at build/server.js:1761 |
| lighthouse_documents_list_for_record | untrusted-input | untrusted-input: keyword "fetch" |
| lighthouse_crm_list_views | no tags | |
| lighthouse_crm_update_view | external-sink | external-sink: handler sends an HTTP PATCH ( api.patch(/views/${id}) at build/server.js:1846 |
| lighthouse_crm_get_view | no tags | |
| lighthouse_crm_delete_view | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(/views/${params.id}) at build/server.js:1876 |
| lighthouse_workspace_me | no tags | |
| lighthouse_workspace_list_users | no tags | |
| lighthouse_workspace_get_user | no tags | |
| lighthouse_workspace_list_teams | no tags | |
| lighthouse_workspace_get_team | no tags | |
| lighthouse_workspace_list_webhook_subscriptions | external-sink | external-sink: keyword "webhook" |
| lighthouse_workspace_get_webhook_subscription | external-sink | external-sink: keyword "webhook" |
| lighthouse_discovery_list_attributes | external-sink | external-sink: handler sends an HTTP POST ( api.post("/mcp/database/attributes") at build/server.js:2023 |
| lighthouse_discovery_list_options | external-sink | external-sink: handler sends an HTTP POST ( api.post("/mcp/database/options") at build/server.js:2046 |
| lighthouse_discovery_search_companies | no tags | |
| lighthouse_discovery_search_people | no tags | |
| lighthouse_discovery_semantic_search_companies | no tags | |
| lighthouse_discovery_semantic_search_people | no tags | |
| lighthouse_discovery_lookup_by_domain | no tags | |
| lighthouse_discovery_lookup_by_linkedin | no tags | |
| lighthouse_discovery_lookup_people_by_linkedin | no tags | |
| lighthouse_discovery_list_saved_searches | no tags | |
| lighthouse_discovery_list_search_results | no tags | |
| lighthouse_discovery_list_locations | no tags | |
| lighthouse_discovery_list_industries | no tags | |
| lighthouse_discovery_list_tags | no tags | |
| lighthouse_discovery_list_funding_types | no tags | |
| lighthouse_discovery_search_investors | no tags | |
| lighthouse_discovery_search_organizations | no tags | |
| lighthouse_discovery_search_schools | no tags | |
| lighthouse_discovery_search_entities | no tags | |
| lighthouse_discovery_get_company | no tags | |
| lighthouse_discovery_get_person | no tags | |
| lighthouse_discovery_get_company_traction | no tags | |
| lighthouse_discovery_get_company_signals | no tags | |
| lighthouse_discovery_get_person_signals | no tags | |
| lighthouse_discovery_get_entity_by_name | no tags | |
| lighthouse_reports_list_dashboards | no tags | |
| lighthouse_reports_create_dashboard | external-sink | external-sink: handler sends an HTTP POST ( api.post("/dashboards") at build/server.js:2638 |
| lighthouse_reports_get_dashboard | no tags | |
| lighthouse_reports_update_dashboard | external-sink | external-sink: handler sends an HTTP PATCH ( api.patch(/dashboards/${id}) at build/server.js:2680 |
| lighthouse_reports_delete_dashboard | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(/dashboards/${params.id}) at build/server.js:2695 |
| lighthouse_reports_list_widgets | no tags | |
| lighthouse_reports_create_widget | external-sink | external-sink: handler sends an HTTP POST ( api.post(/dashboards/${dashboard_id}/widgets) at build/server.js:2740 |
| lighthouse_reports_update_widget | external-sink | external-sink: handler sends an HTTP PATCH ( api.patch(/dashboards/${dashboard_id}/widgets/${widget_id}) at build/server.js:2761 |
| lighthouse_reports_delete_widget | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(/dashboards/${params.dashboard_id}/widgets/${params.widget_id}) at build/server.js:2777 |
| lighthouse_reports_get_widget_data | untrusted-input | untrusted-input: keyword "fetch" |
| lighthouse_reports_share_dashboard_with_teams | external-sink | external-sink: handler sends an HTTP POST ( api.post(/dashboards/${id}/teams) at build/server.js:2822 |
| lighthouse_reports_revoke_dashboard_from_teams | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(/dashboards/${id}/teams) at build/server.js:2840 |
| lighthouse_crm_share_view_with_teams | external-sink | external-sink: handler sends an HTTP POST ( api.post(/views/${id}/teams) at build/server.js:2865 |
| lighthouse_crm_revoke_view_from_teams | external-sink | external-sink: handler sends an HTTP DELETE ( api.delete(/views/${id}/teams) at build/server.js:2884 |
| lighthouse_crm_update_view_sharing | external-sink | external-sink: handler sends an HTTP PATCH ( api.patch(/views/${id}/sharing) at build/server.js:2908 |
| lighthouse_inbox_email_accounts | no tags | |
| lighthouse_inbox_linkedin_accounts | untrusted-input | untrusted-input: keyword "read_message" |
| lighthouse_inbox_email_threads | no tags | |
| lighthouse_inbox_email_thread | no tags | |
| lighthouse_inbox_email_attachment | no tags | |
| lighthouse_inbox_email_create_draft | external-sink | external-sink: handler sends an HTTP POST ( api.post("/inbox/email/drafts") at build/server.js:3103 |
| lighthouse_inbox_linkedin_chats | no tags | |
| lighthouse_inbox_linkedin_chat_messages | no tags | |
| lighthouse_inbox_calendar_accounts | no tags | |
| lighthouse_inbox_calendar_meetings | no tags | |
| lighthouse_inbox_calendar_meeting | no tags | |
| lighthouse_inbox_calendar_meeting_notes | no tags | |
| lighthouse_inbox_calendar_meeting_transcript | no tags | |
| lighthouse_private_equity_list_saved_searches conditional | no tags | |
| lighthouse_private_equity_list_saved_search_results conditional | no tags | |
| lighthouse_private_equity_get_company conditional | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digestfb7f340243856594
Scanned2026-10-15
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.11. Pin a release below and the command asks for exactly that one.
0.2.11
8 Oct 2026
latestNo release note was published with this version.
0.2.6
3 Oct 2026
No release note was published with this version.
0.2.3
28 Sep 2026
No release note was published with this version.
0.2.1
20 Sep 2026
No release note was published with this version.
0.1.101
18 Sep 2026
No release note was published with this version.
0.1.98
12 Sep 2026
No release note was published with this version.
0.1.95
10 Sep 2026
No release note was published with this version.
0.1.93
3 Sep 2026
No release note was published with this version.
0.1.90
3 Sep 2026
No release note was published with this version.
0.1.87
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Trylighthouse can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.