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.

behold

NPM · @INTENTIUS/BEHOLD

Your infrastructure repo as a graph, from the files. Draws Terraform roots, no state needed.

Available components

+18 this week 77 Trust /100

Last scanned (11 hours ago)

Scores higher than 55% of npm servers

Category Cloud Infrastructure

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.1, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 43 of 168 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to INTENTIUS/behold). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3378 tokens (~482/item across 7 items; 6 tools + 1 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
What we tested

Checks we ran (17)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 21 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: fail → unverified ▼ security
    • Dependency health: 0.90 → unverified ▼ functional
    • Package version: 0.34.2 → 0.34.4 functional
    • Package version: 0.34.2 → 0.34.3 functional
  • 19 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 18 Nov 26 −15
    • Known CVEs: fail → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Dependency health: 0.91 → unverified ▼ functional
    • Package version: 0.33.3 → 0.34.2 functional
    • Package version: 0.33.3 → 0.34.1 functional
    • Package version: 0.33.3 → 0.34.0 functional
  • 17 Nov 26 +21
    • Known CVEs: unverified → fail ▼ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: unverified → 0.91 ▲ functional
  • 16 Nov 26 −5
    • Tool safety: pass → unverified ▼ security
    • Known CVEs: fail → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Dependency health: 0.90 → unverified ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.32.0 → 0.33.3 functional
    • Package version: 0.32.0 → 0.33.2 functional
    • Package version: 0.32.0 → 0.33.1 functional
    • Package version: 0.32.0 → 0.33.0 functional
  • 15 Nov 26 59

    First indexed and scored.

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 Nov 2026 · Analysed npm/@intentius/behold@0.34.4

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo INTENTIUS/behold
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/INTENTIUS/behold/.github/workflows/release.yml@refs/heads/main
Rekor log index 4034112256
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:1bd4a110d801f8ed7fdd8e1a908169f7f46bd9ebea63086b8fdb59ff07b98761366158e5fd7c01f47eb151647225f9d312bbc0df5a62f3cf34101e0d4

Background: How many MCP packages publish verified provenance →

Vulnerabilities 5 findings
ID CVE Severity Vector Fix available
GHSA-22jm-h49p-29qw CVE-2026-111767 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-46jr-4wx8-v453 CVE-2026-111768 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-6qxp-vccf-f47h CVE-2026-104850 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-rvq5-wwqv-78pq CVE-2026-111771 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 168 packages
Packages resolved 168
Stale 43
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~3,197 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
ask ~1,213

Ask a chant search query of the estate behold serves, and get chant's answer: its read-contract search document, verbatim, with `link` (the behold view that draws it) and `drawn: false` added. ask never moves the person's tab; use show for that. On a declared workspace the document is chant workspace search's, with every member's rows as <member>/<id>; on one project or a Terraform folder it is chant search --json's. Uses the running behold serve of this project; with none, behold answers in this process. Needs chant 0.124.46 or newer. Which demo questions it answers: "what's in here?" is countBy kind with the query kind:aws_ (or empty); "how many resources does each module own, by type?" is countBy module, then countBy kind with the query narrowed to a module; "what would this change do, and why does it replace the database?" is plan with the query attr:planAction=replace and show planActions,planReplacePaths,planActionReason. Beside a chant search query, ask takes cypher (a read-only Cypher query over every member's graph and every index in one LadybugDB, behold#1027) or resource (resolve a name, id, address or cloud id, then a template). The query is chant's search grammar, unchanged (https://intentius.io/chant/cli/search/). env reads that environment live (chant search --live --env <env>); snapshot with env replays a recorded snapshot instead (chant --snapshot <ref>, such as latest); chant's --explain is always on, for the near-misses drawn. It takes no --check-live or --check-snapshot (drift is not drawn), and no --ambient, --src or --fail-on-drift. Read the capabilities tool first: it lists the capabilities a cap: term asks (cap:internet-reachable(22), ->[cap=network]), each one's meaning, parameters and rule (INTENTIUS/chant#4375).

NameTypeReqDescription
countBystring–Group the matches the way chant search --count-by does: kind, module or attr:<name> (behold#922). The answer is chant's groups and total; the view lights each group's cards and labels the group with…
cypherstring–A read-only Cypher query over the graph pane's database (behold#1027): every member's chant IR, every engine graph document (choudoufu, plunge) and every index version, in one LadybugDB. Tables: Reso…
envstring–The environment whose live state the view shows. Without it, the declared source.
inputsstring–With template: its inputs as a JSON object of strings ({"kind": "aws_internet_gateway"}).
paramsstring–With cypher: its parameters, as a JSON object ({"k": "aws_s3_bucket"} for $k). Values are strings, numbers, booleans or null.
planboolean–The plan read (behold#922): the query is answered at the plan depth (CHANT_TERRAFORM_OBSERVE=plan, chant search --live --env), and the cards carry each Terraform root's planAction, planActions, planR…
querystring–A chant search query whose matches the view lights, such as `attr:internetFacing=true`.
resourcestring–Start from a resource (behold#1022): a name, an IR id, a block address or a cloud id (an ARN, an instance id, a Kubernetes UID). The answer is one node or the candidates, with the investigation templ…
showstring–Comma-separated attributes to carry on each row (chant search --show).
snapshotstring–With env: a recorded snapshot to show instead of a live read (latest, or a ref chant lists). Not with plan.
templatestring–With resource that resolves to one node: run one of the templates resolve lists for that node, by name. They are chant's and the project's own (.chant/templates.json), each with its origin; ask with…

No output schema declared.

No examples provided.

capabilities ~177

Read this first. The capability catalog chant answers cap: terms with, for the estate behold serves: chant's read-contract capabilities document, verbatim (chant search --capabilities --json, INTENTIUS/chant#4375; chant workspace search --capabilities --json on a declared workspace). Each capability has its name, what it means, its parameters, the search term that asks it (cap:internet-reachable, ->[cap=network]), the questions it answers, what it does not evaluate, its rule, and which lexicons supply it. Then ask with that term; a cap: match's path is in its because hops, and show draws it. Uses the running behold serve of this project; with none, behold answers in this process. Takes no arguments. Needs chant 0.124.46 or newer.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

graph ~404

Draw the repository as a graph, or a cut of it. A host that renders MCP Apps shows the interactive view inline; every other host gets this answer: how many roots, cards and edges, the cut asked for, a Mermaid diagram when it fits (else a table of roots with card counts), and a link to the running behold serve at that view. The answer holds no document JSON, and no card list when the diagram does not fit. For a big estate ask again with around, a root or card id from the table, to see one part. Reads the files and git objects in this process; it needs no serve and no chant search. dir is a folder inside the project (default: the project). around takes comma-separated card or box ids and cuts to them and what is within depth hops (default 1); direction up follows what they depend on, down what depends on them. changed takes <base>..<head> (or <base>...<head> from the merge base) and cuts to what changed between the two commits, each card marked added, removed, changed or neighbour. around and changed are two cuts: give one.

NameTypeReqDescription
aroundstring–Comma-separated card or box ids to cut around (a root such as a Terraform root, or a card id from the roots table), with what is within depth hops of them.
changedstring–A revision range, <base>..<head> or <base>...<head> (from the merge base): cut to what changed between the two commits and the cards within depth hops.
depthinteger–Hops from the cards around names, or from what changed (default 1).
dirstring–A folder inside the project to read, relative to it (default: the project folder).
directionstring–With around: up follows what the cards depend on, down what depends on them (default both).

No output schema declared.

No examples provided.

graph_document ~220

For the graph view only, not for a model: the behold-graph/1 document of a graph call, taking the same arguments, so the view can draw it. The model is never offered this tool, and its answer never enters the conversation.

NameTypeReqDescription
aroundstring–Comma-separated card or box ids to cut around (a root such as a Terraform root, or a card id from the roots table), with what is within depth hops of them.
changedstring–A revision range, <base>..<head> or <base>...<head> (from the merge base): cut to what changed between the two commits and the cards within depth hops.
depthinteger–Hops from the cards around names, or from what changed (default 1).
dirstring–A folder inside the project to read, relative to it (default: the project folder).
directionstring–With around: up follows what the cards depend on, down what depends on them (default both).

No output schema declared.

No examples provided.

shot ~609

A PNG of a view, framed on the query's matches, and the link to the same view. Returns the image inline. Uses the running behold serve of this project; with none, it starts behold in this process for the shot and stops it after. Needs the optional peer playwright-core and a browser; without them it refuses with the install line. Writes no file. Without a query, node or focus frames the view's own selection. The query is chant's search grammar, unchanged (https://intentius.io/chant/cli/search/). env reads that environment live (chant search --live --env <env>); snapshot with env replays a recorded snapshot instead (chant --snapshot <ref>, such as latest); chant's --explain is always on, for the near-misses drawn. It takes no --check-live or --check-snapshot (drift is not drawn), and no --ambient, --src or --fail-on-drift. Read the capabilities tool first: it lists the capabilities a cap: term asks (cap:internet-reachable(22), ->[cap=network]), each one's meaning, parameters and rule (INTENTIUS/chant#4375).

NameTypeReqDescription
countBystring–Group the matches the way chant search --count-by does: kind, module or attr:<name> (behold#922). The answer is chant's groups and total; the view lights each group's cards and labels the group with…
envstring–The environment whose live state the view shows. Without it, the declared source.
focusstring–Comma-separated box ids to keep at full weight; the rest dims.
heightinteger–The page's height in px (default 1000).
memberstring–Show one estate member.
nodestring–A card to select, by behold's node id.
planboolean–The plan read (behold#922): the query is answered at the plan depth (CHANT_TERRAFORM_OBSERVE=plan, chant search --live --env), and the cards carry each Terraform root's planAction, planActions, planR…
querystring–A chant search query whose matches the view lights, such as `attr:internetFacing=true`.
snapshotstring–With env: a recorded snapshot to show instead of a live read (latest, or a ref chant lists). Not with plan.
widthinteger–The page's width in px (default 1600).
zoomstring–The zoom: components, resources, attributes, or another behold offers.

No output schema declared.

No examples provided.

show ~574

Move the person's open behold tab to a view: the query's matches lit and the rest dimmed, in the env or snapshot asked for. The tab says an agent moved it and keeps the view it left one Back away. It changes nothing but what the tab shows. Needs a running behold serve of this project; with none, it refuses and names the command that starts one. With no tab open it answers the link to hand the person. The query is chant's search grammar, unchanged (https://intentius.io/chant/cli/search/). env reads that environment live (chant search --live --env <env>); snapshot with env replays a recorded snapshot instead (chant --snapshot <ref>, such as latest); chant's --explain is always on, for the near-misses drawn. It takes no --check-live or --check-snapshot (drift is not drawn), and no --ambient, --src or --fail-on-drift. Read the capabilities tool first: it lists the capabilities a cap: term asks (cap:internet-reachable(22), ->[cap=network]), each one's meaning, parameters and rule (INTENTIUS/chant#4375).

NameTypeReqDescription
countBystring–Group the matches the way chant search --count-by does: kind, module or attr:<name> (behold#922). The answer is chant's groups and total; the view lights each group's cards and labels the group with…
envstring–The environment whose live state the view shows. Without it, the declared source.
focusstring–Comma-separated box ids to keep at full weight; the rest dims.
memberstring–Show one estate member.
nodestring–A card to select, by behold's node id.
planboolean–The plan read (behold#922): the query is answered at the plan depth (CHANT_TERRAFORM_OBSERVE=plan, chant search --live --env), and the cards carry each Terraform root's planAction, planActions, planR…
querystring–A chant search query whose matches the view lights, such as `attr:internetFacing=true`.
snapshotstring–With env: a recorded snapshot to show instead of a live read (latest, or a ref chant lists). Not with plan.
zoomstring–The zoom: components, resources, attributes, or another behold offers.

No output schema declared.

No examples provided.

Install

How do I install the behold MCP server?

behold runs locally as an npm package, launched with npx -y @intentius/behold mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @intentius/behold

# add to Claude Code
claude mcp add intentius-behold -- npx -y @intentius/behold mcp
Common questions

What is the behold MCP server?

behold is an MCP server listed in the public MCP registry as io.github.INTENTIUS/behold. Your infrastructure repo as a graph, from the files. Draws Terraform roots, no state needed. This page covers its npm package (@intentius/behold).

Is the behold MCP server safe to use?

behold scores 77 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 22 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 behold MCP server expose?

behold exposes 6 tools: ask, show, shot, capabilities, graph, graph_document. Their descriptions and schemas cost roughly 3,197 tokens of context every time the server is loaded.

Is the behold MCP server still maintained?

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

What licence is the behold MCP server under?

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

What did VerifyMCP test on the behold MCP server?

VerifyMCP ran 17 checks on behold, covering Malware scan, Known CVEs, Install scripts, Dependency health and 13 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.