Enhanced MCP server for Limitless Pendant with advanced conversation analysis, meeting detection, action item extraction, and comprehensive
Free
Nothing to run from here
Libscope 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.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
AI-powered knowledge base with MCP integration — query library docs, internal wikis, and topics with semantic search
Quickstart
# 1 — run it from where its publisher ships it
npx -y libscope
# 2 — ask your agent something
> AI-powered knowledge base with MCP integration — query library docs, internal wikis, and topics with semantic search
Libscope is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
ROAll 1 server
robertld1 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 Libscope 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. It is scanned, signed and pinned to the version you choose — 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. Claude Code registers it in one command.
claude mcp add libscope-mcp -- npx -y libscopeReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
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
33 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.
Semantic search across all indexed documentation, library docs, and topics
Takes no parameters.
Example callreturns →
Find chunks semantically similar to a given chunk (more-like-this). Returns related content seeded from an existing chunk
Takes no parameters.
Example callreturns →
Retrieve a specific document by its ID
Takes no parameters.
Example callreturns →
Delete a document from the knowledge base by its ID
Takes no parameters.
Example callreturns →
Update an existing document
Takes no parameters.
Example callreturns →
Rate a document or suggest corrections. Use this when documentation appears outdated, incorrect, or particularly helpful.
Takes no parameters.
Example callreturns →
Submit a new document for indexing into the knowledge base. You can provide content directly, or provide a URL to fetch and index automatically. Set spider=true to crawl linked pages from the URL.
Takes no parameters.
Example callreturns →
List available documentation topics
Takes no parameters.
Example callreturns →
Check the health of the LibScope server, including database connectivity, document and chunk counts, and FTS5 index status
Takes no parameters.
Example callreturns →
List all indexed documents with optional filters
Takes no parameters.
Example callreturns →
Ask a question and get an LLM-synthesized answer based on indexed documentation (RAG)
Takes no parameters.
Example callreturns →
Re-embed all document chunks with the current embedding model. Use after switching embedding providers to update vectors without re-fetching content.
Takes no parameters.
Example callreturns →
Sync Slack channel messages and threads into the knowledge base
Takes no parameters.
Example callreturns →
Install a knowledge pack from the registry or a local file path
Takes no parameters.
Example callreturns →
List installed knowledge packs or available packs from the registry
Takes no parameters.
Example callreturns →
Sync OneNote notebooks via Microsoft Graph API
Takes no parameters.
Example callreturns →
Sync pages and databases from a connected Notion workspace into the knowledge base
Takes no parameters.
Example callreturns →
Sync an Obsidian vault into the knowledge base. Parses wikilinks, frontmatter, embeds, and tags with incremental sync support.
Takes no parameters.
Example callreturns →
Sync Confluence spaces and pages into the knowledge base
Takes no parameters.
Example callreturns →
View search analytics dashboard and knowledge gap detection
Takes no parameters.
Example callreturns →
Create a relationship between two documents (see_also, prerequisite, supersedes, related)
Takes no parameters.
Example callreturns →
Get all cross-reference links for a document (both outgoing and incoming)
Takes no parameters.
Example callreturns →
Remove a cross-reference link between documents
Takes no parameters.
Example callreturns →
Save a search query with optional filters for later re-use
Takes no parameters.
Example callreturns →
Suggest tags for a document based on content analysis
Takes no parameters.
Example callreturns →
List all saved searches
Takes no parameters.
Example callreturns →
Execute a saved search by name or ID and return results
Takes no parameters.
Example callreturns →
Delete a saved search by name or ID
Takes no parameters.
Example callreturns →
Register a webhook to receive notifications for document events
Takes no parameters.
Example callreturns →
List all registered webhooks
Takes no parameters.
Example callreturns →
Remove a registered webhook by ID
Takes no parameters.
Example callreturns →
Get the current status, progress, and result of an async background task
Takes no parameters.
Example callreturns →
Request cancellation of a pending or running async background task
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Libscope costs nothing to install and nothing to call, 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: $8.42
$16.58 left
ATrust score 94 / 100
Release 1.8.0 · scanned 26 Aug 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 score94
Findings2 threat · 4 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest3d94e9406d11794936a96620e827591036f97443497643763ec0fe3d4b55fbec
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| 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 (31 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>".
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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search-docs | no tags | |
| get-related | no tags | |
| get-document | no tags | |
| delete-document | no tags | |
| update-document | no tags | |
| rate-document | no tags | |
| submit-document | untrusted-input | |
| list-topics | no tags | |
| health-check | no tags | |
| list-documents | no tags | |
| ask-question | no tags | |
| reindex-documents | no tags | |
| sync-slack | no tags | |
| install-pack | no tags | |
| list-packs | no tags | |
| sync-onenote | no tags | |
| sync-notion | no tags | |
| sync-obsidian-vault | no tags | |
| sync-confluence | no tags | |
| search-analytics | no tags | |
| link-documents | no tags | |
| get-document-links | no tags | |
| delete-link | no tags | |
| save-search | no tags | |
| suggest-tags | no tags | |
| list-saved-searches | no tags | |
| run-saved-search | no tags | |
| delete-saved-search | no tags | |
| create-webhook | external-sink | |
| list-webhooks | no tags | |
| delete-webhook | external-sink |
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.
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest3d94e9406d117949
Scanned2026-08-26
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
Pinned to 1.8.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
1.8.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Libscope in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
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 an account with 50 real tool calls against it.