Atlas / MCP servers / duhlink / Instagram Server Next

Instagram Server NextSAFE

mcp/duhlink/instagram-server-next
Verdict
SAFE
Grade
B
Trust score
85 /100
Exposed tools
3 2r · 1w · 0d
Transport
stdio
License
—
Stars
51
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

A Model Context Protocol (MCP) server for fetching Instagram posts using Chrome's existing login session.

Features

  • Modular architecture with clear separation of concerns
  • Type-safe implementation using TypeScript
  • Improved error handling and logging
  • Configurable through environment variables
  • JSON-RPC 2.0 compliant communication
  • Automatic media downloading and metadata generation
  • SEO-friendly description generation

Architecture

The server follows a modular architecture with the following structure:

src/
├── core/                      # Core MCP functionality
│   ├── mcp/                  # MCP server implementation
│   │   ├── server.ts        # Server class
│   │   ├── stdio.ts         # StdioServerTransport
│   │   └── index.ts         # Barrel exports
│   ├── types/               # Core type definitions
│   │   └── mcp.ts          # MCP types
│   └── utils/               # Utility functions
│       ├── config.ts        # Configuration management
│       └── errors.ts        # Error handling
├── features/                 # Feature modules
│   └── instagram/           # Instagram feature
│       ├── types.ts         # Instagram types
│       ├── utils/           # Feature utilities
│       │   ├── media.ts     # Media handling
│       │   ├── post.ts      # Post processing
│       │   └── seo.ts       # SEO generation
│       └── instagram.service.ts # Instagram service
├── services/                 # Shared services
│   └── browser/             # Browser service
│       ├── types.ts         # Browser types
│       └── browser.service.ts # Browser service
├── index.ts                 # Entry point
└── server.ts                # Main server class

Configuration

The server requires the following environment variables:

  • CHROME_USER_DATA_DIR: Path to Chrome user data directory containing login session

Additional configuration options are available through the config manager:

  • Browser settings (viewport,
Read from source at commit a682c46e48f8OBSERVED · 2026-10-08
Advertisement
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code
claude mcp add instagram-server -- npx -y [email protected]
claude-desktop
{
  "mcpServers": {
    "instagram-server": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ]
    }
  }
}
03

Exposed tools (3)

2 read · 1 write · 0 destructive.

ToolRiskDescription
get_instagram_postsreadGet recent posts from an Instagram profile using existing Chrome login
get_post_datawriteGet detailed data from an Instagram post
get_profile_datareadGet comprehensive data from an Instagram profile
04

Trust audit

SAFEgrade B · trust 85/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codeWARN
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
declared (5 observation(s))
Network
declared (5 observation(s))
Shell
none-observed
Dependencies
not all pinned
Secrets in source
none-found

Findings (9)

MEDIUMNetwork egress · net.raw_ip · CWE-200, CWE-319
src/services/browser/browser.service.ts:72
browserURL: `http://127.0.0.1:${this.config.debugPort}`,
LOWInventory / provenance · inv.hidden_file · CWE-1104
.cline.rules
.cline.rules
Why it matters. hidden member outside the usual dotfiles
Fix. review its purpose
LOWInventory / provenance · inv.no_license · CWE-1104
Why it matters. no LICENSE file and no repo licence
Fix. add a licence
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
src/features/instagram/instagram.mcp.ts:1
import { Server, StdioServerTransport, ErrorCode, McpError, McpRequest } from '../../core/mcp/server';
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
src/features/instagram/instagram.mcp.ts:4
import { ConfigManager } from '../../core/utils/config';
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
src/features/instagram/instagram.service.ts:2
import { IInstagramPost } from '../../core/types/instagram.js';
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
src/features/instagram/instagram.service.ts:3
import { ConfigManager } from '../../core/utils/config.js';
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
src/features/instagram/instagram.service.ts:4
import { InstagramError, handleClassAsyncErrors } from '../../core/utils/errors.js';
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
@modelcontextprotocol/sdk, axios, playwright, puppeteer, zod, @types/debug, @types/node, @typescript-eslint/eslint-plugin
Why it matters. 17 dependency range(s) float
Fix. pin exact versions or ship a lockfile

Gates applied: no_behavioural_pass, no_license.

Audited 2026-10-08 · audit v0.4.1 · source sha a682c46e48f8full audit observations/trust-audit/mcp-server/duhlink__instagram-server-next.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-08a682c46e48f8SAFEB85first audit
06

Questions

What tools does Instagram Server Next expose?

3 in total: 2 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Instagram Server Next safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (85/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.

What credentials does Instagram Server Next need?

No credential environment variables were found in its source, so it appears to need none.

How does Instagram Server Next run?

It speaks stdio, so it runs as a local process your client starts. It is published on npm as instagram-server at 0.2.0.

How current is this page?

The grade is for one exact copy of the source (a682c46e48f8), read on 2026-10-08. The repository is watched and re-audited when it changes.

Advertisement