Claude Connector

Miggo

MCP server for Miggo's public API - query services, endpoints, vulnerabilities, findings, dependencies, and third-party integrations

View in the Claude registry

Brand: Miggo

Category: Security
Primary Subcategory: Application Security & Vulnerability Management

Integration details

Description

Connect Claude to your Miggo security environment. This extension provides 25 tools to explore and analyze your application security posture including services, endpoints, vulnerabilities, findings, dependencies, and third-party integrations. Use natural language to assess risk, investigate threats, onboard security teams, and prioritize remediation across your entire environment.

Integration type: Connector
Verification status: Verified connector
Platform: Claude
Category: Security
Primary Subcategory: Application Security & Vulnerability Management
Secondary Subcategories: None listed
Brand: Miggo
Access: Unknown
First tracked: 2026-08-10
Tool count: 25
Market: US

Agent DiscoverabilityClaude Discoverability Score

Miggo isn’t discoverable through Claude’s Connector picker

It runs as a local Claude Desktop Extension, so Claude cannot surface or score it there today.

No spam. Unsubscribe any time.

What the current score measures

Claude showing a list of relevant Connectors in a conversation

Remote Connectors Claude can surface from the Connector picker.

How this score is measured

Primary Subcategory

Application Security & Vulnerability Management

View Category

ActiveLayerPending VerificationGet notified

Affirmed AIPending VerificationGet notified

AgentAvowPending VerificationGet notified

AgentMart Site CheckPending VerificationGet notified

AI Website SecurityPending VerificationGet notified

—MiggoLocal Extension · Not scored

Tools

25 tools agents can invoke

Count dependencies matching filters — use to answer 'how many vulnerable dependencies do we have?'
Get possible field values for dependency filters — use to discover package ecosystems, vulnerability statuses, and versions in use
Fetch a single dependency by ID — use to inspect a package's version, vulnerabilities, and which services depend on it
Search software dependencies across your services — use for supply-chain audits, license reviews, or finding which services use a specific package
Count endpoints matching filters — use for questions like 'how many public endpoints do we expose?'
Get possible field values for endpoint filters — use to discover available HTTP methods, services, or exposure types
Fetch a single endpoint by ID — use to inspect an endpoint's owning service, exposure level, and associated findings
Search for API endpoints across your environment — use to find internet-facing routes, specific URL patterns, or endpoints by HTTP method
Count findings matching filters — use for executive summaries like 'how many critical findings are open?'
Get possible field values for finding filters — use to see available severity levels, finding types, and statuses
Fetch a single finding by ID — use to get full details on a specific security issue including affected services and remediation context
Search security findings including posture issues, configuration drift, and incidents — use for risk assessments and compliance reviews
Get metadata for the authenticated project — use to confirm which Miggo environment you're connected to and see project-level settings
Count services matching filters — use for quick summaries like 'how many Java services do we run?'
Get possible field values for service filters — use to discover available filter options before searching
Fetch a single service by ID — use to drill into a specific service's details, dependencies, and risk score
Search for services in your Miggo environment — use to inventory running microservices, find services by name or technology, or scope a risk review
Count third-party integrations matching filters — use to answer 'how many external services do we depend on?'
Get possible field values for third-party filters — use to discover known providers and integration types
Fetch a single third-party integration by ID — use to review what services connect to a specific external provider
Search for third-party integrations your services communicate with — use to audit external dependencies and data flows
Count vulnerabilities matching filters — use to answer 'how many critical unpatched CVEs do we have?'
Get possible field values for vulnerability filters — use to discover severity levels, statuses, and affected packages
Fetch a single vulnerability by ID — use to see which services and dependencies are affected by a specific CVE
Search known vulnerabilities (CVEs) across your services — use to check exposure to specific CVEs or prioritize patching by severity

FAQs

Miggo Claude Connector FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve Miggo's Claude Connector discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Miggo alternatives on Claude?

As of 2026-11-02, Miggo competes with CloudBees Unify MCP Server, ActiveLayer, Affirmed AI, AgentAvow, AgentMart Site Check, AI Website Security, Apiiro Guardian, Arcjet and 34 more in Claude Application Security & Vulnerability Management, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.