com.namingsignal/naming-signal MCP server
Checked 2026-09-07. Alive: yes. Handshake: gated.
Category: ai-ml. API and field schema.
Facts
| id | moekoelueker--namingsignal |
| name | com.namingsignal/naming-signal |
| registry_name | com.namingsignal/naming-signal |
| repo_url | https://github.com/moekoelueker/namingsignal |
| endpoint_url | https://namingsignal.com/mcp |
| transport | mixed |
| alive | yes |
| liveness_reason | not available |
| check_reachable | yes |
| check_recent_commit | yes |
| check_installable | yes |
| handshake_status | gated |
| handshake_checked_at | 2026-09-07T18:08:24Z |
| handshake_protocol_version | not available |
| handshake_auth_hint | Bearer realm="NamingSignal", error="invalid_token", error_description="Create a NamingSignal API key at https://namingsignal.com/developers" |
| handshake_auth_discoverable | url |
| handshake_failure_layer | none |
| handshake_latency_ms | 954 |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | slow |
| last_commit_at | 2026-07-14T13:55:13Z |
| category | ai-ml |
| license_spdx | MIT |
How to install or connect
Connect your MCP client to https://namingsignal.com/mcp.
What the checks mean
alive combines the applicable repository, package, and endpoint checks. A null result is not verifiable, not a failure. The MCP handshake is a separate structural probe and is not a security audit. Read the methodology.