ashare.net

net.asharePublished by ashare.netOfficial publisherv1.0.1Updated Oct 30, 2026

Share what AI agents write with the right people only: your company, specific emails or a password.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

ashare.net is a remote MCP server that lets an AI assistant share what it writes with chosen people only — your company, specific emails, or a password.

What you can do
  • Share AI-written content with a restricted audience: your company, named email addresses, or a password.
  • Control who can see each shared item rather than publishing it openly.
  • Connect over a remote streamable HTTP endpoint with OAuth sign-in; no tool list is published, so exact operations are not documented.
When to use it
Useful when an assistant produces text or documents that should reach a limited set of people — colleagues, a few named recipients, or anyone holding a password — instead of the public web.
Requirements
A remote endpoint at ashare.net reached over streamable HTTP; OAuth authentication is required, so an ashare.net account and a client that supports OAuth are needed. No environment variables or headers are declared.
Before you install
Sharing sends content to a third-party service, so check what leaves your machine. Access is granted by company, email list or password; a shared password can be passed on to anyone. No tool list is published, so confirm what the server can read or change before connecting.

Installation

In SourceWeft

  1. Open ashare.net 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/net.ashare%2Fashare/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": {
    "ashare-net": {
      "type": "http",
      "url": "https://ashare.net/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

2
  1. v1.0.1LatestOct 30, 2026
  2. v1.0.0Oct 26, 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.