My MCP server
live.alpic.stagingPublished by staging.alpic.liveOfficial publisherv0.0.34Updated Oct 24, 2026
Description of my MCP server mega cool capabilities, lesgo
Overview
A remotely hosted MCP server with no published tool list or documentation, described only as offering unspecified capabilities.
- What you can do
- The registry entry gives no tool list, so what the assistant can actually do through it is unknown. The only description is a one-line promotional statement about unspecified capabilities. No instructions or README are provided to explain usage. Treat it as an undocumented endpoint until its tools are inspected after connecting.
- When to use it
- Only worth trying if you specifically want to inspect what this staging endpoint exposes, for example to test a deployment. It is not a good choice for real work, since nothing documents what it does.
- Requirements
- A remote streamable HTTP endpoint; no package, environment variables or headers are declared. The manifest declares no authentication, so no credentials appear to be needed. Network access to the provider's staging host is required.
Installation
In SourceWeft
- Open My MCP server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. 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/live.alpic.staging%2Falpic-poc-frontend-9eb5bfc8/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.
{
"mcpServers": {
"my": {
"type": "http",
"url": "https://alpic-poc-frontend-9eb5bfc8.staging.alpic.live/"
}
}
}Tools
0Version history
1- v0.0.34LatestSep 16, 2026
Score
56% 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 listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- 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.
Other Alpic integrations
Email Server
live.alpic.stagingOfficial publisher
A remote MCP server that gives an assistant email capabilities, hosted on the Alpic platform.
Hey World
live.alpic.stagingOfficial publisher
Hey World's hosted MCP server, published by staging.alpic.live; no sign-in required; Streamable HTTP.
My MCP Server
live.alpic.stagingOfficial publisher
My's hosted MCP server, published by staging.alpic.live; no sign-in required; Streamable HTTP.
Email Server
live.alpic.stagingOfficial publisher
A hosted MCP server that gives an assistant email capabilities through a remote endpoint.
My MCP Serve
live.alpic.stagingOfficial publisher
My MCP Serve's hosted MCP server, published by staging.alpic.live; no sign-in required; Streamable HTTP.