Site Rep MCP

io.github.nish3451Published by GitHub account nish3451v1.0.0Updated Oct 24, 2026

Read-only Site Rep handoff: agent brief, pending work, first-customer receipt with payment evidence.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A read-only Site Rep handoff server that lets an assistant fetch an agent brief, pending work, and a first-customer receipt with payment evidence.

What you can do
Site Rep MCP is a remote, read-only handoff endpoint. According to its description, it exposes an agent brief, pending work, and a first-customer receipt that includes payment evidence. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Use it when an assistant needs to pick up context from Site Rep, such as reviewing an agent brief, checking what work is still pending, or confirming a first-customer receipt with payment evidence.
Requirements
A remote streamable HTTP endpoint at siterep.net. It requires bearer authentication: an Authorization header carrying a Site Rep API key with the scopes bot:read, sources:read, conversations:read and leads:read. No environment variables or packages are declared.
Before you install
The server requires a Site Rep API key sent in the Authorization header; treat it as a secret and grant only the listed read scopes. The description says access is read-only, but the manifest does not list tools, so confirm what each call does before relying on it. Payment evidence may include sensitive customer or financial data.

Installation

In SourceWeft

  1. Open Site Rep MCP in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/io.github.nish3451%2Fsite-rep/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": {
    "site-rep": {
      "type": "http",
      "url": "https://siterep.net/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 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.