
Velaris Intelligence
io.github.Velaris-CSMPublished by GitHub account Velaris-CSMv1.0.1Updated Oct 24, 2026
AI-generated customer success reports for Velaris platform users. Authenticates via OAuth.
Overview
Lets an assistant produce AI-generated customer success reports for users of the Velaris platform, with OAuth sign-in.
- What you can do
- This remote MCP server exposes AI-generated customer success reports for users of the Velaris platform. The registry description names report generation as its purpose and states that it authenticates via OAuth. No individual tools are listed in the manifest or description, so the exact operations available are not documented here.
- When to use it
- Relevant if you already use the Velaris platform and want an assistant to draft or retrieve customer success reports inside that context. It is not useful without a Velaris account, and the description gives no detail on report scope or format. The description is very short, so verify capabilities before relying on it. The description is very short, so verify capabilities before relying on it.
- Requirements
- A remote SSE endpoint at reachable over the network. OAuth authentication is required; no environment variables or headers are declared. A Velaris platform account is implied by the description.
Installation
In SourceWeft
- Open Velaris Intelligence in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Velaris-CSM%2Fvelaris-intelligence/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"velaris-intelligence": {
"type": "sse",
"url": "https://gx7rt55cmrb2ilws3nrl5hpvli0lvzxg.lambda-url.eu-west-2.on.aws/"
}
}
}Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.