Other · Local MCP server
Intended
Intended's authority layer as MCP tools: ALLOW/ESCALATE/DENY decisions with signed tokens.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.intended-so/intended- Version
- 0.1.1
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- intended-so (GitHub)
- Repository
- github.com/intended-so/intended (folder packages/mcp-server)
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @intended-inc/mcp-server | 0.1.1 | stdio |
How to connect Intended
Intended runs locally from a Node.js package published to the npm registry: @intended-inc/mcp-server version 0.1.1. 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 @intended-inc/mcp-server@0.1.1. It reads these environment variables: INTENDED_API_KEY (required, secret), INTENDED_TENANT_ID (required) and INTENDED_API_URL; set them 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": {
"intended": {
"command": "npx",
"args": [
"-y",
"@intended-inc/mcp-server@0.1.1"
],
"env": {
"INTENDED_API_KEY": "<secret>",
"INTENDED_TENANT_ID": "<value>",
"INTENDED_API_URL": "<value>"
}
}
}
}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 other servers
| Server | Runs |
|---|---|
| IntelliboardKanban do Intelliboard por MCP: handoff entre agentes e validação imposta antes de concluir. | Local · stdio |
| Intelligence GatewayUnified MCP gateway to Algeria TKAWEN ecosystem: commerce, certification and AI tools. | Remote · HTTP |
| Intelthreadlinqs MCPThreadlinqs threat-intelligence MCP — 73 tools: threats, detections, IOCs, actors, C2, MITRE, CVEs. | Local · stdio |
| IntenCheckPsychological text analysis: tone, emotions, communication style, multilingual replies. | Remote · HTTP |
| Intent EngineeringAudit, scaffold, and triage agent intent specs against a 9-section template. | Local · stdio |
| Intent HubBook a local business by saying what you need; matching businesses bid and you confirm one. | Remote · HTTP |
| Intent-Verified Development (IVD)33 tools that make AI write, implement, and verify intent against explicit, testable constraints. | Remote · HTTP |
| InterAI Risk OraclePre-execution policy gate for consequential agent actions with durable trust receipts. | Remote · HTTP |