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.

Type Atlas

NPM · @TYPE-ATLAS/MCP

Editor-grade TypeScript, Markdown, and JSON intelligence for coding agents.

Available components

0 this week 87 Trust /100

Last scanned (9 hours ago)

Scores higher than 91% of npm servers

Category Developer Tools

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 Security82
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/client 2.0.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 26 of 124 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 tyler-mitchell/type-atlas). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 69 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
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 9008 tokens (~225/item across 40 items; 40 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 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; "remove_unused_code" implies "remove" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 41 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (16)

  • 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

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.

  • 6 Nov 26 +6
    • Source repository: unverified → pass ▲ security
  • 5 Nov 26 −6
    • Provenance: pass → unverified ▼ security
  • 31 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 28 Oct 26 0
    • GHSA-f897-62hf-6gxq affects this package: high ▼ security
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
  • 26 Oct 26 0
    • Stability: pass → 0.97 functional
  • 21 Oct 26 0
    • CVE-2026-111771 affects this package: high ▼ security
    • CVE-2026-111770 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • CVE-2026-111769 affects this package: high ▼ security
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 6 Nov 2026 · Analysed npm/@type-atlas/mcp@1.0.0

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 tyler-mitchell/type-atlas
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/tyler-mitchell/type-atlas/.github/workflows/release.yml@refs/heads/release
Rekor log index 2634493981
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:85d4656258c4d1cf363b57f5526855a144b123f590c1a5b19bbb3b2535c8017dec7f1c6e02a0d6731a50f3589ad81941f442086936f89b1984ed8a992

Background: How many MCP packages publish verified provenance →

Vulnerabilities 6 findings
ID CVE Severity Vector Fix available
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-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-f897-62hf-6gxq high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-jm63-cq47-j5jp CVE-2026-111770 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:H 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 124 packages
Packages resolved 124
Stale 26
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 40 exposed · ~8,460 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_missing_imports ~148

Return TypeScript's source-wide missing-import fixes as a Codex patch. The MCP does not modify files.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
insertSpacesboolean–Use spaces rather than tabs in TypeScript code-action edits.
tabSizeinteger–Indentation width used by TypeScript code actions.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

callees ~159

Show which callable symbols are invoked directly by the function at a position, grouped with exact call sites. Use this instead of references when tracing outgoing execution flow.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
positionobjectyesSource position to inspect, as { line, character }. Both are one-based, matching what an editor displays. Point at the symbol name itself, not the line start.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

callers ~164

Show which functions call the callable symbol at a position, across every project loaded this session, grouped by caller with exact call sites. Use this instead of references when tracing incoming execution flow.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
positionobjectyesSource position to inspect, as { line, character }. Both are one-based, matching what an editor displays. Point at the symbol name itself, not the line start.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

code_actions ~236

Discover quick fixes and refactors for a range, or resolve a displayed action to a Codex patch. Stable source-wide actions have dedicated tools. The MCP does not modify files.

NameTypeReqDescription
actioninteger–Resolve the corresponding action number from discovery.
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
includeUnavailableboolean–Include actions that the language service marks unavailable.
insertSpacesboolean–Use spaces rather than tabs in TypeScript code-action edits.
only––Restrict discovery to quick fixes or refactors.
rangeobjectyesSource range for action discovery. For refactors, prefer a zero-length cursor at the target expression unless the action requires a selection.
tabSizeinteger–Indentation width used by TypeScript code actions.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

completions ~234

Return a bounded completion page at a source position. Set resolve to include upstream details for that page or raw to return every unresolved candidate.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
limitinteger–Maximum results returned in this page.
offsetinteger–Number of leading results to skip before this page.
positionobjectyesSource position to inspect, as { line, character }. Both are one-based, matching what an editor displays. Point at the symbol name itself, not the line start.
rawboolean–Return every result instead of one page. Potentially very large in a monorepo; prefer paging.
resolveboolean–Resolve documentation and insert details for the returned page. Costs an extra request per candidate.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

compose ~1,094

Answer several questions about code in one call, laid out how you want. `{% ask %}` declares data and renders nothing; the body you write is the answer. Every ask binds `.text`, already rendered exactly as that tool renders it. {% ask "references" as="uses" file="src/x.ts" symbol="foo" /%} {% $uses.text %} Every ask takes `as`. Positional asks take `file` and either `symbol` or one-based `line`+`character`. File and workspace asks take only the attributes shown below. Add `each=<an earlier bind, or a literal list>` to run it once per item, max 10 → { items, total, of, failureCount, text }, each item also carrying `title`. ASKS — further attributes → what it binds besides `text` inspect_symbol(includeSource?, includeTypeDefinitions?, limit?=20) → { symbol, documentation, mentions, callers, callees, implementations, typeDefinitions } hover() → { } subject() → { name, kind, file, at } references(tests?: "only" | "exclude", limit?=50) → { total, shown, beyond, any, files, paths, projects, groups } definitions(limit?=50) → { total, shown, beyond, any, files, paths, hits } type_definitions(limit?=50) → as definitions implementations(limit?=50) → as definitions // a zero can mean unsearched; text says which file_references(limit?=50) → as references // who imports this module callers() → { name, total, any, groups, standardLibrary, projects } // loaded projects callees() → { name, total, any, groups, standardLibrary } // owning project document_symbols(depth?, raw?) → { total, tree } diagnostics(files?: (path | place)[] <= 5) → { total, any, checked, of, groups } read_file(from?, to?) → { lines, startLine } list_files(directory?, glob?: string[], depth?, limit?=500, changed?) → { files, total, any } search_code(query, directory?, limit?=5, snippetLines?=10) → { hits, of, tot…

NameTypeReqDescription
documentstringyesMarkdoc source: ask declarations followed by a body composing what they bind.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

definitions ~134

Return definition locations at a position.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
positionobjectyesSource position to inspect, as { line, character }. Both are one-based, matching what an editor displays. Point at the symbol name itself, not the line start.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

diagnostics ~157

Report diagnostics for the TypeScript projects you have touched — the compiler's own whole-program check, run once per project.

NameTypeReqDescription
limitinteger–Maximum diagnostics returned.
offsetinteger–First diagnostic returned.
projectstring–Which TypeScript project to check, named by its directory or by any path inside it. Only needed when nothing has changed yet; the changed files choose the project otherwise.
scope––changed (files written since this workspace opened, the default) or project (every file in the projects owning them).
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

document_highlights ~138

Return same-document semantic usages at a position.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
positionobjectyesSource position to inspect, as { line, character }. Both are one-based, matching what an editor displays. Point at the symbol name itself, not the line start.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

document_links ~104

Return resolved links discovered by the active language service in a Markdown or JSON document.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

document_symbols ~168

Return the top-level document outline and source ranges. Set depth to include nested symbols or raw to return the complete hierarchy.

NameTypeReqDescription
depthinteger–Levels of nested symbols to include. Defaults to top-level declarations only, which is usually what an agent wants.
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
rawboolean–Return the complete symbol hierarchy, including object properties and anonymous callbacks. Potentially far larger than the source file.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

explore_symbol ~289

Combine exact definitions, types, implementations, callers, calls, and references for one symbol with structurally similar code. Verified relationships and similarity are separate.

NameTypeReqDescription
directorystring–Workspace-relative directory to search, not a file. Narrows results to that subtree; the workspace is indexed either way, so scoping costs nothing.
filestringyesWorkspace-relative or absolute file path.
includeSourceboolean–Include the complete selected symbol body.
includeTypeDefinitionsboolean–Include callable type-definition targets.
limitinteger–Maximum verified relationships shown per section (1-100).
positionobject–Source position of the symbol, as a one-based { line, character }. Pass either this or symbol, not both.
relatedLimitinteger–Maximum retrieval matches returned (1-20).
snippetLinesinteger–Source lines under each similar-code match (0-30). Defaults to pointer rows — location and symbol only — since similarity is a lead to follow, not a preview; raise it to read the matches inline.
symbolstring–Exact document-symbol name in the file. Pass either this or position, not both.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

file_references ~171

Return a bounded page of module references from the TypeScript project selected by file. Set raw to return every project-scoped reference.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
limitinteger–Maximum results returned in this page.
offsetinteger–Number of leading results to skip before this page.
rawboolean–Return every result instead of one page. Potentially very large in a monorepo; prefer paging.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

find_successor ~175

Establish what happened to a symbol that no longer resolves: whether it still exists somewhere, or was withdrawn, and what currently occupies its role. Use this before concluding a capability is gone — a name that returns nothing from search is the case this answers, not evidence of removal.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
limitinteger–Maximum retrieval matches returned (1-20).
modulestring–The module it was imported from, when it had one. Its current surface is the strongest evidence of what replaced it.
namestringyesThe symbol name that no longer resolves.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

fix_all ~148

Return TypeScript's source-wide fix-all action as a Codex patch when applicable. The MCP does not modify files.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
insertSpacesboolean–Use spaces rather than tabs in TypeScript code-action edits.
tabSizeinteger–Indentation width used by TypeScript code actions.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

format_document ~158

Return a Codex patch containing document-formatting edits. The MCP does not modify files.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
insertFinalNewlineboolean–Ensure the file ends with a newline.
insertSpacesboolean–Indent with spaces rather than tabs.
tabSizeinteger–Columns per indentation level.
trimFinalNewlinesboolean–Collapse repeated trailing newlines at the end of the file.
trimTrailingWhitespaceboolean–Remove trailing whitespace from every line.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

hover ~136

Return type and documentation hover at a position.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
positionobjectyesSource position to inspect, as { line, character }. Both are one-based, matching what an editor displays. Point at the symbol name itself, not the line start.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

impact ~143

Experimental: weigh a change to the symbol at a position — uses in loaded projects, grouped by package, with how many sit in tests. Composed for the decision, not the enumeration; references lists the sites themselves.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
positionobjectyesSource position to inspect, as { line, character }. Both are one-based, matching what an editor displays. Point at the symbol name itself, not the line start.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

implementations ~134

Return implementation locations at a position.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
positionobjectyesSource position to inspect, as { line, character }. Both are one-based, matching what an editor displays. Point at the symbol name itself, not the line start.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

inlay_hints ~141

Return inline type and parameter hints for a source range.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
rangeobjectyesSource range as { start, end }, each a one-based { line, character }. Use a zero-length range (start equal to end) to act at a cursor.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

inspect_symbol ~318

Return a bounded working view of a symbol: type and documentation, exact definition/body ranges, distinct implementations and types, callers, direct calls, remaining references, project scope, and optional source. Select by exact file-local symbol name or source position.

NameTypeReqDescription
compactExternalCallsboolean–Summarize dependency and JavaScript runtime call targets while workspace calls retain exact ranges. Pass false for complete external call details.
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
includeSourceboolean–Include the complete symbol body.
includeTypeDefinitionsboolean–Include callable type-definition targets.
limitinteger–Maximum callers, callees, references, and ambiguity candidates shown per section.
positionobject–Source position of the symbol, as a one-based { line, character }. Pass either this or symbol, not both.
scope––Projects searched: workspace (every project loaded this session, default) or project (only the file's owning project). The result states which it used.
symbolstring–Exact document-symbol name in the file, such as createServer. Pass either this or position, not both. Ambiguous matches are returned as candidates.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

investigate_code ~257

Retrieve ranked code for an implementation question and attach verified relationships to the exact identifier match or a bounded set of distinct candidates. Structural similarity is optional and remains separate.

NameTypeReqDescription
candidateLimitinteger–Maximum retrieval matches returned (1-20).
directorystring–Workspace-relative directory to search, not a file. Narrows results to that subtree; the workspace is indexed either way, so scoping costs nothing.
includeSourceboolean–Include complete source for the inspected symbol or symbols.
inspectionLimitinteger–Maximum distinct retrieved candidates given verified relationships (1-5). Exact identifier matches inspect only that symbol.
questionstringyesImplementation question or behavior to investigate.
relatedLimitinteger–Optional structurally similar results derived from the first inspected candidate (0-20).
relationshipLimitinteger–Maximum verified relationships shown per section (1-100).
snippetLinesinteger–Source lines included for each retrieval match (0-30). Read the file at a match for more.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

list_files ~530

Show one bounded workspace-relative file tree rooted at the selected directory, with directories before files. Rows carry `git status` inline with editor-standard letters — `· M +2 -1`, `· R old.ts →`, `· U`, `· 2 changed` on directories — so one call answers structure, reading cost, and working-tree state together; no separate git call is needed to see what changed. Results honor .gitignore, omit dependency and VCS internals, and treat Git submodules as separate workspaces by default.

NameTypeReqDescription
changedboolean–List only paths git reports changed — the whole working-tree delta as one tree, at any depth, without the clean rows around it. depth, glob, and expand do not apply.
depthinteger–Directory levels to include. Defaults to 10 with glob and 1 otherwise.
directorystring–Workspace-relative directory to list.
expandobject–Subtrees to open deeper than the shared depth, in place, within the one tree — like expanding folders in a file explorer. Keys are paths relative to `directory`; values are a depth or an options obje…
gitboolean–Mark git changes with the editor-standard badge letters: `· M +2 -1` modified, `· A +8` added (staged), `· U` untracked, `· R old.ts →` renamed, `· C` conflicted, `· D -12` deleted (ghost rows for de…
globarray–One or more OR-combined Picomatch patterns relative to the selected directory.
includeHiddenboolean–Include paths whose names begin with a dot.
includeIgnoredboolean–Include files matched by applicable .gitignore files.
includeSubmodulesboolean–Descend into Git submodules instead of treating them as separate workspaces.
limitinteger–Maximum files or directories returned.
locboolean–Suffix each file with its line count (`· 244 loc`).
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

list_module_exports ~326

Inspect the usable module surface visible from an importing TypeScript file. Returns runtime signatures by default, declared package subpaths at package roots, nested runtime paths on request, and exported types or their members as opt-ins.

NameTypeReqDescription
fromFilestringyesWorkspace-relative or absolute importing file that determines the exact TypeScript project and package versions.
includeDetailsboolean–Resolve the displayed exports to include signatures and declared shapes.
includeDocsboolean–Include upstream documentation for the displayed exports.
includeSubpathsboolean–Include declared importable subpaths when inspecting a package root.
limitinteger–Maximum exports returned.
modulestringyesModule specifier to inspect, such as react, @scope/package, or ./local-module.js.
offsetinteger–Zero-based offset into the completion results.
patharray–Nested member path to inspect, such as ["d"], ["default"], or ["device"] with an exported type.
querystring–Optional case-insensitive text filter over Volar's completion labels.
surface––Runtime exports by default; use all to include top-level type exports. Nested paths are runtime surfaces.
typestring–Module-scoped exported type expression whose instance members to inspect, such as TgpuRoot or TgpuBuffer<any>. Type-only surfaces are opt-in.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

occurrences ~213

Find exact identifiers or expressions without knowing their files. Identifier queries resolve semantic references; expression queries match AST structure and receive Volar annotations. Use search_code for meaning-based retrieval.

NameTypeReqDescription
limitinteger–Maximum semantic references returned across every resolved symbol.
offsetinteger–Number of leading semantic references to skip across every resolved symbol.
pathstring–Workspace-relative file or directory that bounds candidates and returned uses.
pathsarray–Several files or directories to search together. Pass path or paths.
queriesarray–Several exact identifiers or expressions to resolve in one investigation.
querystring–One exact identifier or expression. Identifiers resolve semantic references; expressions match syntax structurally and receive semantic annotations.
symbolLimitinteger–Maximum distinct canonical symbols inspected across every requested name.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

organize_imports ~146

Return the TypeScript organize-imports action as a Codex patch. The MCP does not modify files.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
insertSpacesboolean–Use spaces rather than tabs in TypeScript code-action edits.
tabSizeinteger–Indentation width used by TypeScript code actions.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

project_config ~71

Return the TypeScript configuration selected for a source file.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

quorl ~186

Expand the transitive reference closure of a symbol, breadth-first, reporting every site with its source line and the declaration enclosing it, plus the frontier that was not expanded. Use before removing or replacing something, when you need the whole blast radius rather than one hop.

NameTypeReqDescription
depthinteger–How many hops of enclosing declarations to follow.
filestringyesWorkspace-relative or absolute file path.
limitinteger–Maximum declarations expanded before the rest are reported as a frontier.
positionobjectyesSource position to inspect, as { line, character }. Both are one-based, matching what an editor displays. Point at the symbol name itself, not the line start.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

read_file ~272

Read one or more UTF-8 text files, including source, Markdown, and JSON, with stable line numbers. Pass every path in one call rather than calling repeatedly. Function bodies fold to their signatures by default; startLine, endLine, and fold apply to every path in the call.

NameTypeReqDescription
endLineinteger–Last inclusive 1-based source line, for entries that do not set their own.
filearrayyesOne or more files to read together: a path, or { path, startLine, endLine, fold } to bound a single file. Mixing both is allowed, as in ["a.ts", { "path": "b.ts", "startLine": 1, "endLine": 40 }].
foldboolean–Fold function bodies to their signatures, for entries that do not set their own.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
startLineinteger–First 1-based source line, for entries that do not set their own.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

references ~249

Return a bounded page of reference locations, across every project loaded this session unless scope narrows it. Set raw to return the complete scope instead of one page.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
limitinteger–Maximum results returned in this page.
offsetinteger–Number of leading results to skip before this page.
positionobjectyesSource position to inspect, as { line, character }. Both are one-based, matching what an editor displays. Point at the symbol name itself, not the line start.
rawboolean–Return every result instead of one page. Potentially very large in a monorepo; prefer paging.
scope––Projects searched: workspace (every project loaded this session, default) or project (only the file's owning project). The result states which it used.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

related_code ~206

Find structurally similar code for a source line and anchor each match to an exact language-server symbol. Similarity is not a call, reference, or runtime relationship.

NameTypeReqDescription
directorystring–Workspace-relative directory to search, not a file. Narrows results to that subtree; the workspace is indexed either way, so scoping costs nothing.
filestringyesWorkspace-relative or absolute file path.
includeTypesboolean–Include hover types and documentation for every match.
limitinteger–Maximum retrieval matches returned (1-20).
lineintegeryesOne-based source line from a search result or known location.
snippetLinesinteger–Source lines included for each retrieval match (0-30). Read the file at a match for more.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

remove_unused_code ~147

Return TypeScript's source-wide unused-code removal as a Codex patch. The MCP does not modify files.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
insertSpacesboolean–Use spaces rather than tabs in TypeScript code-action edits.
tabSizeinteger–Indentation width used by TypeScript code actions.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

rename_files ~95

Return a Codex patch that moves files and updates affected references. The MCP does not modify files.

NameTypeReqDescription
filesarrayyesOne or more { from, to } file moves applied together, so references are updated across the whole set.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

rename_symbol ~140

Return a Codex patch for a TypeScript-project symbol rename at a source position. The MCP does not modify files.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
newNamestringyesNew identifier for the symbol at that position.
positionobjectyesSource position to inspect, as { line, character }. Both are one-based, matching what an editor displays. Point at the symbol name itself, not the line start.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

search_code ~195

Find code by behavior or concept and anchor each match to an exact language-server symbol. The first search of a repository builds its index and takes seconds; later searches answer in milliseconds.

NameTypeReqDescription
directorystring–Workspace-relative directory to search, not a file. Narrows results to that subtree; the workspace is indexed either way, so scoping costs nothing.
includeTypesboolean–Include hover types and documentation for every match.
limitinteger–Maximum retrieval matches returned (1-20).
querystringyesNatural-language behavior, concept, or code to find.
snippetLinesinteger–Source lines included for each retrieval match (0-30). Read the file at a match for more.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

search_dependency_code ~250

Search installed package code and its matching public runtime API without indexing all of node_modules. Use path for a known namespace or type for instance and chained methods. The importing file selects the exact package versions visible to that project.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
limitinteger–Maximum retrieval matches returned (1-20).
packagearrayyesOne to ten installed package names, resolved from the importing file.
patharray–Nested runtime export path to search, such as ["Effect"] or ["default"]. Defaults to the top-level exports.
querystringyesBehavior, concept, or identifier to find in package code.
snippetLinesinteger–Source lines included for each retrieval match (0-30). Read the file at a match for more.
surface––Runtime exports by default; use all when type-only exports are relevant.
typestring–Exported type whose instance or chained methods should be searched.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

selection_ranges ~166

Return the nested structural ranges an editor expands through from one or more source positions.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
positionobject–Source position to inspect, as { line, character }. Both are one-based, matching what an editor displays. Point at the symbol name itself, not the line start.
positionsarray–Source positions to inspect together, each a one-based { line, character }.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

signature_help ~138

Return overload and parameter information at a call site.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
positionobjectyesSource position to inspect, as { line, character }. Both are one-based, matching what an editor displays. Point at the symbol name itself, not the line start.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

type_definitions ~137

Return type-definition locations at a position.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
includeDiagnostics––One of: summary (one complete diagnostic plus file totals), verbose (the full report), off (omit diagnostics).
positionobjectyesSource position to inspect, as { line, character }. Both are one-based, matching what an editor displays. Point at the symbol name itself, not the line start.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

workspace_symbols ~187

Search symbols across TypeScript projects activated in this workspace session. Potentially expensive in large monorepos: each call may search many project files, and limit only bounds returned output. Use document_symbols when the file is known; avoid parallel or repeated speculative searches.

NameTypeReqDescription
filestringyesWorkspace-relative or absolute file path.
limitinteger–Maximum results returned; this does not reduce the underlying workspace search.
offsetinteger–Number of leading results to skip before this page.
querystringyesUse a specific symbol name; avoid broad speculative queries in large workspaces.
rawboolean–Return every matching symbol; potentially very large in monorepos.
workspacestringyesRepository root. This selects the language-server session, so use one stable root per repository rather than a subdirectory. Relative paths resolve from the MCP process working directory.

No output schema declared.

No examples provided.

Install

How do I install the Type Atlas MCP server?

Type Atlas runs locally as an npm package, launched with npx -y @type-atlas/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 · @type-atlas/mcp

# add to Claude Code
claude mcp add tyler-mitchell-type-atlas -- npx -y @type-atlas/mcp
Common questions

What is the Type Atlas MCP server?

Type Atlas is an MCP server listed in the public MCP registry as io.github.tyler-mitchell/type-atlas. Editor-grade TypeScript, Markdown, and JSON intelligence for coding agents. This page covers its npm package (@type-atlas/mcp).

Is the Type Atlas MCP server safe to use?

Type Atlas scores 87 out of 100 on VerifyMCP. We recorded 6 known advisories against it as of 6 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 Type Atlas MCP server expose?

Type Atlas exposes 40 tools: read_file, list_files, diagnostics, document_links, document_symbols, and 35 more. Their descriptions and schemas cost roughly 8,460 tokens of context every time the server is loaded.

Is the Type Atlas MCP server still maintained?

Type Atlas is still listed as active in the MCP registry. We last reached this channel on 6 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 Type Atlas MCP server under?

Type Atlas 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 Type Atlas MCP server?

VerifyMCP ran 16 checks on Type Atlas, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 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.