LLM Pulse
io.github.LLM-Pulse/llmpulse-mcpVersion 1.0.0AI visibility analytics for brand mentions, citations, sentiment, and GEO reports
Status
Sign-in required183 msReachable. It asks for authorization, so we did not look inside.- Last checked
- Nov 14, 2026, 14:39 UTC
- Latency
- 183 ms
- Remotes responding
- 1 of 1
- Sign-in
- OAuth sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://api.llmpulse.ai/api/v1/mcpSign-in required183 msOAuth sign-in
Claude Code
This server asks for sign-in. Your client opens the sign-in when it connects.
claude mcp add --transport http llmpulse-mcp https://api.llmpulse.ai/api/v1/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'Replace <YOUR_TOKEN> before running.
Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: llmpulse-mcp
Remote MCP server URL: https://api.llmpulse.ai/api/v1/mcp
This server expects the header Authorization.Cursor
{
"mcpServers": {
"llmpulse-mcp": {
"url": "https://api.llmpulse.ai/api/v1/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Replace <YOUR_TOKEN> before running.
VS Code
code --add-mcp '{"name":"llmpulse-mcp","type":"http","url":"https://api.llmpulse.ai/api/v1/mcp","headers":{"Authorization":"Bearer <YOUR_TOKEN>"}}'Replace <YOUR_TOKEN> before running.
Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
Tools are visible after sign-in; we do not look inside protected servers.
Details
- Registry status
- Active
- Published
- Jul 6, 2026
- Updated
- Jul 6, 2026
- Categories (suggested)
- AI modelsData and analyticsMarketing and SEOSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared