Periscope
MCPB · LINUX-X64
MCP broker into your live Neovim/diver config: LSP, formatters, linters, DAP, MATE attention.
Available components
Last scanned (10 hours ago)
Scores higher than 74% of MCPB servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1138 tokens (~71/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "attention_publish" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Unverified: 2 categories
Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 21 Oct 26 36
First indexed and scored.
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 24 Oct 2026 · Analysed mcpb/https://github.com/qompassai/periscope/releases/download/v0.1.0/periscope-mcp-0.1.0-linux-x64.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
attention_alignment ~64
Alignment between your published focus and a partner agent's focus, measured only inside one saliency snapshot frame (Jaccard overlap, shared targets, shared top). Refused across frames.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The partner agent whose advertised focus to read or compare against. |
No output schema declared.
No examples provided.
attention_decide ~73
Coordination decision against a partner agent's focus: parallel (no contention), serialize (same top target — the named holder proceeds, you defer), or reject (stale frame or invalid focus — re-snapshot, never guess).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The partner agent whose advertised focus to read or compare against. |
No output schema declared.
No examples provided.
attention_focus ~55
Read a partner agent's currently advertised focus (ordered salient targets + the saliency snapshot hash it was computed from) from the coordination board.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The partner agent whose advertised focus to read or compare against. |
No output schema declared.
No examples provided.
attention_publish ~73
Publish your attention focus to the coordination board. The focus document's agent_id must equal your client identity; sequences must strictly advance. Bounded: at most 8 targets.
| Name | Type | Req | Description |
|---|---|---|---|
| focus | object | yes | A focus document: {agent_id, snapshot_hash, seq, targets[]} — ordered salient targets, most salient first. |
No output schema declared.
No examples provided.
broker_status ~30
Report the broker mode (managed or attached), the editor version, its config root, and its working directory.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_definition ~97
Definitions of the symbol at a position, from the editor's attached language servers, merged across clients.
| Name | Type | Req | Description |
|---|---|---|---|
| character | integer | yes | 0-based character offset in UTF-16 code units (the LSP convention). |
| line | integer | yes | 0-based line number. |
| path | string | yes | Absolute path of the file to inspect. It is loaded into the brokered editor (without being displayed) if it is not open yet. |
No output schema declared.
No examples provided.
get_diagnostics ~72
Diagnostics for one file from every source the editor aggregates (language servers and the linter pipeline), each entry naming its producing tool in `source`.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path of the file to inspect. It is loaded into the brokered editor (without being displayed) if it is not open yet. |
No output schema declared.
No examples provided.
get_document_symbols ~63
The symbol outline of one file, flattened with container names, from the editor's attached language servers.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path of the file to inspect. It is loaded into the brokered editor (without being displayed) if it is not open yet. |
No output schema declared.
No examples provided.
get_hover ~99
Hover text (types, documentation) for the symbol at a position, from the editor's attached language servers.
| Name | Type | Req | Description |
|---|---|---|---|
| character | integer | yes | 0-based character offset in UTF-16 code units (the LSP convention). |
| line | integer | yes | 0-based line number. |
| path | string | yes | Absolute path of the file to inspect. It is loaded into the brokered editor (without being displayed) if it is not open yet. |
No output schema declared.
No examples provided.
get_references ~104
References to the symbol at a position, merged across the editor's attached language servers.
| Name | Type | Req | Description |
|---|---|---|---|
| character | integer | yes | 0-based character offset in UTF-16 code units (the LSP convention). |
| include_declaration | boolean | – | – |
| line | integer | yes | 0-based line number. |
| path | string | yes | Absolute path of the file to inspect. It is loaded into the brokered editor (without being displayed) if it is not open yet. |
No output schema declared.
No examples provided.
list_dap ~38
The debug setup the config ships: per-language dap modules, adapters registered with nvim-dap right now, and launch configurations by filetype.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_formatters ~18
Every formatter in the editor config's registry.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_linters ~24
Every linter in the editor config's registry (internal helpers reported separately).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_servers ~26
Every language server the editor config defines, plus the clients active in the editor right now.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_format ~172
Format one file with the editor config's own formatter pipeline and return the result. The formatted text is applied to the brokered editor's buffer and returned in `text`; the file on disk is never written (`written` is always false). With no `formatters`, the filetype's configured pipeline runs (including the pipeline's LSP fallback unless `lsp` is 'never').
| Name | Type | Req | Description |
|---|---|---|---|
| formatters | array | – | Explicit formatter names to run, in order. Omit for the filetype's configured pipeline. |
| lsp | string | – | The pipeline's LSP mode. 'only' cannot be combined with explicit `formatters`. |
| path | string | yes | Absolute path of the file to inspect. It is loaded into the brokered editor (without being displayed) if it is not open yet. |
No output schema declared.
No examples provided.
run_lint ~130
Lint one file with the editor config's own linter runner and return per-linter results: status, exit code, and the diagnostics each linter produced (every diagnostic names its linter in `source`). With no `linters`, the filetype's configured set runs. Nothing is written to disk.
| Name | Type | Req | Description |
|---|---|---|---|
| linters | array | – | Explicit linter names to run. Omit for the filetype's configured set. |
| path | string | yes | Absolute path of the file to inspect. It is loaded into the brokered editor (without being displayed) if it is not open yet. |
No output schema declared.
No examples provided.
How do I install the Periscope MCP server?
Periscope ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, e89eaaedb868ca7825f2d1247608dc74c35911b88d33ff633e2857a6b63952bc; the commands to do that are on this page. If it does not match, do not open it.
mcpb · linux-x64
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
e89eaaedb868ca7825f2d1247608dc74c35911b88d33ff633e2857a6b63952bc
macOS / Linux
echo "e89eaaedb868ca7825f2d1247608dc74c35911b88d33ff633e2857a6b63952bc periscope-mcp-0.1.0-linux-x64.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\periscope-mcp-0.1.0-linux-x64.mcpb).Hash -eq "e89eaaedb868ca7825f2d1247608dc74c35911b88d33ff633e2857a6b63952bc"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the Periscope MCP server?
Periscope is an MCP server listed in the public MCP registry as ai.qompass/periscope. MCP broker into your live Neovim/diver config: LSP, formatters, linters, DAP, MATE attention. This page covers its MCPB bundle (https://github.com/qompassai/periscope/releases/download/v0.1.0/periscope-mcp-0.1.0-linux-x64.mcpb).
Is the Periscope MCP server safe to use?
Periscope scores 36 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 Periscope MCP server expose?
Periscope exposes 16 tools: attention_alignment, attention_decide, attention_focus, attention_publish, broker_status, and 11 more. Their descriptions and schemas cost roughly 1,138 tokens of context every time the server is loaded.
What licence is the Periscope MCP server under?
Periscope declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.