SHAR Public Knowledge MCP

com.sharprodPublished by sharprod.comOfficial publisherv0.1.0Updated Oct 24, 2026

Anonymous read-only access to source-backed public SHAR Production knowledge.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

A remote MCP endpoint giving assistants anonymous, read-only access to source-backed public SHAR Production knowledge.

What you can do
Retrieve public SHAR Production knowledge entries through a remote MCP endpoint, with no tool list published in the manifest. Access is anonymous and read-only, and results are described as source-backed. No further capabilities are documented in the supplied description, instructions or README.
When to use it
When an assistant needs to look up public, source-backed SHAR Production knowledge without signing in, and read-only access is sufficient.
Requirements
A remote streamable HTTP connection to the provider's endpoint; no packages, environment variables, headers or authentication are declared. Network access to the endpoint is required.
Before you install
Only public knowledge is exposed and access is read-only, so no writes are expected. No credentials are requested. The manifest lists no tools, so verify the actual tool behavior after connecting; queries go to a third-party service.

Installation

In SourceWeft

  1. Open SHAR Public Knowledge MCP 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.sharprod%2Fpublic-knowledge/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": {
    "shar-public-knowledge": {
      "type": "http",
      "url": "https://mcp.sharprod.com/public"
    }
  }
}

Tools

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

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

28% 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.

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