Developer · Local MCP server
Identity Forge
Design kits, brand naming, and domain research for coding agents.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.identityforge/mcp- Version
- 0.4.6
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-15
- Updated
- 2026-08-15
- Publisher
- io.identityforge
- Namespace
- Namespace verified by the MCP Registry via the domain identityforge.io · how
- Website
- identityforge.io
- Repository
- github.com/KasayoDotCom/identityforge-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | identityforge | 0.4.6 | stdio |
How to connect Identity Forge
Identity Forge runs locally from a Node.js package published to the npm registry: identityforge version 0.4.6. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y identityforge@0.4.6. It reads the environment variable IDENTITYFORGE_API_KEY (secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"identityforge@0.4.6"
],
"env": {
"IDENTITYFORGE_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Idea Reality MCPPre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt - returns 0-100 signal. | Local · stdio |
| Ideabob ValidationScore, validate, and pressure-test startup ideas with AI from Claude or any MCP agent. | Remote · HTTPLive check: ✓ handshake |
| IdencifyWhole-repo code graph for AI agents: impact analysis, dead code, cycles, semantic search - 14 tools. | Remote · HTTP, SSELive check: ✗ no handshake |
| IdentArk GatewayZero-secret MCP gateway for AI agents: risk-scored, audited calls with human-in-the-loop approval. | Remote · HTTPLive check: ✗ no handshake |
| Idig DnsProfessional DNS diagnostics: 14 tools for DNS, DNSSEC, email security, SSL, and propagation. | Remote · SSELive check: ✓ SSE reachable |
| IDLE ProtocolWeb scraping, inference, DNS, monitoring from residential IPs - pay per request in USDC. | Local · stdio |
| Idle9A persistent Linux computer for your AI: what it installs and writes survives the session. | Remote · HTTPLive check: sign-in required |
| IFC MCPLocal IFC/BIM MCP server with IfcOpenShell Python in Pyodide and an IFC viewer. | Local · stdio |