MCP Server
MCP
com.namingsignal/naming-signal
Evidence-first naming: briefs, sprints, exact domain checks, finalist research. Read-only.
Install
npx -y @namingsignal/[email protected]Configuration Example
{
"remotes": [
{
"type": "streamable-http",
"url": "https://namingsignal.com/mcp",
"headers": [
{
"description": "Bearer <NamingSignal user API key>. Create and revoke keys at https://namingsignal.com/developers. Every tool call is metered and rate limited through the account attached to the key.",
"isRequired": true,
"isSecret": true,
"name": "Authorization"
}
]
}
],
"packages": [
{
"registryType": "npm",
"registryBaseUrl": "https://registry.npmjs.org",
"identifier": "@namingsignal/mcp",
"version": "0.2.0",
"transport": {
"type": "stdio"
},
"environmentVariables": [
{
"description": "NamingSignal user API key created at https://namingsignal.com/developers. Required for hosted tool calls.",
"isRequired": true,
"isSecret": true,
"name": "NAMING_SIGNAL_API_KEY"
},
{
"description": "API origin. Defaults to https://namingsignal.com; set http://localhost:3000 for a local development server.",
"default": "https://namingsignal.com",
"name": "NAMING_SIGNAL_API_URL"
}
]
}
]
}
mcp
model-context-protocol
streamable-http
npm
Comments
Sign in to leave a comment