mcpField
P

Polarity

Local
@radar989Security

About Polarity

Real-time threat intelligence lookups and IOC parsing from your self-hosted Polarity instance.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "radar989-polarity": {
      "command": "npx",
      "args": [
        "-y",
        "@polarityio/mcp-connector"
      ],
      "env": {
        "POLARITY_SERVER_URL": "<POLARITY_SERVER_URL>",
        "POLARITY_TOKEN": "<POLARITY_TOKEN>",
        "POLARITY_IGNORE_SSL": "<POLARITY_IGNORE_SSL>",
        "POLARITY_TIMEOUT_MS": "<POLARITY_TIMEOUT_MS>"
      }
    }
  }
}
Run commandnpx -y @polarityio/mcp-connector
Environment variables to set
POLARITY_SERVER_URLThe base URL of your Polarity server, e.g. https://polarity.yourcompany.com
POLARITY_TOKENSecretA Polarity API key. Generate one in Polarity under Settings > API Keys.
POLARITY_IGNORE_SSLSet to 'true' if your Polarity server uses a self-signed certificate.
POLARITY_TIMEOUT_MSTimeout in milliseconds for Polarity API requests. Defaults to 30000 (30 seconds). Increase for slow integrations.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@polarityio/mcp-connector1.0.1

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.