Vicem

ai.vicemPublished by vicem.aiOfficial publisherv1.0.0Updated Oct 24, 2026

See the calls your Vicem answered and ask it to call or message someone, with your OK first.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant see the calls Vicem answered and, with your approval, ask Vicem to call or message someone.

What you can do
Vicem is a remote MCP server reached over streamable HTTP. According to its description, it lets an assistant view the calls that Vicem answered and request that Vicem place a call or send a message to someone. Such requests are described as requiring your confirmation first. No individual tools are listed in the manifest.
When to use it
Relevant if you use Vicem for calls or messaging and want an assistant to review which calls were answered or to initiate a call or message through it. Less useful if you do not already use Vicem.
Requirements
A remote endpoint at api.vicem.ai over streamable HTTP. Authentication is OAuth and is required; no environment variables or headers are declared. A Vicem account is implied by the OAuth sign-in.
Before you install
The server can initiate calls and messages to other people, which are outward-facing actions; the description says these need your approval first, so review each request before confirming. Access is granted through OAuth, so check which permissions you authorize. No tool list is published, so the exact scope of actions is unclear.

Installation

In SourceWeft

  1. Open Vicem in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/ai.vicem%2Fvicem/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "vicem": {
      "type": "http",
      "url": "https://api.vicem.ai/v1/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 10, 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.