Copass Remote

com.olanePublished by olane.comv0.1.0Updated Oct 24, 2026

Knowledge graph ingestion, entity search, ontology analysis, and CoPass scoring.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

A remote MCP endpoint for ingesting knowledge graphs, searching entities, analyzing ontologies, and computing CoPass scores.

What you can do
Copass Remote is a hosted MCP server reached at a fixed remote endpoint. According to its registry description, it covers knowledge graph ingestion, entity search, ontology analysis, and CoPass scoring. No tool list, README, or package details are published, so the exact tool names and parameters are not documented here.
When to use it
Consider it when an assistant needs to load graph-structured knowledge, look up entities, inspect ontology relationships, or obtain CoPass scores as part of a workflow. It is less suitable if you need documented tool schemas or offline operation, since neither is described.
Requirements
A client that supports the streamable HTTP transport and network access to the remote endpoint. The manifest declares no authentication, environment variables, headers, or packages, so no credentials are documented as required.
Before you install
The manifest declares no authentication, which means anyone who can reach the endpoint may be able to use it; confirm access control before sending sensitive data. Ingestion and scoring may write data to a third-party service, and no privacy or retention terms are provided. No tool list is published, so review actual tool behavior before relying on it.

Installation

In SourceWeft

  1. Open Copass Remote in the dashboard and add it to a workspace.
  2. 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/com.olane%2Fcopass-remote/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.

{
  "mcpServers": {
    "copass-remote": {
      "type": "http",
      "url": "https://mcp.copass.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.